Skip to content

Commit 85d0cc3

Browse files
committed
1331138 Differentiate more clearly between operator-facing FQDNs and DR-facing FQDNs
1 parent 2abdc0f commit 85d0cc3

File tree

2 files changed

+13
-7
lines changed

2 files changed

+13
-7
lines changed

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

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -35,9 +35,9 @@ You must be able to sign in to the Microsoft 365 admin center for your test cust
3535

3636
## Choose a DNS subdomain label to use to identify the customer
3737

38-
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 these subdomains to match calls to tenants.
38+
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.
3939

40-
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/).
40+
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>`. The base domain name is the **Domain** on your Azure Communications Gateway resource in the [Azure portal](https://azure.microsoft.com/).
4141
1. Choose a DNS label to identify the test customer.
4242
- The label must be up to **eight** characters in length and can only contain letters, numbers, underscores, and dashes.
4343
- You must not use wildcard subdomains or subdomains with multiple labels.
@@ -56,6 +56,9 @@ For example:
5656
- `test.1-r1.<deployment-id>.commsgw.azure.com`
5757
- `test.1-r2.<deployment-id>.commsgw.azure.com`
5858

59+
> [!IMPORTANT]
60+
> 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.
61+
5962
> [!TIP]
6063
> Lab deployments have one per-region domain name. Your test customer therefore also only has one customer-specific per-region domain name.
6164

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

Lines changed: 8 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ You must be able to sign in to the Microsoft 365 admin center for your tenant as
3131
## Enable Microsoft Teams Direct Routing support
3232

3333
> [!NOTE]
34-
> If you selected Microsoft Teams Direct Routing when you [deployed Azure Communications Gateway](deploy.md), skip this step and go to [Find your Azure Communication Gateway's domain names](#find-your-azure-communication-gateways-domain-names).
34+
> If you selected Microsoft Teams Direct Routing when you [deployed Azure Communications Gateway](deploy.md), skip this step and go to [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).
3535
3636
1. Sign in to the [Azure portal](https://azure.microsoft.com/).
3737
1. In the search bar at the top of the page, search for your Communications Gateway resource and select it.
@@ -41,7 +41,7 @@ You must be able to sign in to the Microsoft 365 admin center for your tenant as
4141
1. Select the **Overview** page for your resource.
4242
1. Wait for your resource to be updated. When your resource is ready, the **Provisioning Status** field on the resource overview changes to "Complete." We recommend that you check in periodically to see if the Provisioning Status field is "Complete." This step might take up to two weeks.
4343

44-
## Find your Azure Communication Gateway's domain names
44+
## Find your Azure Communication Gateway's domain names for connecting to Microsoft Teams Direct Routing
4545

4646
Before starting this step, check that the **Provisioning Status** field for your resource is "Complete".
4747

@@ -52,11 +52,14 @@ Microsoft Teams only sends traffic to domains that you confirm that you own. You
5252
1. Select your Communications Gateway resource. Check that you're on the **Overview** of your Azure Communications Gateway resource.
5353
1. Select **Properties**.
5454
1. Find the field named **Domain**. This name is your deployment's _base domain name_.
55-
1. Work out the _per-region domain names_. These use the form `1-r<region-number>.<base-domain-name>`.
55+
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>`.
5656
- 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>`
5757
- A lab deployment has one service region and therefore one per-region domain name: `1-r1.<base-domain-name>`.
5858
1. Note down the base domain name and the per-region domain name(s). You'll need these values in the next steps.
5959

60+
> [!IMPORTANT]
61+
> The domain names for connecting to Microsoft Teams Direct Routing are different to the domain names for connecting to your network.
62+
6063
## Register the base domain name for Azure Communications Gateway in your tenant
6164

6265
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.
@@ -66,7 +69,7 @@ You need to register the base domain for Azure Communications Gateway in your te
6669
> - You must register Azure Communications Gateway's base domain name.
6770
> - Microsoft 365 automatically verifies the base domain name.
6871
69-
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](#find-your-azure-communication-gateways-domain-names).
72+
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).
7073

7174
If Microsoft 365 prompts you to verify the domain name:
7275

@@ -105,7 +108,7 @@ To activate the base domain in Microsoft 365, you must have at least one user or
105108

106109
## Connect your tenant to Azure Communications Gateway
107110

108-
You must configure your Microsoft 365 tenant with SIP trunks to Azure Communications Gateway. Each trunk connects to one of the per-region domain names that you found in [Find your Azure Communication Gateway's domain names](#find-your-azure-communication-gateways-domain-names).
111+
You must configure your Microsoft 365 tenant with SIP trunks to Azure Communications Gateway. Each trunk connects to one of the per-region domain names 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).
109112

110113
Use [Connect your Session Border Controller (SBC) to Direct Routing](/microsoftteams/direct-routing-connect-the-sbc) and the following configuration settings to set up the trunks.
111114

0 commit comments

Comments
 (0)