Skip to content

Commit 8999d91

Browse files
committed
remove casing note
1 parent cbcdef1 commit 8999d91

File tree

1 file changed

+0
-3
lines changed

1 file changed

+0
-3
lines changed

articles/lighthouse/how-to/onboard-customer.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -115,9 +115,6 @@ To onboard your customer, you'll need to create an [Azure Resource Manager](../.
115115
|**managedByTenantId** |Your tenant ID. |
116116
|**authorizations** |The **principalId** values for the users/groups/SPNs from your tenant, each with a **principalIdDisplayName** to help your customer understand the purpose of the authorization, and mapped to a built-in **roleDefinitionId** value to specify the level of access. |
117117

118-
> [!TIP]
119-
> Be sure that your **managedByTenantID**, **principalIdDisplayName**, and **roleDefinitionId** entries are identical to the values used by Azure. Do not use any capital letters in these values.
120-
121118
The onboarding process requires an Azure Resource Manager template (provided in our [samples repo](https://github.com/Azure/Azure-Lighthouse-samples/) and a corresponding parameters file that you modify to match your configuration and define your authorizations.
122119

123120
The template you choose will depend on whether you are onboarding an entire subscription, a resource group, or multiple resource groups within a subscription. We also provide a template that can be used for customers who purchased a managed service offer that you published to Azure Marketplace, if you prefer to onboard their subscription(s) this way.

0 commit comments

Comments
 (0)