Operator Connect vs. Direct Routing: Which Microsoft Teams Architecture Delivers the Better Margin?

Enterprise demand for Microsoft Teams calling is no longer emerging — it's here. Teams Phone has crossed tens of millions of active PSTN users globally, and your enterprise customers are already asking which operator can support them. The real strategic question is not whether to enter this market, but how — and what that architecture decision costs you in margin, autonomy, and time-to-market over the next three years.

Operator Connect and Direct Routing represent two fundamentally different technical and commercial architectures. Each carries distinct implications for your margin structure, provisioning model, go-to-market speed, and competitive differentiation. If you've already worked through the foundational best practices for Microsoft Teams Direct Routing — the infrastructure requirements, SBC certification standards, and interconnect architecture — this article takes the next step: mapping both paths against the commercial criteria your product team needs to make, and defend, the right build decision.

Two Paths Into the Microsoft Teams Voice Market

Both Operator Connect and Direct Routing let service providers deliver PSTN calling to Microsoft Teams users. The difference is where control sits, who owns the infrastructure, and what your commercial relationship with Microsoft looks like.

• Direct Routing connects your existing PSTN infrastructure to Teams via a certified Session Border Controller (SBC). You own the routing, the billing logic, and the service definition. Microsoft provides the application layer; you provide the network.
• Operator Connect is a managed marketplace program run by Microsoft. Approved operators publish their PSTN offers directly inside the Teams Admin Center. Microsoft governs the interconnect; the operator provides PSTN access within defined constraints.

Neither is inherently superior. The right choice maps directly to your existing infrastructure, operational capacity, and target customer segment.

Direct Routing — Full Control Over Your PSTN Stack

Direct Routing is the architecture of choice for operators who want to maximize margin, differentiation, and control over their voice service. It leverages your existing SIP infrastructure and gives you direct ownership of the full voice path from PSTN to Teams tenant.

Technical Prerequisites for Direct Routing

Deploying Direct Routing requires:

• A certified Session Border Controller (SBC) — Microsoft maintains a published list of approved vendors. Certification is vendor- and firmware-specific: a device certified for one release is not automatically valid for the next.
• A direct SIP trunk between your SBC and Microsoft's PSTN gateway endpoint (sip.pstnhub.microsoft.com).
• TLS 1.2 and SRTP enforced for all signaling and media paths — no exceptions.
• A public FQDN and a valid TLS certificate registered on your SBC.
• Your customer's tenant must hold a Microsoft 365 Phone System license — factor this into your sales motion, as it directly affects purchasing decisions at the enterprise level.

Customer onboarding involves coordinating with the enterprise Teams admin to configure voice routing policies, PSTN usage records, and online voice routing policies. Timeline: days to weeks, depending on tenant complexity.

Margin Model and Operator Positioning

Direct Routing keeps the commercial relationship entirely between you and your customer. Operationally, this means:

• Set your own pricing — per-seat, per-minute, or bundled — independent of Microsoft's published rates.
• Full control over number porting, geographic routing, and emergency services routing.
• White-label potential: the service runs under your brand with no Microsoft commercial constraints on positioning.
• Higher ARPU per Teams seat compared to Operator Connect peers — because you own the full voice path with no revenue-share obligations upstream.

The counterweight: you own SBC maintenance, firmware lifecycle management, capacity planning, and 24/7 NOC coverage. Microsoft platform updates can silently break SBC compatibility, requiring rapid response from your engineering team.

Strategic Insight

If SIP trunks already form the core of your infrastructure offer, Direct Routing is the natural commercial extension — not a new product line. You can package Teams voice alongside your existing trunk capacity for a higher-margin, single-vendor bundle for your customers. Enreach's SIP trunk infrastructure for service providers is carrier-grade, geo-redundant, and pre-validated for Teams Direct Routing interconnect — reducing your certification timeline and SBC integration risk significantly.

Operator Connect — Simpler Entry, Tighter Commercial Constraints

Operator Connect reduces the technical barrier to the Teams market but exchanges operational control for convenience — a trade-off with direct implications for your margin floor and differentiation ceiling.

Qualifying for the Microsoft Operator Connect Program

Operator Connect is not open to all providers. Participation requires:

1. A formal application to Microsoft's Operator Connect program, including technical validation, regulatory review, and commercial agreement negotiation.
2. Completion of interoperability testing against Microsoft's infrastructure.
3. Commitment to Microsoft-defined SLA thresholds for PSTN availability and quality.
4. Integration of your provisioning systems with Microsoft's Operator Connect APIs for real-time number assignment and user management.

From application submission to first live customer: typically 6 to 12 months, depending on region, regulatory environment, and operator scale. If provisioning automation and API-layer orchestration are not already core competencies in your engineering team, the integration timeline extends further — a dimension covered in detail when examining how API automation becomes a margin lever for telecom operators.

What Operator Connect Gives Up

The customer experience is genuinely smooth — number assignment happens directly from the Teams Admin Center in minutes, with no technical coordination required from the enterprise IT team. That simplicity is real. But the structural trade-offs are equally real:

