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
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,24 +49,24 @@ You must be able to configure the tenant with at least two user or resource acco
49
49
50
50
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.
51
51
52
-
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/).
52
+
1. Work out the per-region domain names for connecting to Microsoft Teams Direct Routing. These 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/).
53
53
1. Choose a DNS label to identify the test customer.
54
-
- The label must be up to **eight** characters in length and can only contain letters, numbers, underscores, and dashes.
54
+
- The label must be up to **nine** characters in length and can only contain letters, numbers, underscores, and dashes.
55
55
- You must not use wildcard subdomains or subdomains with multiple labels.
56
56
- For example, you could allocate the label `test`.
57
57
> [!IMPORTANT]
58
-
> 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.
58
+
> 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 `contoso12.1r1.a1b2c3d4e5f6g7h8.commsgw.azure.com` is 48 characters.
59
59
1. Use this label to create a _customer subdomain_ of each per-region domain name for your Azure Communications Gateway.
60
60
1. Make a note of the label you choose and the corresponding customer subdomains.
61
61
62
62
For example:
63
63
- Your base domain name might be `<deployment-id>.commsgw.azure.com`, where `<deployment-id>` is autogenerated and unique to the deployment.
64
64
- Your per-region domain names are therefore:
65
-
-`1-r1.<deployment-id>.commsgw.azure.com`
66
-
-`1-r2.<deployment-id>.commsgw.azure.com`
65
+
-`1r1.<deployment-id>.commsgw.azure.com`
66
+
-`1r2.<deployment-id>.commsgw.azure.com`
67
67
- If you allocate the label `test`, this label combined with the per-region domain names creates the following customer subdomains for your test customer:
68
-
-`test.1-r1.<deployment-id>.commsgw.azure.com`
69
-
-`test.1-r2.<deployment-id>.commsgw.azure.com`
68
+
-`test.1r1.<deployment-id>.commsgw.azure.com`
69
+
-`test.1r2.<deployment-id>.commsgw.azure.com`
70
70
71
71
> [!IMPORTANT]
72
72
> 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.
@@ -80,7 +80,7 @@ To route calls to a customer tenant, the customer tenant must be configured with
80
80
81
81
1. Sign into the Microsoft 365 admin center for the customer tenant as a Global Administrator.
82
82
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):
83
-
1. Register the first customer subdomain (for example `test.1-r1.<deployment-id>.commsgw.azure.com`).
83
+
1. Register the first customer subdomain (for example `test.1r1.<deployment-id>.commsgw.azure.com`).
84
84
1. Start the verification process using TXT records.
85
85
1. Note the TXT value that Microsoft 365 provides.
86
86
1. (Production deployments only) Repeat the previous step for the second customer subdomain.
@@ -140,7 +140,7 @@ To activate the customer subdomains in Microsoft 365, set up at least one user o
140
140
141
141
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.
142
142
143
-
- 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 step sets up _derived trunks_ for the customer tenant, as described in the [Microsoft Teams documentation for creating trunks and provisioning users for multiple tenants](/microsoftteams/direct-routing-sbc-multiple-tenants#create-a-trunk-and-provision-users).
143
+
- Set the PSTN gateway to the customer subdomains for Azure Communications Gateway (for example, `test.1r1.<deployment-id>.commsgw.azure.com` and `test.1r2.<deployment-id>.commsgw.azure.com`). This step sets up _derived trunks_ for the customer tenant, as described in the [Microsoft Teams documentation for creating trunks and provisioning users for multiple tenants](/microsoftteams/direct-routing-sbc-multiple-tenants#create-a-trunk-and-provision-users).
144
144
- Don't configure any users to use the call routing policy yet.
Copy file name to clipboardExpand all lines: articles/communications-gateway/connect-teams-direct-routing.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -59,9 +59,9 @@ Microsoft Teams only sends traffic to domains that you confirm that you own. You
59
59
1. Select your Communications Gateway resource. Check that you're on the **Overview** of your Azure Communications Gateway resource.
60
60
1. Select **Properties**.
61
61
1. Find the field named **Domain**. This name is your deployment's _base domain name_.
62
-
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>`.
63
-
- 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>`
64
-
- A lab deployment has one service region and therefore one per-region domain name: `1-r1.<base-domain-name>`.
62
+
1. Work out the _per-region domain names_ for connecting to Microsoft Teams Direct Routing. These use the form `1r<region-number>.<base-domain-name>`.
63
+
- A production deployment has two service regions and therefore two per-region domain names: `1r1.<base-domain-name>` and `1r2.<base-domain-name>`
64
+
- A lab deployment has one service region and therefore one per-region domain name: `1r1.<base-domain-name>`.
65
65
1. Note down the base domain name and the per-region domain names. You'll need these values in the next steps.
Copy file name to clipboardExpand all lines: articles/communications-gateway/interoperability-teams-direct-routing.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -59,10 +59,10 @@ For each customer, you must:
59
59
60
60
1. Choose a suitable subdomain. The label for the subdomain must:
61
61
- Contain only letters, numbers, underscores, and dashes.
62
-
- Be up to **eight** characters in length.
62
+
- Be up to **nine** characters in length.
63
63
- Not contain a wildcard or multiple labels separated by `.`.
64
64
> [!IMPORTANT]
65
-
> 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 `contoso1.1-r1.a1b2c3d4e5f6g7h8.commsgw.azure.com` is 48 characters.
65
+
> 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.
66
66
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.
67
67
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).
0 commit comments