Teams Direct Routing Setup

Before you start: VoIP Toolbox controls the DNS zone for your Direct Routing domain. When Microsoft gives you a TXT verification value, paste it into this page while signed in so we can publish the verification record for you.

Confirm Microsoft 365 admin rights

You can only add new domains if you are signed in to the Microsoft 365 admin center as a Global Administrator.

Sign in to the Microsoft 365 admin center.
Go to Users > Active Users.
Open your user and verify that you have the Global Administrator role.

Microsoft reference: About admin roles in Microsoft 365.

Add and verify the tenant subdomain

Add your Direct Routing domain as a domain in the customer tenant. Log in to see your account's value; here is a placeholder example:

example-123.probeXX.voiptoolbox.net

Publish the Microsoft TXT verification record

Open PowerShell with the Microsoft Graph PowerShell SDK available.
Connect to the customer tenant with permissions to add domains.

Connect-MgGraph -Scopes "Domain.ReadWrite.All" -TenantId <tenant-id>

Add your Direct Routing domain to the customer tenant.

New-MgDomain -Id example-123.probeXX.voiptoolbox.net

Load the directory management module and retrieve Microsoft's TXT verification value.

Import-Module Microsoft.Graph.Identity.DirectoryManagement
(Get-MgDomainVerificationDnsRecord -DomainId example-123.probeXX.voiptoolbox.net | Where-Object {$_.RecordType -eq "Txt"}).AdditionalProperties.text

Copy the output, usually in the form MS=ms12345678, into the VoIP Toolbox form above and publish the TXT record.
After VoIP Toolbox confirms the TXT record has been published, run the Microsoft domain confirmation command.

Confirm-MgDomain -DomainId example-123.probeXX.voiptoolbox.net

When Confirm-MgDomain completes successfully, return to VoIP Toolbox and select Confirm DNS to remove the temporary TXT record.

Important: The base URL and the subdomain for the individual client have to be on the same Microsoft tenant before you can add a Direct Routing derived trunk.

Activate the subdomain in Teams

After the domain is verified, activate it by adding at least one Teams licensed user or resource account that uses the new subdomain.

Accepted account types

User account with Office 365 E1, E3, E5, A3, or A5.
User account with Microsoft 365 E3, E5, A3, or A5.
User account with Office 365 F1 or F3, or Microsoft 365 F1 or F3.
User account with Microsoft 365 Business Basic, Standard, Premium, G3, or G5.
User account with a Microsoft Teams Shared Devices license.
Resource account with a Microsoft Teams Phone Resource Account license.

UPN or SIP address examples

The account's UPN or Skype for Business on-premises SIP address must use the same FQDN as the new subdomain.

teams-test-user{{ $teamsSuperTrunkFqdn }} aa-main{{ $teamsSuperTrunkFqdn }} cq-support{{ $teamsSuperTrunkFqdn }}

Add the derived trunk to a Teams voice route

Add the tenant's derived trunk FQDN to the voice route that should handle VoIP Toolbox test calls.

Open the Teams Admin Center.
From the left siderail, expand Voice, then select Direct Routing.
Open the Voice routes tab.
Select Add, or select an existing voice route.
In the voice route profile, under SBCs enrolled, select Add SBCs.
In the right side panel, under Add SBC as derived trunk, enter example-123.probeXX.voiptoolbox.net.
Select Add, then select Apply.

Create VoIP Toolbox Teams tests

Once the domain and voice route are ready, create Pulse checks for the Teams destinations you want to validate.

Teams users

Place scheduled test calls to direct user numbers or routing targets.

Auto attendants

Confirm main numbers answer and menu paths stay reachable.

Call queues

Monitor queue entry points and validate that Teams accepts the call.

Go to Add Assurance Endpoint.
Set SIP Target to Microsoft Teams Direct Routing.
Choose Test Call (RTP metrics are collected automatically).
Enter the Teams user, auto attendant, or call queue destination you want to test.