
Microsoft Teams Direct Routing connects Teams Phone to a phone carrier or phone system you choose, through a Microsoft-certified session border controller (SBC), so people make and receive regular phone calls in the Teams app. It's the alternative to buying calling from Microsoft with Calling Plans.
What is Direct Routing?
Direct Routing links Teams to your SIP trunks or an existing PBX, which connects to the public phone network (PSTN). It suits organizations that want to:
- keep control of their phone numbers, routing and rates,
- keep their current carrier or phone system,
- bring calling into the Teams app they already use, and
- avoid moving to Microsoft Calling Plans.
How does Direct Routing work?
The SBC sits between Teams and your carrier or phone system. Usually virtual today, it:
- receives the call request from Teams once the user is verified,
- checks the user is allowed to make the call,
- routes it to your phone system or carrier, or keeps it in Teams,
- translates signaling and media between the two systems, and
- logs call details for security and auditing.
Each Teams user making calls needs a Teams Phone license. See What licensing Direct Routing needs.
How can you deploy Direct Routing?
Self-managed
You host certified SBCs on-premises or in the cloud. You get full control, but you need specialist skills, hardware or cloud oversight, and carrier agreements.
Direct Routing as a Service (DRaaS)
A provider runs the SBCs and setup for a monthly fee. For service providers, TeamMate's SIP Trunk Connector automates Direct Routing with SBCs included. See Direct Routing as a Service for service providers.
Direct Routing vs Calling Plans vs Operator Connect
| Calling Plans | Operator Connect | Direct Routing | |
|---|---|---|---|
| Who provides calling | Microsoft | A certified operator | The carrier or phone system you choose |
| SBC | Not needed | Run by the operator | Microsoft-certified SBC, yours or a provider's |
| Keep an existing PBX | No | No | Yes |
| Carrier choice | Microsoft only | Certified operators | Any carrier you connect |
Direct Routing's advantages are cost control, carrier choice, keeping the phone system you already have, and flexibility for complex routing. For the provider-side view, read Operator Connect vs Direct Routing for service providers.
How to implement Direct Routing in 4 steps
- Assess. Map users, locations, call volumes and compliance needs, and check your team's skills.
- Plan. Choose self-managed or DRaaS, and get the right Microsoft licenses.
- Configure and test. Set up certified SBCs, connect any existing PBX, and test call flows before rollout.
- Monitor and maintain. Run health checks and apply updates and security patches.
Keep learning
Frequently asked questions
What is Microsoft Teams Direct Routing?
Direct Routing connects Teams Phone to a carrier or phone system you choose through a Microsoft-certified session border controller (SBC), so people make and receive phone calls in the Teams app instead of buying calling from Microsoft.
How does Direct Routing work?
An SBC sits between Teams and your carrier or phone system. It checks the user is allowed to call, routes the call, translates signaling and media between the systems, and logs call details.
What license does Direct Routing need?
Each Teams user who makes and receives calls needs a Teams Phone license.
What are the ways to deploy Direct Routing?
Self-managed, with certified SBCs hosted on-premises or in the cloud, or Direct Routing as a Service, where a provider runs the SBCs and setup for a monthly fee.
How is Direct Routing different from Calling Plans and Operator Connect?
With Calling Plans, Microsoft is the carrier. With Operator Connect, a certified operator provides calling. With Direct Routing, you connect the carrier or phone system you choose, including an existing PBX.


