Use include for details of Direct Routing customer label restrictions

Author: rcdun

articles/communications-gateway/includes/communications-gateway-direct-routing-subdomain-calculation.md

@@ -5,25 +5,9 @@ ms.service: communications-gateway
 ms.topic: include
 ms.date: 04/04/2024
 ---
-
-1. Work out the per-region domain names for connecting to Microsoft Teams Direct Routing. These domain names use the form `1r<region-number>.<base-domain-name>`. The base domain name is the **Domain** on your Azure Communications Gateway resource in the [Azure portal](https://azure.microsoft.com/).
-1. Choose a DNS label to identify the test customer.
+1. Choose a suitable customer-specific DNS label to form the subdomains.
     - The label must be up to **nine** characters in length and can only contain letters, numbers, underscores, and dashes.
     - You must not use wildcard subdomains or subdomains with multiple labels.
     - For example, you could allocate the label `contoso`.
     > [!IMPORTANT]
-    > The full customer subdomains (including the per-region domain names) must be a maximum of 48 characters. Microsoft Entra ID does not support domain names of more than 48 characters. For example, the customer subdomain `contoso1.1r1.a1b2c3d4e5f6g7h8.commsgw.azure.com` is 48 characters.
-1. Use this label to create a _customer subdomain_ of each per-region domain name for your Azure Communications Gateway.
-1. Make a note of the label you choose and the corresponding customer subdomains.
-
-For example:
-- Your base domain name might be `<deployment-id>.commsgw.azure.com`, where `<deployment-id>` is autogenerated and unique to the deployment.
-- Your per-region domain names are therefore:
-    - `1r1.<deployment-id>.commsgw.azure.com`
-    - `1r2.<deployment-id>.commsgw.azure.com`
-- If you allocate the label `contoso`, this label combined with the per-region domain names creates the following customer subdomains for your customer:
-    - `contoso.1r1.<deployment-id>.commsgw.azure.com`
-    - `contoso.1r2.<deployment-id>.commsgw.azure.com`
-
-> [!IMPORTANT]
-> The per-region domain names for connecting to Microsoft Teams Direct Routing are different to the per-region domain names for connecting to your network.
+    > The full customer subdomains (including the per-region domain names) must be a maximum of 48 characters. Microsoft Entra ID does not support domain names of more than 48 characters. For example, the customer subdomain `contoso1.1r1.a1b2c3d4e5f6g7h8.commsgw.azure.com` is 48 characters.

articles/communications-gateway/interoperability-teams-direct-routing.md

@@ -57,14 +57,11 @@ Each of your customers needs _customer subdomains_ of these per-region domains.
 
 For each customer, you must:
 
-1. Choose a suitable subdomain. The label for the subdomain must:
-    - Contain only letters, numbers, underscores, and dashes.
-    - Be up to **nine** characters in length.
-    - Not contain a wildcard or multiple labels separated by `.`.
-    > [!IMPORTANT]
-    > The full customer subdomain (including the regional subdomains and the base domain) must be a maximum of 48 characters. Microsoft Entra ID does not support domain names of more than 48 characters. For example, the customer subdomain `contoso12.1r1.a1b2c3d4e5f6g7h8.commsgw.azure.com` is 48 characters.
-2. Configure Azure Communications Gateway with this information, as part of "account" configuration available in Azure Communications Gateway's Number Management Portal and Provisioning API.
-3. Liaise with the customer to update their tenant with the appropriate subdomain, by following the [Microsoft Teams documentation for registering subdomain names in customer tenants](/microsoftteams/direct-routing-sbc-multiple-tenants#register-a-subdomain-name-in-a-customer-tenant).
+[!INCLUDE [communications-gateway-direct-routing-subdomain-calculation](includes/communications-gateway-direct-routing-subdomain-calculation.md)]
+
+1. Configure Azure Communications Gateway with this information, as part of "account" configuration available in Azure Communications Gateway's Number Management Portal and Provisioning API.
+
+1. Liaise with the customer to update their tenant with the appropriate subdomain, by following the [Microsoft Teams documentation for registering subdomain names in customer tenants](/microsoftteams/direct-routing-sbc-multiple-tenants#register-a-subdomain-name-in-a-customer-tenant).
 
 As part of arranging updates to customer tenants, you must create DNS records containing a verification code (provided by Microsoft 365 when the customer updates their tenant with the domain name) on a DNS server that you control. These records allow Microsoft 365 to verify that the customer tenant is authorized to use the domain name. Azure Communications Gateway provides the DNS server that you must use. You must obtain the verification code from the customer and upload it to Azure Communications Gateway with the Number Management Portal (preview) or the Provisioning API (preview). This step allows Azure Communications Gateway to generate the DNS TXT records that verify the domain.
 

articles/communications-gateway/manage-enterprise-teams-direct-routing.md

@@ -45,8 +45,26 @@ This procedure provides detailed guidance equivalent to the following steps in t
 
 Azure Communications Gateway has _per-region domain names_ for connecting to Microsoft Teams Direct Routing. You need to choose subdomains of these domain names for your customer. Microsoft Phone System and Azure Communications Gateway use these subdomains to match calls to tenants.
 
+1. Work out the per-region domain names for connecting to Microsoft Teams Direct Routing. These domain names use the form `1r<region-number>.<base-domain-name>`. The base domain name is the **Domain** on your Azure Communications Gateway resource in the [Azure portal](https://azure.microsoft.com/).
+
 [!INCLUDE [communications-gateway-direct-routing-subdomain-calculation](includes/communications-gateway-direct-routing-subdomain-calculation.md)]
 
+1. Use this label to create a _customer subdomain_ of each per-region domain name for your Azure Communications Gateway.
+
+1. Make a note of the label you choose and the corresponding customer subdomains.
+
+For example:
+- Your base domain name might be `<deployment-id>.commsgw.azure.com`, where `<deployment-id>` is autogenerated and unique to the deployment.
+- Your per-region domain names are therefore:
+    - `1r1.<deployment-id>.commsgw.azure.com`
+    - `1r2.<deployment-id>.commsgw.azure.com`
+- If you allocate the label `contoso`, this label combined with the per-region domain names creates the following customer subdomains for your customer:
+    - `contoso.1r1.<deployment-id>.commsgw.azure.com`
+    - `contoso.1r2.<deployment-id>.commsgw.azure.com`
+
+> [!IMPORTANT]
+> The per-region domain names for connecting to Microsoft Teams Direct Routing are different to the per-region domain names for connecting to your network.
+
 > [!TIP]
 > Lab deployments have one per-region domain name. A customer for a lab deployment therefore also only has one customer subdomain.