Skip to content
Answer Stack
Open menu

What is the difference between Direct Routing and Operator Connect?

✓ Verified Last reviewed by AnswerStack Next review due Oct 17, 2026

Every claim is sourced below

Both connect Microsoft Teams Phone to the public phone network through a carrier other than Microsoft. With Operator Connect, the carrier belongs to a Microsoft program and has already built the link to Teams, so you switch it on in the Teams admin center and assign its numbers. With Direct Routing, you bring a carrier of your own choosing, and the link runs through a session border controller that someone has to set up and operate. That someone can be you, an integrator or a service provider. The difference is how much of the connection arrives ready-made and how much you can shape.

What the two have in common

Teams Phone is a phone system, and it needs a carrier before anyone can call an outside number. Microsoft's PSTN connectivity page lists four ways to add one. A Microsoft Calling Plan makes Microsoft the carrier. Teams Phone Mobile uses a mobile operator and the number on a user's SIM. Operator Connect and Direct Routing are the two routes that use a landline carrier other than Microsoft, which is why they get compared.

On both routes every user needs a Teams Phone license. When an operator other than Microsoft supplies the calling, Microsoft's licensing page requires no further license, because those costs come from the operator. So the Teams Phone license requirement is the same on both routes. The carrier's charge and the cost of the connection are the parts of what Teams Phone costs that vary. People make and take calls in the same Teams app on both. The differences are behind the app, in who builds the connection and who looks after it.

How Operator Connect works

Operator Connect is a program. A carrier joins it by completing the integration with Microsoft and being certified. Microsoft's planning page for Operator Connect says the operator manages the phone network infrastructure, and your administrators manage users from the Teams admin center.

Setting it up is a matter of choosing and assigning. You sign a contract with a participating operator and enable that operator in the admin center. You then get numbers, either new ones from the operator or existing ones ported over, and assign them to users. Microsoft lists a few prerequisites: Teams Phone licenses, users in Teams Only mode, the right administrator permissions, and an operator that serves the countries where you need service.

That last condition limits the choice of carrier. It has to be an operator in the program, and each one serves particular countries.

Support is shared, and Microsoft's planning page says where the line falls. Microsoft is responsible for Teams, the admin center and the integration with Operator Connect. The operator is responsible for the phone network connection, number provisioning and porting, the calling service and troubleshooting on its side.

How Direct Routing works

Direct Routing has no carrier list. In Microsoft's words, you can use any PSTN operator. The connection is made through a session border controller, or SBC, a device that sits between the carrier's network and Teams. Microsoft supports only the SBC models it has certified.

Somebody has to make that connection work, and the planning page for Direct Routing lists what it involves. The SBC needs one or more carrier trunks. It needs a public IP address that Teams can reach. It also needs a fully qualified domain name under a domain verified in your Microsoft 365 tenant, with a public DNS entry and a trusted certificate for that name. The firewall has to allow Microsoft's signaling and media traffic. Then come voice routes, dial plans and the routing policies assigned to users.

Microsoft gives the reasons an organization takes that on. The planning page says Direct Routing fits organizations that have an existing carrier relationship, need to connect a third-party PBX or analog devices, need advanced call routing, want more control over their telephony, or run complex or multinational deployments.

Support follows the equipment. Microsoft's guidance for Direct Routing is to contact the SBC vendor when a problem occurs. The vendor investigates and escalates to Microsoft if needed. When a provider runs the SBC for you, your first call is to that provider under its support terms.

Direct Routing doesn't have to mean your own hardware

The SBC for Direct Routing can be procured, installed and managed by the customer, an integrator or a Direct-Routing-as-a-Service provider. A company can use Direct Routing and never own a session border controller.

