Skip to content

Commit 4aabf31

Browse files
committed
Fixes MicrosoftDocs/azure-docs#97633
1 parent 0f1e806 commit 4aabf31

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

articles/lighthouse/concepts/architecture.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Azure Lighthouse architecture
33
description: Learn about the relationship between tenants in Azure Lighthouse, and the resources created in the customer's tenant that enable that relationship.
4-
ms.date: 06/09/2022
4+
ms.date: 08/26/2022
55
ms.topic: conceptual
66
---
77

@@ -16,6 +16,9 @@ Azure Lighthouse helps service providers simplify customer engagement and onboar
1616
1717
This topic discusses the relationship between tenants in Azure Lighthouse, and the resources created in the customer's tenant that enable that relationship.
1818

19+
> [!NOTE]
20+
> Onboarding a customer to Azure Lighthouse requires a deployment by a non-guest account in the customer's tenant who has a role with the `Microsoft.Authorization/roleAssignments/write` permission, such as [Owner](../../role-based-access-control/built-in-roles.md#owner), for the subscription being onboarded (or which contains the resource groups that are being onboarded).
21+
1922
## Delegation resources created in the customer tenant
2023

2124
When a customer’s subscription or resource group is onboarded to Azure Lighthouse, two resources are created: the **registration definition** and the **registration assignment**. You can use [APIs and management tools](cross-tenant-management-experience.md#apis-and-management-tool-support) to access these resources, or work with them [in the Azure portal](../how-to/view-manage-customers.md).

0 commit comments

Comments
 (0)