In this guide
Direct Routing suits businesses that need greater control, their own PSTN provider, integration with an existing PBX or analogue devices, or complex routing. Operator Connect simplifies connectivity through a participating operator, while Microsoft Calling Plan offers a more fully Microsoft-managed model where available. The right choice depends on the country, licences, numbers and the existing telephony that must be retained.
First distinguish Teams Phone from PSTN connectivity
Microsoft Teams can be used for meetings and internal collaboration without every user having external telephony. To make and receive calls through the public telephone network, users need the appropriate Teams Phone licences and one of the available PSTN connectivity options.
Microsoft supports several models and even allows them to be combined within the same tenant. This is useful for businesses with different countries, roles or legacy telephone systems.
When Direct Routing makes sense
Direct Routing connects Teams Phone to telephony infrastructure through a certified Session Border Controller. It allows a chosen PSTN carrier to be retained, an existing PBX or dedicated or analogue devices to be connected, and more complex routing rules to be applied.
This flexibility brings more technical requirements: a certified SBC, DNS, certificates, firewall and networking, voice routes and a clear support model. Direct Routing therefore requires design and testing as well as licence activation.
When to consider Operator Connect and Calling Plan
With Operator Connect, PSTN connectivity is provided by an operator participating in Microsoft’s programme, and users and numbers are managed more directly through Teams. Availability depends on the operator and country.
Microsoft Calling Plan is the most directly Microsoft-managed option where offered. It suits businesses seeking simplicity without specific requirements for an existing PBX, carrier or complex routing.
Questions that determine the architecture
- Do you want to retain your current provider or existing numbers?
- Are there PBXs, analogue lines, intercoms, fax machines or dedicated devices that must remain?
- Are different routes required by country, department or call type?
- Who will manage the SBC, voice policies and incidents?
- Do you need a phased migration or coexistence between Teams and existing telephony?
The best choice may be a combination
In complex environments, not every user needs to follow the same model. Microsoft’s documentation states that organisations can combine different PSTN connectivity options. This allows migration to be planned by country, team or use case instead of changing the entire telephone system at once.
For UniLoud, Direct Routing is particularly relevant when a business wants to connect Teams, telephony services, SBCs and existing installations within one plan.
Frequently asked questions
Does every user need Teams Phone?
No. Teams Phone is needed by users who will use its telephony capabilities. The exact licence combination depends on usage and must be confirmed before implementation.
Can the existing PBX remain?
Yes. In many scenarios, Direct Routing is used specifically for coexistence or integration with existing telephony infrastructure, provided the design and compatibility support it.
Is a certified SBC required?
Microsoft Teams Direct Routing requires a Microsoft-certified SBC. Certification and current requirements must be confirmed in Microsoft’s official documentation.
Related services and guides
- Microsoft Teams Direct Routing
- VoIP & SIP Trunk – UniLoud ITSP
- UniPBX – VoIP PBX
- Telephony in Teams: what we check before migration
Discuss your next step with UniLoud
Tell us which numbers, users and telephone systems you want to retain. We will map the Teams Phone model and migration approach that fits your environment.
