Connect Azure Communications Gateway to Microsoft Teams Direct Routing
After you deploy Azure Communications Gateway and connect it to your core network, you need to connect it to Microsoft Teams Direct Routing by following the steps in this article.
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.
- 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.
Using Azure Communications Gateway for Microsoft Teams Direct Routing requires provisioning the details of your customers and the numbers that you assign to them on Azure Communications Gateway. You can do this with Azure Communications Gateway's Provisioning API (preview) or its Number Management Portal (preview). If you're planning to use the Provisioning API:
- Your organization must integrate with the API
- You must know the IP addresses or address ranges (in CIDR format) in your network that should be allowed to connect to the Provisioning API
You must have Reader access to the subscription into which Azure Communications Gateway is deployed.
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.
Enable Microsoft Teams Direct Routing support
Note
If you selected Microsoft Teams Direct Routing when you deployed Azure Communications Gateway, skip this step and go to Find your Azure Communication Gateway's domain names for connecting to Microsoft Teams Direct Routing.
- Sign in to the Azure portal.
- In the search bar at the top of the page, search for your Communications Gateway resource and select it.
- In the side menu bar, find Communications services and select Teams Direct Routing to open a page for the service.
- On the service's page, select Teams Direct Routing settings.
- Fill in the fields, selecting Review + create and Create.
- Select the Overview page for your resource.
- 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.
Find your Azure Communication Gateway's domain names for connecting to Microsoft Teams Direct Routing
Before starting this step, check that the Provisioning Status field for your resource is "Complete".
Microsoft Teams only sends traffic to domains that you confirm that you own. Your Azure Communications Gateway deployment automatically receives an autogenerated fully qualified domain name (FQDN) and regional subdomains of this domain.
- Sign in to the Azure portal.
- In the search bar at the top of the page, search for your Communications Gateway resource.
- Select your Communications Gateway resource. Check that you're on the Overview of your Azure Communications Gateway resource.
- Select Properties.
- Find the field named Domain. This name is your deployment's base domain name.
- 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>and1-r2.<base-domain-name> - A lab deployment has one service region and therefore one per-region domain name:
1-r1.<base-domain-name>.
- A production deployment has two service regions and therefore two per-region domain names:
- 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 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.
Follow the instructions to add a domain to your tenant. Use the base domain name that you found in Find your Azure Communication Gateway's domain names for connecting to Microsoft Teams Direct Routing.
If Microsoft 365 prompts you to verify the domain name:
- Select DNS TXT records as your verification method with Add a TXT record instead.
- Select Next, and note the TXT value that Microsoft 365 provides.
- Provide the TXT value to your onboarding team as part of Provide additional information to your onboarding team.
Don't try to finish verifying the domain name until your onboarding team confirms that DNS records with the TXT value have been set up.
Provide additional information to your onboarding team
Before your onboarding team can finish onboarding you to the Microsoft Teams Direct Routing environment, you need to provide them with some additional information.
- Wait for your onboarding team to provide you with a form to collect the additional information.
- Complete the form and give it to your onboarding team.
If you don't already have an onboarding team, contact azcog-enablement@microsoft.com, providing your Azure subscription ID and contact details.
Finish verifying the base domain name in Microsoft 365
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.
- Sign into the Microsoft 365 admin center as a Global Administrator.
- Select Settings > Domains.
- Select the base domain.
- On the Choose your online services page, clear all options and select Next.
- Select Finish on the Update DNS settings page.
- Ensure that the status is Setup complete.
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 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.
Microsoft 365 should automatically verify these domain names, because you verified the base domain name.
Activate 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.
Connect your tenant to Azure Communications Gateway
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.
Use Connect your Session Border Controller (SBC) to Direct Routing and the following configuration settings to set up the trunks.
- For a production deployment, set up two trunks.
- For a lab deployment, set up one trunk.
| Teams Admin Center setting | PowerShell parameter | Value to use (Admin Center / PowerShell) |
|---|---|---|
| Add an FQDN for the SBC | FQDN |
The regional domain of Azure Communications Gateway |
| Enabled | Enabled |
On / True |
| SIP signaling port | SipSignalingPort |
5063 |
| Send SIP options | SendSIPOptions |
On / True |
| Forward call history | ForwardCallHistory |
On / True |
| Forward P-Asserted-identity (PAI) header | ForwardPAI |
On / True |
| Concurrent call capacity | MaxConcurrentSessions |
Use default |
| Failover response codes | FailoverResponseCodes |
Use default |
| Failover times (seconds) | FailoverTimeSeconds |
Use default |
| SBC supports PIDF/LO for emergency calls | PidfloSupported |
On / True |
| Media bypass | MediaBypass |
Off / False |
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
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for