You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/communications-gateway/configure-test-customer-teams-direct-routing.md
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,9 +35,9 @@ You must be able to sign in to the Microsoft 365 admin center for your test cust
35
35
36
36
## Choose a DNS subdomain label to use to identify the customer
37
37
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.
39
39
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/).
41
41
1. Choose a DNS label to identify the test customer.
42
42
- The label must be up to **eight** characters in length and can only contain letters, numbers, underscores, and dashes.
43
43
- You must not use wildcard subdomains or subdomains with multiple labels.
@@ -56,6 +56,9 @@ For example:
56
56
-`test.1-r1.<deployment-id>.commsgw.azure.com`
57
57
-`test.1-r2.<deployment-id>.commsgw.azure.com`
58
58
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
+
59
62
> [!TIP]
60
63
> Lab deployments have one per-region domain name. Your test customer therefore also only has one customer-specific per-region domain name.
Copy file name to clipboardExpand all lines: articles/communications-gateway/connect-teams-direct-routing.md
+8-5Lines changed: 8 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,7 +31,7 @@ You must be able to sign in to the Microsoft 365 admin center for your tenant as
31
31
## Enable Microsoft Teams Direct Routing support
32
32
33
33
> [!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).
35
35
36
36
1. Sign in to the [Azure portal](https://azure.microsoft.com/).
37
37
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
41
41
1. Select the **Overview** page for your resource.
42
42
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.
43
43
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
45
45
46
46
Before starting this step, check that the **Provisioning Status** field for your resource is "Complete".
47
47
@@ -52,11 +52,14 @@ Microsoft Teams only sends traffic to domains that you confirm that you own. You
52
52
1. Select your Communications Gateway resource. Check that you're on the **Overview** of your Azure Communications Gateway resource.
53
53
1. Select **Properties**.
54
54
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>`.
56
56
- 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>`
57
57
- A lab deployment has one service region and therefore one per-region domain name: `1-r1.<base-domain-name>`.
58
58
1. Note down the base domain name and the per-region domain name(s). You'll need these values in the next steps.
59
59
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
+
60
63
## Register the base domain name for Azure Communications Gateway in your tenant
61
64
62
65
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
66
69
> - You must register Azure Communications Gateway's base domain name.
67
70
> - Microsoft 365 automatically verifies the base domain name.
68
71
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).
70
73
71
74
If Microsoft 365 prompts you to verify the domain name:
72
75
@@ -105,7 +108,7 @@ To activate the base domain in Microsoft 365, you must have at least one user or
105
108
106
109
## Connect your tenant to Azure Communications Gateway
107
110
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).
109
112
110
113
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.
0 commit comments