Merge pull request #269932 from rcdun/1391629_ensure_correct_domain_validation_and_user_configuration

1391629 Fix Teams setup instructions for Direct Routing with Communications Gateway

Author: JamesJBarnett

articles/communications-gateway/configure-test-customer-teams-direct-routing.md

@@ -5,7 +5,7 @@ author: rcdun
 ms.author: rdunstan
 ms.service: communications-gateway
 ms.topic: how-to
-ms.date: 01/08/2024
+ms.date: 03/22/2024
 
 #CustomerIntent: As someone deploying Azure Communications Gateway, I want to test my deployment so that I can be sure that calls work.
 ---
@@ -19,6 +19,11 @@ Testing Microsoft Teams Direct Routing requires some test numbers in a Microsoft
 >
 > For more information about how Azure Communications Gateway and Microsoft Teams use tenant configuration to route calls, see [Support for multiple customers with the Microsoft Teams multitenant model](interoperability-teams-direct-routing.md#support-for-multiple-customers-with-the-microsoft-teams-multitenant-model).
 
+This article provides detailed guidance equivalent to the following steps in the [Microsoft Teams documentation for configuring an SBC for multiple tenants](/microsoftteams/direct-routing-sbc-multiple-tenants).
+
+- Registering a subdomain name in the customer tenant.
+- Configuring derived trunks in the customer tenant (including failover).
+
 ## Prerequisites
 
 You must have a Microsoft 365 tenant that you can use as a test customer. You must have at least one number that you can allocate to this test customer.
@@ -33,6 +38,11 @@ Your organization must [integrate with Azure Communications Gateway's Provisioni
 
 You must be able to sign in to the Microsoft 365 admin center for your test customer tenant as a Global Administrator.
 
+You must be able to configure the tenant with at least two user or resource accounts licensed for Microsoft Teams. For more information on suitable licenses, see the [Microsoft Teams documentation](/microsoftteams/direct-routing-sbc-multiple-tenants#activate-the-subdomain-name).
+
+- You need two user or resource accounts to activate the Azure Communications Gateway domains that you add to Microsoft 365 by following this article. Lab deployments require one account.
+- You need at least one user account to use for testing later when you carry out [Configure test numbers for Microsoft Teams Direct Routing with Azure Communications Gateway](configure-test-numbers-teams-direct-routing.md). You can reuse one of the accounts that you use to activate the domains, or you can use an account with one of the other domain names for this tenant.
+
 ## Choose a DNS subdomain label to use to identify the customer
 
 Azure Communications Gateway has _per-region domain names_ for connecting to Microsoft Teams Direct Routing. You need to set up subdomains of these domain names for your test customer. Microsoft Phone System and Azure Communications Gateway use these subdomains to match calls to tenants.
@@ -44,41 +54,41 @@ Azure Communications Gateway has _per-region domain names_ for connecting to Mic
     - For example, you could allocate the label `test`.
     > [!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.1-r1.a1b2c3d4e5f6g7h8.commsgw.azure.com` is 48 characters.
-1. Use this label to create a subdomain of each per-region domain name for your Azure Communications Gateway.
-1. Make a note of the label you choose and the corresponding subdomains.
+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:
     - `1-r1.<deployment-id>.commsgw.azure.com`
     - `1-r2.<deployment-id>.commsgw.azure.com`
-- If you allocate the label `test`, this label combined with the per-region domain names creates the following domain names for your test customer:
+- If you allocate the label `test`, this label combined with the per-region domain names creates the following customer subdomains for your test customer:
     - `test.1-r1.<deployment-id>.commsgw.azure.com`
     - `test.1-r2.<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. Your test customer therefore also only has one customer-specific per-region domain name.
+> Lab deployments have one per-region domain name. Your test customer therefore also only has one customer subdomain.
 
 ## Start registering the subdomains in the customer tenant and get DNS TXT values
 
-To route calls to a customer tenant, the customer tenant must be configured with the customer-specific per-region domain names that you allocated in [Choose a DNS subdomain label to use to identify the customer](#choose-a-dns-subdomain-label-to-use-to-identify-the-customer). Microsoft 365 then requires you (as the carrier) to create DNS records that use a verification code that Microsoft 365 supplies in the customer tenant.
+To route calls to a customer tenant, the customer tenant must be configured with the customer subdomains that you allocated in [Choose a DNS subdomain label to use to identify the customer](#choose-a-dns-subdomain-label-to-use-to-identify-the-customer). Microsoft 365 then requires you (as the carrier) to create DNS records that use a verification code from the customer tenant.
 
 1. Sign into the Microsoft 365 admin center for the customer tenant as a Global Administrator.
 1. Using [Add a subdomain to the customer tenant and verify it](/microsoftteams/direct-routing-sbc-multiple-tenants#add-a-subdomain-to-the-customer-tenant-and-verify-it):
-    1. Register the first customer-specific per-region domain name (for example `test.1-r1.<deployment-id>.commsgw.azure.com`).
+    1. Register the first customer subdomain (for example `test.1-r1.<deployment-id>.commsgw.azure.com`).
     1. Start the verification process using TXT records.
     1. Note the TXT value that Microsoft 365 provides.
-1. (Production deployments only) Repeat the previous step for the second customer-specific per-region domain name.
+1. (Production deployments only) Repeat the previous step for the second customer subdomain.
 
 > [!IMPORTANT]
 > Don't complete the verification process yet. You must carry out [Use Azure Communications Gateway's Provisioning API to configure the customer and generate DNS records](#use-azure-communications-gateways-provisioning-api-to-configure-the-customer-and-generate-dns-records) first.
 
 ## Use Azure Communications Gateway's Provisioning API to configure the customer and generate DNS records
 
-Azure Communications Gateway includes a DNS server. You must use Azure Communications Gateway to create the DNS records required to verify the customer subdomain. To generate the records, provision the details of the customer tenant and the DNS TXT values on Azure Communications Gateway.
+Azure Communications Gateway includes a DNS server. You must use Azure Communications Gateway to create the DNS records required to verify the customer subdomains. To generate the records, provision the details of the customer tenant and the DNS TXT values on Azure Communications Gateway.
 
 1. Use Azure Communications Gateway's Provisioning API to configure the customer as an account. The request must:
     - Enable Direct Routing for the account.
@@ -94,14 +104,29 @@ When you have used Azure Communications Gateway to generate the DNS records for
 
 1. Sign into the Microsoft 365 admin center for the customer tenant as a Global Administrator.
 1. Select **Settings** > **Domains**.
-1. Finish verifying the customer-specific per-region domain names by following [Add a subdomain to the customer tenant and verify it](/microsoftteams/direct-routing-sbc-multiple-tenants#add-a-subdomain-to-the-customer-tenant-and-verify-it).
+1. Finish verifying the customer subdomains by following [Add a subdomain to the customer tenant and verify it](/microsoftteams/direct-routing-sbc-multiple-tenants#add-a-subdomain-to-the-customer-tenant-and-verify-it).
+
+## Activate the domains in the customer tenant
+
+To activate the customer subdomains in Microsoft 365, set up at least one user or resource account licensed for Microsoft Teams for each  domain name. For information on the licenses you can use and instructions, see [Activate the subdomain name](/microsoftteams/direct-routing-sbc-multiple-tenants#activate-the-subdomain-name).
+
+> [!IMPORTANT]
+> Ensure the accounts use the customer subdomains (for example, `test.1-r1.<deployment-id>.commsgw.azure.com`), instead of any existing domain names in the tenant.
 
 ## Configure the customer tenant's call routing to use Azure Communications Gateway
 
 In the customer tenant, [configure a call routing policy](/microsoftteams/direct-routing-voice-routing) (also called a voice routing policy) with a voice route that routes calls to Azure Communications Gateway.
-- Set the PSTN gateway to the customer-specific per-region domain names for Azure Communications Gateway (for example, `test.1-r1.<deployment-id>.commsgw.azure.com` and `test.1-r2.<deployment-id>.commsgw.azure.com`).
+- Set the PSTN gateway to the customer subdomains for Azure Communications Gateway (for example, `test.1-r1.<deployment-id>.commsgw.azure.com` and `test.1-r2.<deployment-id>.commsgw.azure.com`). This sets up _derived trunks_ for the customer tenant.
 - Don't configure any users to use the call routing policy yet.
 
+> [!IMPORTANT]
+> You must use PowerShell to set the PSTN gateways for the voice route, because the Microsoft Teams Admin Center doesn't support adding derived trunks. You can use the Microsoft Teams Admin Center for all other voice route configuration.
+>
+> To set the PSTN gateways for a voice route, use the following PowerShell command.
+> ```powershell
+> Set-CsOnlineVoiceRoute -id "<voice-route-id>" -OnlinePstnGatewayList <customer-subdomain-1>, <customer-subdomain-2>
+> ```
+
 ## Next step
 
 > [!div class="nextstepaction"]

articles/communications-gateway/configure-test-numbers-teams-direct-routing.md

@@ -5,7 +5,7 @@ author: rcdun
 ms.author: rdunstan
 ms.service: communications-gateway
 ms.topic: how-to
-ms.date: 10/09/2023
+ms.date: 03/22/2024
 
 #CustomerIntent: As someone deploying Azure Communications Gateway, I want to test my deployment so that I can be sure that calls work.
 ---
@@ -21,6 +21,8 @@ To test Microsoft Teams Direct Routing with Azure Communications Gateway, you ne
 
 You must have at least one number that you can allocate to your test tenant.
 
+You must be able to configure the tenant with at least one user account licensed for Microsoft Teams. You can reuse one of the accounts that you use to activate the customer subdomains in [Configure a test customer for Microsoft Teams Direct Routing](configure-test-customer-teams-direct-routing.md), or you can use an account with one of the other domain names for this tenant.
+
 You must complete the following procedures.
 
 - [Prepare to deploy Azure Communications Gateway](prepare-to-deploy.md)
@@ -29,6 +31,7 @@ You must complete the following procedures.
 - [Configure a test customer for Microsoft Teams Direct Routing](configure-test-customer-teams-direct-routing.md)
 
 Your organization must [integrate with Azure Communications Gateway's Provisioning API](integrate-with-provisioning-api.md). Someone in your organization must be able to make requests using the Provisioning API during this procedure.
+
 You must be able to sign in to the Microsoft 365 admin center for your test customer tenant as a Global Administrator.
 
 ## Configure the test numbers on Azure Communications Gateway with the Provisioning API

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

@@ -5,7 +5,7 @@ author: rcdun
 ms.author: rdunstan
 ms.service: communications-gateway
 ms.topic: integration
-ms.date: 01/08/2024
+ms.date: 03/22/2024
 ms.custom:
     - template-how-to-pattern
 ---
@@ -16,6 +16,11 @@ After you deploy Azure Communications Gateway and connect it to your core networ
 
 This article describes how to start connecting Azure Communications Gateway to Microsoft Teams Direct Routing. After you finish the steps in this article, you can set up test users for test calls and prepare for live traffic.
 
+This article provides detailed guidance equivalent to the following steps in the [Microsoft Teams documentation for configuring an SBC for multiple tenants](/microsoftteams/direct-routing-sbc-multiple-tenants).
+
+- Registering a base domain name in the carrier tenant.
+- Creating a trunk in the carrier tenant (a _carrier trunk_).
+
 ## Prerequisites
 
 You must [deploy Azure Communications Gateway](deploy.md).
@@ -28,6 +33,8 @@ You must have **Reader** access to the subscription into which Azure Communicati
 
 You must be able to sign in to the Microsoft 365 admin center for your tenant as a Global Administrator.
 
+You must be able to configure your tenant with two user or resource accounts licensed for Microsoft Teams. Lab deployments require one account. For more information on suitable licenses, see the [Microsoft Teams documentation](/microsoftteams/direct-routing-sbc-multiple-tenants#activate-the-domain-name).
+
 ## Enable Microsoft Teams Direct Routing support
 
 > [!NOTE]
@@ -55,12 +62,12 @@ Microsoft Teams only sends traffic to domains that you confirm that you own. You
 1. Work out the _per-region domain names_ for connecting to Microsoft Teams Direct Routing. These use the form `1-r<region-number>.<base-domain-name>`.
     - A production deployment has two service regions and therefore two per-region domain names: `1-r1.<base-domain-name>` and `1-r2.<base-domain-name>`
     - A lab deployment has one service region and therefore one per-region domain name: `1-r1.<base-domain-name>`.
-1. Note down the base domain name and the per-region domain name(s). You'll need these values in the next steps.
+1. Note down the base domain name and the per-region domain names. You'll need these values in the next steps.
 
 > [!IMPORTANT]
 > The domain names for connecting to Microsoft Teams Direct Routing are different to the domain names for connecting to your network.
 
-## Register the base domain name for Azure Communications Gateway in your tenant
+## Register the base domain name in your tenant
 
 You need to register the base domain for Azure Communications Gateway in your tenant and verify it. Registering and verifying the base domain proves that you control the domain.
 
@@ -69,7 +76,7 @@ You need to register the base domain for Azure Communications Gateway in your te
 > - You must register Azure Communications Gateway's base domain name.
 > - Microsoft 365 automatically verifies the base domain name.
 
-Follow the instructions [to add a base domain to your tenant](/microsoftteams/direct-routing-sbc-multiple-tenants#add-a-base-domain-to-the-tenant-and-verify-it). Use the base domain name that you found in [Find your Azure Communication Gateway's domain names for connecting to Microsoft Teams Direct Routing](#find-your-azure-communication-gateways-domain-names-for-connecting-to-microsoft-teams-direct-routing).
+Follow the instructions [to add a domain to your tenant](/microsoftteams/direct-routing-sbc-multiple-tenants#add-a-base-domain-to-the-tenant-and-verify-it). Use the base domain name that you found in [Find your Azure Communication Gateway's domain names for connecting to Microsoft Teams Direct Routing](#find-your-azure-communication-gateways-domain-names-for-connecting-to-microsoft-teams-direct-routing).
 
 If Microsoft 365 prompts you to verify the domain name:
 
@@ -91,7 +98,7 @@ If you don't already have an onboarding team, contact azcog-enablement@microsoft
 ## Finish verifying the base domain name in Microsoft 365
 
 > [!NOTE]
-> If Microsoft 365 did not prompt you to verify the domain in [Register the base domain name for Azure Communications Gateway in your tenant](#register-the-base-domain-name-for-azure-communications-gateway-in-your-tenant), skip this step.
+> If Microsoft 365 did not prompt you to verify the domain in [Register the base domain name in your tenant](#register-the-base-domain-name-in-your-tenant), skip this step.
 
 After your onboarding team confirms that the DNS records have been set up, finish verifying the base domain name in the Microsoft 365 admin center.
 
@@ -102,9 +109,19 @@ After your onboarding team confirms that the DNS records have been set up, finis
 1. Select **Finish** on the **Update DNS settings** page.
 1. Ensure that the status is **Setup complete**.
 
-## Set up a user or resource account with the base domain and an appropriate license
+## Register the per-region domain names in your tenant
+
+Before you can connect your tenant to Azure Communications Gateway, you need to:
+- Register the per-region domain names for connecting to Microsoft Teams Direct Routing in your tenant (this step).
+- Activate the domain names in Microsoft 365 by setting up a user or resource account for each domain name and an appropriate license (next step).
+
+Follow the instructions [to add a domain to your tenant](/microsoftteams/direct-routing-sbc-multiple-tenants#add-a-base-domain-to-the-tenant-and-verify-it) once for each per-region domain name. You found these domain names in [Find your Azure Communication Gateway's domain names for connecting to Microsoft Teams Direct Routing](#find-your-azure-communication-gateways-domain-names-for-connecting-to-microsoft-teams-direct-routing).
 
-To activate the base domain in Microsoft 365, you must have at least one user or resource account licensed for Microsoft Teams. For more information, including the licenses you can use, see [Activate the domain name](/microsoftteams/direct-routing-sbc-multiple-tenants#activate-the-domain-name).
+Microsoft 365 should automatically verify these domain names, because you verified the base domain name.
+
+## Active the per-region domain names in your tenant
+
+To activate the per-region domain names in Microsoft 365, set up at least one user or resource account licensed for Microsoft Teams for each per-region domain name. For information on the licenses you can use and instructions, see [Activate the domain name](/microsoftteams/direct-routing-sbc-multiple-tenants#activate-the-domain-name).
 
 ## Connect your tenant to Azure Communications Gateway
 
@@ -131,6 +148,10 @@ Use [Connect your Session Border Controller (SBC) to Direct Routing](/microsoftt
 
 Use the default values for all other settings.
 
+## Confirm that your SIP trunks are active
+
+Confirm that the SIP OPTIONS status of each SIP trunk is Active.
+
 ## Next step
 
 > [!div class="nextstepaction"]