Atlantech Online is an example of a carrier that sells both routes. Its Teams Calling page says that setting up Direct Routing on your own creates costs for equipment, personnel and installation, and that its service includes Direct Routing. The page lists that service as "starting at $10 per user per month," with an enterprise dial plan, call queues and optional call recording. Its Operator Connect page lists a flat rate "as low as $3 per user/month" and says Atlantech manages the calling service and the SBCs. Both figures are starting prices for the carrier's service. They cover different sets of features, so the gap between them is not the price of Direct Routing.

With a provider like that, both routes are managed services. The customer isn't choosing between owning hardware and avoiding it. The customer is choosing how much the connection can be customized. Atlantech describes the trade in its explanation of Operator Connect: Operator Connect removes the work of managing SBCs, and in exchange an organization gives up some control over call routing, customization and integration with older systems.

Running the SBC yourself remains a third choice. It leaves the SBC configuration and the voice routing policies with your own team, along with the certificate and firewall work.

Point of comparison Operator Connect Direct Routing
Which carriers Operators in Microsoft's program, where they offer service A PSTN operator you choose
Who runs the session border controller The operator You, an integrator or a service provider
What you configure Enable the operator and assign numbers in the Teams admin center SBC connection, DNS, certificate, firewall, voice routes and policies, or a provider does it
What Microsoft says it suits A managed connection with no SBC of your own, or staying with an operator in the program An existing carrier, a third-party PBX or analog devices, advanced call routing
Who supports the connection The operator for calling, Microsoft for Teams Whoever runs the SBC, with the SBC vendor escalating to Microsoft

Choosing between them, or using both

Start with what has to connect to Teams. If the answer is people and phone numbers, and a carrier you're happy with is in the program for your countries, Operator Connect does the job with less to set up. If the answer includes an existing PBX, analog devices or call routing rules of your own, those are the cases Microsoft names for Direct Routing. The same goes for a carrier that isn't in the program. Mobile numbers and Microsoft's own calling plans are separate routes, covered in how to choose a PSTN connectivity option for Teams Phone.

You don't have to pick one for the whole organization. Direct Routing can run alongside the other routes in the same tenant, and Microsoft's planning page describes a common pattern. Operator Connect or a Calling Plan handles ordinary calling, and Direct Routing handles calls to a third-party PBX, analog devices and specialized routing.

Suppose a 200-person distributor has 170 office staff and a warehouse with an older phone system and analog handsets on the floor. The office staff can go on Operator Connect, with numbers assigned in the admin center. The warehouse can reach Teams through Direct Routing, assuming its equipment works with a certified SBC, and a provider can run that SBC. The office staff are Teams Phone users. The warehouse keeps its own phone system, and calls pass between it and Teams through the SBC. Each site uses the route that matches its equipment.

Sources

Microsoft - PSTN connectivity options

Microsoft

Primary source Verified Jul 17, 2026 Supports: The four PSTN connectivity models; Direct Routing uses any operator through a certified SBC procured, installed, and managed by you, an integrator, or a DRaaS provider; Operator Connect uses a certified third-party operator with no infrastructure to manage; Direct Routing works in any country or reg

“With the Direct Routing model, you can use any PSTN operator. Integration of your preferred PSTN operator's access to your tenant is achieved through a certified Session Border Controller (SBC) that is procured, installed, and managed by you, your integrator, or a Direct-Routing-as-a-Service (DRaaS) provider.”

Microsoft - Plan for Operator Connect

Microsoft

Primary source Verified Jul 17, 2026 Supports: Operator Connect operator manages the PSTN calling services and SBCs, saving hardware purchase and management; keep an existing operator or choose a participating one; faster deployment from the Teams admin center; requires Teams Phone license and TeamsOnly mode; availability limited to participatin

“Your operator manages the PSTN calling services and Session Border Controllers (SBCs), allowing you to save on hardware purchase and management.”

Plan Direct Routing - Microsoft Teams

Microsoft Learn

