Connect Microsoft Teams Direct Routing to Enfonica

Who does what

Setup happens in two places:

• The Enfonica Console. You create a Teams Direct Routing SIP domain, which is your SIP trunk, and the phone numbers your users call from.
• Your Microsoft 365 tenant. Your IT team or MSP verifies the SIP domain, assigns licenses, and configures Teams to use it.

You stay in control of Microsoft 365. Enfonica never needs admin access to your tenant.

Create a Teams Direct Routing SIP domain

Your SIP domain is ready as soon as you create it.

1. Sign in to the Enfonica Console, and open your project.
2. Go to Cloud SIP, and select New SIP domain.
3. For Type, select Teams Direct Routing.
4. Enter a SIP domain ID, and complete the steps to create the SIP domain.
5. Note the SIP domain's FQDN (fully qualified domain name). It's shown at the top of the SIP domain's page, next to SIP domain, in the format <name>.sip.enfonica.com. You'll use it in Microsoft 365.

Add your phone numbers

Each user needs a phone number to call from and be called on. You might also want more numbers for main business lines.

1. If you haven't created a regulatory listing yet, go to Phone Numbers > Regulatory listings, create one, and complete the steps. You need one before you can buy numbers.
2. Go to Phone Numbers > Purchase, search for a number, and select it to buy it.
3. On the number's page, under Call settings, in Incoming call handlers, select Add, and then select SIP.
4. Select Load balancer, and then select the load balancer named teams@<your FQDN>.
5. Select Save Changes.
6. Repeat these steps for each number you need.

To keep your current numbers, port them to Enfonica. Requesting a port takes about two minutes, and porting has zero service interruptions.

Verify the SIP domain in Microsoft 365

Your Global Administrator verifies the FQDN so that Teams can use it.

1. In the Microsoft 365 admin center, go to Settings > Domains, and select Add domain.
2. Enter your FQDN as the domain name, and continue.
3. For the verification method, select Add a TXT record, and continue.
4. Copy the TXT value. It starts with MS=.
5. In the Enfonica Console, open your SIP domain. In its Teams direct routing section, select Verify.
6. Paste the TXT value into TXT record value, and select Verify.
7. In the Microsoft 365 admin center, select Verify. If verification doesn't succeed, wait a few minutes and try again.
8. When you're asked how to connect your domain, select more options, then Skip and do this later, and then Continue.

You don't need to add any other DNS records. After the domain is verified, Teams can use it.

Configure Teams

Finish the connection in Teams with PowerShell. The Teams Direct Routing guide in the docs has a ready-to-run script for each step.

1. Create a Microsoft 365 user whose primary email address is on your FQDN, such as user@<your FQDN>.
2. Assign the user the free Microsoft Teams Phone Resource Account license. This activates the FQDN in Teams. You can remove the user after setup.
3. Sign in with Connect-MicrosoftTeams.
4. Create the dial plan for Australia. It converts the numbers your users dial into full international format.
5. Create the PSTN usage record and voice routing policy.
6. Create the voice route, with your FQDN as its gateway.
7. For each user, assign their phone number as a Direct Routing number in full international format, for example +61255501234. Then grant them the voice routing policy and dial plan.

Check that it worked

1. Open the Teams desktop app, and go to Calls. A dial pad appears.
2. Call a mobile from the dial pad. The mobile rings.
3. Call the user's Enfonica number from a mobile. The call rings in Teams.

If there's no dial pad, Microsoft 365 might not have finished applying your changes. Wait for it to catch up, and then restart the Teams app. To check why the dial pad is missing, you can also use Microsoft's Remote Connectivity Analyzer.

If calls don't work

Most problems after setup are in the Teams configuration, which your IT team or MSP fixes in your tenant. For each symptom and who fixes it, from 404 Not Found on incoming calls to a second outgoing call failing, see Teams Direct Routing calls fail or don't ring.

Questions