• Microsoft controls your commercial narrative. Your offer appears alongside competing operators in the same marketplace — differentiation is limited to coverage, pricing, and brand recognition within Microsoft's framework.
• No white-labeling. The program requires your offer to be visible as a third-party integration inside Microsoft's ecosystem.
• Revenue share and compliance terms are defined by Microsoft — not negotiable on a per-operator basis.
• PSTN routing logic is locked. You cannot implement custom routing at the network layer without stepping outside the Operator Connect framework entirely.

Side-by-Side Comparison: Key Decision Criteria

Choosing the Right Architecture for Your Go-to-Market

This decision is not purely technical — it is a commercial positioning choice with multi-year implications for your margin stack, product roadmap, and competitive differentiation.

You Already Operate SBC Infrastructure → Direct Routing First

If you already run SBCs for SIP trunking, hosted PBX, or Centrex delivery, Direct Routing is the fastest path to a Teams offer. Your core infrastructure is largely in place; the integration work is primarily configuration, certification validation, and interconnect testing.

More importantly, you can bundle Teams calling with your existing voice services — increasing ARPU per account without introducing new cost structures or external commercial dependencies. The margin model is structurally stronger: you control pricing, routing, and feature packaging end to end.

You're Entering Teams Without an SBC → Model the Trade-offs Carefully

For MVNOs or pure-play resellers without SBC infrastructure, Operator Connect can appear to be the low-friction path. But the 6–12 month onboarding window and Microsoft's commercial constraints deserve rigorous financial modeling before commitment. Key questions to resolve before signing:

• Can you build or lease SBC capacity and enter via Direct Routing instead?
• Is there a wholesale Direct Routing provider you can partner with while building your own infrastructure?
• What is the long-term ARPU impact of operating under Microsoft's commercial framework versus owning your own voice path?

The Hybrid Architecture — Serving Two Segments Simultaneously

A growing number of operators are moving toward a dual-track strategy: Direct Routing for enterprise customers who require customization, control, and deeper integration; Operator Connect for SMBs who prioritize self-service simplicity. This approach increases operational complexity but widens your addressable market and reduces revenue concentration risk.

The architecture selection becomes a market segmentation tool — not just a technical choice.

Strategic Insight

Call data is only as valuable as the business systems it feeds. Enterprises that connect Teams calling to Salesforce, HubSpot, or Microsoft Dynamics report significantly higher platform adoption and lower churn likelihood — because voice becomes embedded in workflows rather than isolated in a separate tool. Including CRM connectivity in your Teams bundle from day one shifts your offer from telephony commodity to productivity infrastructure. Learn how CRM integration reduces churn and increases ARPU for service providers — and how to position it commercially as part of your Teams voice package.

FAQ

Can a service provider offer both Direct Routing and Operator Connect simultaneously?

Yes. Microsoft allows operators to participate in both programs independently, and both can run in parallel for different customer segments. In practice: Direct Routing for enterprise accounts requiring customization and routing control; Operator Connect for SMBs prioritising simplicity and self-service provisioning. The operational overhead increases, but the total addressable market expands proportionally.

What specifically makes an SBC "certified" for Microsoft Teams Direct Routing?

Microsoft certifies SBCs at the intersection of vendor and firmware version. A device certified for firmware version X is not automatically valid on version X+1. Operators must actively track Microsoft's published certification matrix and manage firmware upgrade cycles proactively — SBC-Teams interoperability can degrade silently following a Microsoft platform update, with no automated alerting to the operator.

Does Operator Connect prevent value-added services from being layered on top of Teams calling?

Not entirely, but it constrains the network layer. Services such as call recording, conversation analytics, AI-powered summaries, or CRM integration can still be delivered at the application layer — independently of the PSTN routing path. What Operator Connect limits is the ability to inject services or routing logic at the network level. Direct Routing gives operators significantly more latitude for network-layer value-added services.

How does Teams Phone Mobile change the architecture decision?

Teams Phone Mobile (TPM) is a third architecture — an extension of Operator Connect that allows a mobile SIM to serve as the primary Teams calling identity. It requires operators to hold both an Operator Connect certification and mobile network capabilities. For MNOs and some MVNOs, TPM represents a compelling fixed-mobile convergence (FMC) play within Teams. Program qualification requirements are materially more stringent than standard Operator Connect, making it a longer-horizon consideration rather than an immediate go-to-market option.

Build Your Teams Voice Offer on the Right Foundation

Your Teams go-to-market decision has a longer operational lifespan than most product launches. Getting the architecture right from the start — Direct Routing, Operator Connect, or a hybrid model — determines your margin structure, differentiation ceiling, and provisioning scalability for years.

Enreach works with service providers and operators at every stage of their Teams voice strategy — from architecture evaluation to SIP infrastructure provisioning and integration design.

Talk to a Microsoft Teams specialist — schedule a technical briefing

Related articles:

• CRM Integration for Service Providers: Boost Business with Connect CRM
• API Economy for Telcos: Automation as a Margin Lever