Merge pull request #99268 from JnHs/jh-onboard-case

clarify casing

Author: PRMerger20

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

@@ -1,7 +1,7 @@
 ---
 title: Onboard a customer to Azure delegated resource management
 description: Learn how to onboard a customer to Azure delegated resource management, allowing their resources to be accessed and managed through your own tenant.
-ms.date: 12/12/2019
+ms.date: 12/17/2019
 ms.topic: conceptual
 ---
 
@@ -29,7 +29,7 @@ To onboard a customer's tenant, it must have an active Azure subscription. You'l
 - The tenant ID of the customer's tenant (which will have resources managed by the service provider)
 - The subscription IDs for each specific subscription in the customer's tenant that will be managed by the service provider (or that contains the resource group(s) that will be managed by the service provider)
 
-If you don't have this info already, you can retrieve it in one of the following ways.
+If you don't have this info already, you can retrieve it in one of the following ways. Be sure and use these exact values in your deployment.
 
 ### Azure portal
 
@@ -108,9 +108,12 @@ To onboard your customer, you'll need to create an [Azure Resource Manager](../.
 |Field  |Definition  |
 |---------|---------|
 |**mspOfferName**     |A name describing this definition. This value is displayed to the customer as the title of the offer.         |
-|**mspOfferDescription**     |A brief description of your offer (for example, "Contoso VM management offer")      |
-|**managedByTenantId**     |Your tenant ID         |
-|**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         |
+|**mspOfferDescription**     |A brief description of your offer (for example, "Contoso VM management offer"),      |
+|**managedByTenantId**     |Your tenant ID.          |
+|**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,         |
+
+> [!TIP]
+> 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.
 
 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.