Primary source Verified Jul 17, 2026 Supports: Direct Routing connects a supported, customer-provided SBC to Teams Phone; use virtually any PSTN trunk; interoperate with third-party PBX and analog devices; keep an existing carrier contract; Teams Phone and Teams licenses required; SBC infrastructure requirements (certificate, FQDN/DNS, firewall

“Direct Routing lets you connect a supported, customer-provided Session Border Controller (SBC) to Microsoft Teams Phone.”

Session Border Controllers certified for Direct Routing - Microsoft Teams

Microsoft Learn

Primary source Verified Jul 17, 2026 Supports: Microsoft only supports certified SBCs with Direct Routing; certified vendors include AudioCodes, Ribbon, Oracle, Cisco, and TE-SYSTEMS; support escalation flows through the SBC vendor; certified firmware version requirement

“Microsoft only supports certified SBCs to pair with Direct Routing.”

Microsoft - Configure Operator Connect

Microsoft

Primary source Verified Jul 17, 2026 Supports: Enable an operator in the Teams admin center under Voice and Operator Connect, select countries, then the operator uploads numbers and you assign them to users; no SBC to configure; users need a Phone System license and TeamsOnly mode

“You can enable, edit, and remove operators in the Teams admin center. In the left navigation pane, go to Voice > Operator Connect.”

What is Teams Phone

Microsoft Learn

Primary source Verified Jul 17, 2026 Supports: Teams Phone is Microsoft's call control and PBX technology in Microsoft 365; internal Teams calls stay off the PSTN; a PSTN solution is separate from the Teams Phone license and both are required for external calls; any combination of PSTN solutions is supported

“A PSTN solution is separate from a Teams Phone license. A PSTN solution provides a customer's tenant with phone numbers and PSTN access to domestic, international, and emergency calling. The Teams Phone license entitles a Teams user to enhanced calling capabilities within the tenant and access to the PSTN solution.”

Microsoft Operator Connect vs Direct Routing

UC Today

Independent Verified Jul 17, 2026 Supports: Independent corroboration that Operator Connect is operator-managed with no local SBC, deploys in minutes from the Teams admin center, and offers less routing control, while Direct Routing keeps the SBC in the corporate data center, works with virtually any provider, and suits organizations needing

“Connecting and assigning phone numbers to users only takes minutes.”

Microsoft Teams Direct Routing vs. Operator Connect

Ribbon Communications

Independent Verified Jul 17, 2026 Supports: Independent corroboration that Direct Routing gives more flexibility and customer-managed SBC control for advanced features and carrier choice, while Operator Connect is provider-managed with numbers assigned from the Operators tab and is limited to participating operators

“Direct Routing allows companies to have more flexibility.”

What Is the Difference Between Operator Connect, Calling Plans and Direct Routing for Teams?

Pure IP

Independent Verified Jul 17, 2026 Supports: Independent corroboration that the carrier owns the connectivity in Operator Connect (fast deployment, no SBC) while Direct Routing is customer-managed with an SBC, and that Microsoft fully supports a hybrid mix of Operator Connect and Direct Routing in one tenant

“Yes, you can mix Direct Routing and Operator Connect within the same Microsoft Teams environment. Microsoft fully supports a hybrid configuration.”

Microsoft Teams: Calling Plans Vs Operator Connect Vs Direct Routing

Communication Square

Independent Verified Jul 17, 2026 Supports: Independent corroboration that Direct Routing requires additional infrastructure such as an SBC that adds to upfront cost and complexity, that the operator manages the SBCs under Operator Connect for cost savings, and that Direct Routing offers the most customization

“Direct routing requires additional infrastructure, such as a session border controller (SBC), which can add to the upfront cost.”

Microsoft Operator Connect Explained: What It Is, How It Works, and When to Use It

Atlantech Online

Supporting Verified Jul 17, 2026 Supports: Business-facing corroboration that Operator Connect is a Microsoft-certified, operator-managed calling model that removes the need for customer-managed SBCs; corroborated by [2] and [1]

“Operator Connect reduces operational overhead by eliminating the need for customer-managed Session Border Controllers (SBCs).”

Revision history

1 revision since publication
Originally published