Teams Calling Plans and Operator Connect

For organisations adopting Teams Phone, the choice of how to connect to the public telephone network (PSTN) is fundamental. Direct Routing is the most flexible but most operationally heavy option. Microsoft Calling Plans and Operator Connect are the simpler alternatives, suitable for most organisations that don't have specific reasons to go their own way.

Microsoft Calling Plans

With Microsoft Calling Plans, Microsoft is your phone carrier. Microsoft provisions phone numbers, terminates the PSTN, and you don't deal with any third party.

Strengths:

• Simple — one vendor for everything, configured entirely in the Teams admin center.
• No SBC to deploy and operate.
• Microsoft 365-native billing for both licences and call minutes.
• Fast onboarding — order, port, activate from the admin centre.

Weaknesses:

• Geographic coverage — Calling Plans are available in a limited (though expanding) set of countries. For each, you license a country-specific Calling Plan SKU per user.
• Pricing flexibility — Microsoft's tariffs aren't always competitive with what enterprises negotiate directly with carriers.
• Limited customisation — works the way Microsoft offers it; less room for special arrangements.

Calling Plan licensing is per user per month, separate from the Teams Phone licence itself. There are domestic-only and international plans, with metered or bundled-minute models.

Operator Connect

Operator Connect is a middle path: Microsoft has certified specific telecoms operators (BT, Verizon, NTT, Tata, Lumen, KDDI, many smaller regional operators) who provide PSTN connectivity using Microsoft-managed integration. From your side, it looks similar to Calling Plans — configured in the Teams admin center, no SBC of your own — but the carrier is a third party with its own pricing, billing, and contractual terms.

Strengths:

• No SBC operational burden — the operator runs the underlying infrastructure.
• Pick your operator — choose from certified partners based on coverage, price, support.
• Wider geographic coverage than Microsoft Calling Plans in many regions.
• Operator-native services — number management, emergency calling, regulatory features handled by the operator.
• Direct billing with the operator for call minutes (sometimes Microsoft-billed, depending on operator).

Weaknesses:

• Less control than Direct Routing for special configurations.
• Operator capabilities vary — some support compliance recording, advanced contact-centre integration; others don't.
• Geographic limits still depend on which operators serve which countries.

How to choose

A practical decision tree:

• Smaller organisation, single country with Microsoft Calling Plan coverage, no specific telco preferences → Microsoft Calling Plans.
• Multinational organisation, multiple countries, mix of coverage needs → Operator Connect with one or more operators.
• Existing strong carrier relationship you want to keep → Operator Connect (if your carrier is certified) or Direct Routing.
• Specialist requirements (contact centre, compliance recording, emergency calling complexity) → Direct Routing.
• Limited PSTN traffic, mostly internal Teams calls → Microsoft Calling Plans for simplicity.

Mixing models

A tenant can run all three models simultaneously in different regions or for different user groups. Many global enterprises do exactly this:

• Microsoft Calling Plans in countries with good coverage and small headcount.
• Operator Connect in regions with strong local operator relationships.
• Direct Routing in specific sites with contact centres or special needs.

The Teams admin center handles the routing — different users get different voice policies pointing at different connectivity paths.

For most new Teams Phone deployments, start with Operator Connect or Microsoft Calling Plans. Reach for Direct Routing only when there's a specific reason. The operational overhead difference is significant.