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.

Emergency calling: the topic nobody wants to think about

Emergency calling is the item that most quietly separates a working deployment from a liability. Requirements vary by country and by connectivity model:

• Dynamic emergency calling — Teams needs to know where the caller is so emergency services get dispatched to the right address, not the tenant's registered address. Configure Location Information Service (LIS) subnets, Wi-Fi BSSIDs, or switch-port maps in the Teams admin center so a call routes to the correct PSAP.
• Calling Plans in supported countries handle emergency routing end-to-end, but only if the address on the number is correct and dynamic locations are populated for on-network calls.
• Operator Connect — the operator provides emergency routing but relies on the address you register per number, plus whatever dynamic location the client asserts. Operators vary in whether they honour dynamic locations without extra configuration.
• Direct Routing — emergency routing is your problem, typically via an Emergency Location Identification Number (ELIN) integration on the SBC or via a partner service (Intrado, Bandwidth, RedSky).

A remote-worker fleet on Calling Plans still needs a policy: either force a registered address per user (home address, updated when they move) or require the client to prompt for a location the first time it sees a new network. Teams Phone Mobile and softphone-on-laptop scenarios are where deployments most often ship non-compliant.

Number lifecycle: the boring but real work

Numbers survive deployments, mergers, and licence changes. Plan how they move:

• Porting in. Every carrier has a lead time (2–8 weeks typical). Do the port after the user is Teams Phone-licensed and a temporary bridge number is in place; ports fail more often than not on the first attempt because of address mismatches with the losing carrier.
• Number reservation. Buy a small overhead of unassigned numbers per country so joiners get provisioned quickly. Unassigned Calling Plan numbers are billed differently by tenant type — check the current model before hoarding thousands.
• Number recycling. Have a policy for how long a leaver's number is quarantined before reassignment (30–90 days is typical). Otherwise the new hire gets calls for the person who left.
• Toll-free and service numbers. Get communications credits set up before the first tenant-wide voice event; they are pay-as-you-go and are the single most common cause of a botched all-hands call.

Common wrong turns

• Mixing carriers without a clear per-country policy. A user in Germany on Operator Connect and a user in the UK on Calling Plans is fine; the same user having two numbers via different paths is a support headache.
• Ignoring Communications Credits. Toll-free, outbound to unusual destinations, and Audio Conferencing dial-out all draw from the same credit pool. Auto-recharge should be on.
• Assuming Operator Connect gives you contact-centre capability. Some operators bundle it, most do not. If the requirement is a real contact centre, either use a certified Contact Center for Microsoft Teams solution or plan for Direct Routing.
• Overlooking regulatory identity checks. Several countries (France, Germany, India, UAE) require identity documentation before a number can be assigned or ported. Operators enforce this; plan for the paperwork.
• Skipping call quality dashboards. Teams Call Quality Dashboard shows every stream and every rating. Turn it on before the first outage; ramping it up mid-incident is too late.