1331138 Use Teams-facing FQDNs for connecting to Teams

Author: rcdun

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

@@ -37,32 +37,22 @@ You must be able to sign in to the Microsoft 365 admin center for your test cust
 
 Azure Communications Gateway has per-region domain names. You need to set up subdomains of these domain names for your test customer.  Microsoft Phone System and Azure Communications Gateway use this subdomain to match calls to tenants.
 
+1. Work out the _per-region domain names_. These use the form `1-r<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.
-    * The label can be up to 10 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 `test`.
+    - The label can be up to 10 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 `test`.
 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.
 
-> [!TIP]
-> To find your deployment's per-region domain names:
-> 1. Sign in to the [Azure portal](https://azure.microsoft.com/).
-> 1. Search for your Communications Gateway resource and select it.
-> 1. Check that you're on the **Overview** of your Azure Communications Gateway resource.
-> 1. Select **Properties**.
-> 1. In each **Service Location** section, find the **Hostname** field.
-
-For example, your per-region domain names might be as follows, where the `<deployment_id>` subdomain is autogenerated and unique to the deployment:
-
-* `r1.<deployment_id>.commsgw.azure.com`
-* `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:
-
-* `test.r1.<deployment_id>.commsgw.azure.com`
-* `test.r2.<deployment_id>.commsgw.azure.com`
-
-
+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:
+    - `test.1-r1.<deployment-id>.commsgw.azure.com`
+    - `test.1-r2.<deployment-id>.commsgw.azure.com`
 
 > [!TIP]
 > Lab deployments have one per-region domain name. Your test customer therefore also only has one customer-specific per-region domain name.
@@ -73,7 +63,7 @@ To route calls to a customer tenant, the customer tenant must be configured with
 
 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.r1.<deployment_id>.commsgw.azure.com`).
+    1. Register the first customer-specific per-region domain name (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.
@@ -104,7 +94,7 @@ When you have used Azure Communications Gateway to generate the DNS records for
 ## 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.r1.<deployment_id>.commsgw.azure.com` and `test.r2.<deployment_id>.commsgw.azure.com`).
+- 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`).
 - Don't configure any users to use the call routing policy yet.
 
 ## Next step

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

@@ -52,9 +52,9 @@ Microsoft Teams only sends traffic to domains that you confirm that you own. You
 1. Select your Communications Gateway resource. Check that you're on the **Overview** of your Azure Communications Gateway resource.
 1. Select **Properties**.
 1. Find the field named **Domain**. This name is your deployment's _base domain name_.
-1. In each **Service Location** section, find the **Hostname** field. This field provides the _per-region domain name_.
-    - A production deployment has two service regions and therefore two per-region domain names.
-    - A lab deployment has one service region and therefore one per-region domain name.
+1. Work out the  _per-region domain names_. 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.
 
 ## Register the base domain name for Azure Communications Gateway in your tenant

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

@@ -157,7 +157,7 @@ If you believe that media bypass support (preview) would be useful for your depl
 
 ## Topology hiding with domain delegation
 
-The domain for your Azure Communications Gateway deployment is visible to customer administrators in their Microsoft 365 admin center. By default, each Azure Communications Gateway deployment receives an automatically generated domain name similar to `a1b2c3d4efghij5678.<deployment_id>.commsgw.azure.com`, where `<deployment_id>` is autogenerated and unique to the deployment.
+The domain for your Azure Communications Gateway deployment is visible to customer administrators in their Microsoft 365 admin center. By default, each Azure Communications Gateway deployment receives an automatically generated domain name similar to `a1b2c3d4efghij5678.<deployment-id>.commsgw.azure.com`, where `<deployment-id>` is autogenerated and unique to the deployment.
 
 To hide the details of your deployment, you can configure Azure Communications Gateway to use a subdomain of your own base domain. Customer administrators see subdomains of this domain in their Microsoft 365 admin center. This process uses [DNS delegation with Azure DNS](../dns/dns-domain-delegation.md). You must configure DNS delegation as part of deploying Azure Communications Gateway.
 

articles/communications-gateway/reliability-communications-gateway.md

@@ -61,7 +61,7 @@ Each site in your network must:
 > [!div class="checklist"]
 > - Send traffic to its local Azure Communications Gateway service region by default.
 > - Locate Azure Communications Gateway peers within a region using DNS SRV, as outlined in RFC 3263.
->     - Make a DNS SRV lookup on the domain name for the service region, for example `r1.<deployment_id>.commsgw.azure.com`, where `<deployment_id>` is autogenerated and unique to the deployment.
+>     - Make a DNS SRV lookup on the domain name for the service region, for example `r1.<deployment-id>.commsgw.azure.com`, where `<deployment-id>` is autogenerated and unique to the deployment.
 >     - If the SRV lookup returns multiple targets, use the weight and priority of each target to select a single target.
 > - Send new calls to available Azure Communications Gateway peers.