Microsoft Teams Phone PSTN Connectivity Guide: 3 Models

Compare Microsoft Teams Phone PSTN connectivity: Calling Plan, Operator Connect, Direct Routing. Per-user cost stacks, E911 ownership, migration complexity.

Fact-Checked & Lab-Verified

Microsoft Teams Phone is a PBX, not a phone service. That distinction decides whether your Teams rollout comes in on budget or bleeds money for three years. Teams Phone Standard gives you the PBX layer (queues, voicemail), but it cannot reach the public network on its own. You still have to buy PSTN connectivity, and the model you pick determines your per-user cost stack and who owns the work.

This guide covers Microsoft Teams Phone PSTN connectivity across the three models buyers actually choose: Microsoft Calling Plans, Operator Connect, and Direct Routing. The claim up front: the cheapest carrier quote is rarely the cheapest architecture. You have to normalize the complete licensing stack, licensing plus PSTN plus operations, before any per-user number means anything.

At a glance

  • Teams Phone Standard is the PBX layer only. PSTN access, phone numbers, minutes, and emergency calling come from a separate PSTN solution you select and pay for independently (Microsoft Learn, Apr 27, 2026).
  • Every user who needs a number needs two licenses. A qualifying Teams or Microsoft 365 license, plus the Teams Phone Standard add-on at $10/user/month, annual billing (Microsoft list, Oct 2026).
  • The three PSTN models differ in who carries the number. Microsoft as carrier (Calling Plans), a certified third-party operator (Operator Connect), or your own carrier behind a certified SBC (Direct Routing).
  • Emergency calling ownership moves with the model. Microsoft handles it in Calling Plans in available markets, Operator Connect includes dynamic emergency routing in the U.S. and Canada, and Direct Routing puts the routing obligation on you.
  • Normalize before you compare. Microsoft list prices cover the PBX layer only. Carrier, SBC, E911, tax, and hardware costs come from actual quotes, never from a vendor one-pager.

Three Teams Phone PSTN connectivity models converging into one PBX

What Teams Phone Actually Includes, and What It Doesn’t

Teams Phone Standard turns the Teams client into a cloud PBX: call control, voicemail, call park, call queues, auto attendants, and shared-device support. For a user who only calls other Teams users, that license is the whole job. The moment a call needs to reach the public switched telephone network, Teams Phone Standard stops being sufficient. Numbers, minutes, PSTN access, and emergency calling all come from a separate PSTN connectivity decision (Microsoft Learn, Apr 27, 2026).

That split trips up buyers who price Teams Phone like a per-seat UCaaS product. Compare the $10 line to a $25 all-in competitor quote and you will lose every budget review.

The licensing stack is two layers deep for most users. Layer one is the base: a qualifying Teams license or Microsoft 365 suite. Layer two is Teams Phone Standard at $10/user/month on an annual term with annual billing (Microsoft list, Oct 2026). Microsoft 365 E5 suites already include the Phone System entitlement, so E5 users skip layer two; everyone else pays it. Resource accounts, the accounts behind auto attendants and call queues, are licensed at $0 (o365hq, Oct 2026), which is one of the few line items in this stack that does not grow with headcount.

The Three Teams Phone PSTN Models in One Architecture

Microsoft sells one PBX and three ways to reach the network. They share a Teams admin center and a number-management surface, but the carrier relationship and the operational burden land in different places.

Model Who provides numbers and minutes How you manage it Best when
Microsoft Calling Plans Microsoft is the carrier. Numbers and calling plans are bought from Microsoft; minutes are pooled at the tenant level (Microsoft Learn, Oct 1, 2024). Teams admin center, one vendor, one invoice. Domestic calling, single-country footprint, lean IT staff.
Operator Connect A Microsoft-certified operator keeps the carrier relationship and manages the SBC and PSTN infrastructure on your behalf (Microsoft Learn, Jun 18, 2025). Teams admin center; the operator handles the carrier side. You have a preferred carrier, multiple countries, or want out of carrier management without running an SBC.
Direct Routing Your own carrier, connected through a certified session border controller you (or a partner) operate. Teams voice routing policies plus your SBC configuration. Existing carrier contracts, legacy PBX interwork, or custom call flows that the other two models cannot reach.

Calling Plans. Microsoft sells numbers and bundled minutes as add-ons to Teams Phone Standard. The US/UK/Canada bundles include 3,000 outbound domestic minutes per user/month; the domestic-and-international bundle covers the same 3,000 domestic minutes or 600 international minutes, whichever runs out first (CloudTalk, Aug 2026). Emergency calling is handled by Microsoft in the markets where Calling Plans are available. Country availability is the hard constraint: if Microsoft does not sell Calling Plans in a market, this model is off the table there.

Operator Connect. Your carrier keeps the account, provisions the numbers, and peers with Microsoft. You assign numbers in the Teams admin center but never touch an SBC. Operator Connect includes a dynamic emergency routing service in the U.S. and Canada (Microsoft Learn, Jun 18, 2025; Oct 1, 2024). Pricing is set by each operator, so there is no fixed per-user figure to quote here; every comparison runs on operator rate cards.

Direct Routing. Maximum control, maximum responsibility. You keep your carriers, contracts, and numbers, and you get legacy PBX interworking that the managed models cannot match. You also assume full responsibility for emergency call routing, either through an emergency routing service provider or SBC-based ELIN configuration (Microsoft Learn, updated Mar 22, 2026).

A fourth option exists for mobile-heavy workforces: Operator Connect Mobile, where a SIM-enabled mobile number doubles as the Teams number. Operators include AT&T, T-Mobile, Verizon, and Vodafone; pricing lives on the carrier pages, so check them directly before budgeting (Microsoft Learn, updated Oct 2026).

The Real Cost Stack per User per Month

Microsoft’s list prices are the starting line, not the total. For a typical knowledge worker, the monthly stack looks like this:

  • Base license. A qualifying Teams or Microsoft 365 license. After the July 2026 repricing, Microsoft 365 E3 with Teams lists at $39 and E5 at $60 (Microsoft, July 2026).
  • Teams Phone Standard. $10/user/month, annual billing. Skipped if the user sits on an E5 suite that already includes the entitlement.
  • PSTN connectivity. Pick one: Microsoft’s bundled SKUs, an Operator Connect operator’s rate card, or Direct Routing carrier costs plus SBC licensing, hosting, and support.
  • The invisible lines. Taxes and regulatory fees, E911 surcharges, toll-free numbers, porting fees, desk phones, headsets, and the internal hours for number administration. None of these appear in Microsoft’s list price, and all of them appear in your invoice.

Microsoft’s bundled add-ons, U.S. annual-billing list, October 2026: Teams Phone Standard $10, Phone with pay-as-you-go calling $13, Phone with domestic Calling Plan $17, Phone with domestic and international $34 (Microsoft list, Oct 2026). The qualifying base license is still required underneath each one. Pay the annual term monthly instead of annually and the subscription costs 5% more (Microsoft partner pricing, Apr 2025).

Normalize all three models to the same unit before comparing: full per-user monthly cost, fully loaded with taxes, numbers, E911, and the ops labor you will actually staff. An Operator Connect quote that beats Calling Plan by $4 a seat is not a $4 saving if it needs a half-time voice engineer you were not planning to hire. For a deeper look at how consolidation math works across vendors, see our UC consolidation savings guide.

The Direct Routing savings quote has a precondition. A vendor-published estimate from EPC Group credits PSTN-to-Teams migration with 40 to 60 percent savings (EPC Group), but that estimate is built on one assumption: you already run a certified-SBC practice. SBC hardware, integration, and ongoing operations land on top of the carrier rate, and none of them appear in the per-user quote. Price those lines before you compare, because a quote that values the SBC ops at zero will make Direct Routing look a third cheaper on paper and cost-neutral in year one. If you cannot name the person who owns the SBC today, Operator Connect is the overlooked middle path. The operator keeps the SBC and the carrier relationship while you manage numbers in the Teams admin center, which removes carrier management without requiring voice-ops headcount, and it is the path that disappears when buyers frame the choice as Calling Plans versus Direct Routing.

Microsoft’s 2025-2026 Price Changes and What They Signal

Two repricing events in eighteen months changed the economics of this decision, and both rewarded buyers who read the stack instead of the sticker.

On April 1, 2025, Microsoft raised Teams Phone Standard from $8 to $10 per user/month, a 25% increase and the first standalone price change since the product launched in 2017 (CRN, Nov 2024). The pay-as-you-go SKU moved to $13 in the U.S. and the domestic Calling Plan to $17 in the US/UK/Canada ($22 in other markets). Customers buying Teams Phone through Microsoft 365 E5 annual terms with annual billing saw no change, which widened the gap between the add-on path and the E5 path.

On July 1, 2026, Microsoft repriced the suites underneath: Microsoft 365 E3 with Teams rose from $36 to $39, E5 with Teams from $57 to $60. Standalone Teams and Copilot SKUs were excluded from the increase (Microsoft, July 2026). Existing customers keep current pricing until their next renewal, so your renewal date, not July 1, is the commercial deadline that matters (entechus, 2026).

The signal is plain: Microsoft prices the stack in layers, and each layer can move independently. A buyer who negotiated hard on Calling Plan pricing in 2024 absorbed the suite increase in 2026 anyway. Budget the whole stack, lock renewal dates into your calendar, and quote both billing frequencies before signing, since the monthly-billing premium compounds across every seat.

Emergency Calling and Dispatchable Location by Model

Emergency calling is where the three models diverge hardest, and it is the line item most buyers under-scope. Kari’s Law and RAY BAUM’S Act obligations attach to the enterprise regardless of which PSTN model you choose; the model only changes who does the technical work to satisfy them. Our enterprise E911 compliance checklist covers the full obligation set. Here is how responsibility splits:

  • Calling Plans. Microsoft provides emergency calling in the markets where Calling Plans are available (Microsoft Learn, Oct 1, 2024). Your job is keeping the location data accurate for every user and site, not building the routing.
  • Operator Connect. Includes a dynamic emergency routing service in the U.S. and Canada. The operator supplies the routing; you supply accurate location data and policies (Microsoft Learn, Jun 18, 2025).
  • Direct Routing. The enterprise assumes full emergency-call-routing responsibility. You provision an emergency routing service provider or configure SBC-based ELIN yourself, and you maintain the dispatchable-location data behind every number (Microsoft Learn, updated Mar 22, 2026). This is the model where E911 becomes a staffed operational function, not a checkbox.

Score E911 as an operations cost, not a feature comparison. A model that “supports” emergency calling while assigning you the routing work is not cheaper than a model that includes the routing. It just moves the cost into your headcount.

Remote workers are the compliance gap no Phone Standard license covers. On Sep 28, 2026, the FCC’s Public Safety and Homeland Security Bureau issued new NG9-1-1 guidance reminding multiline telephone system operators that accurate location information must accompany every 911 call, and put wireline carriers on notice to collect location data from MLTS customers (APCO International, Sep 2026). The guidance is MLTS-focused, but the enforcement direction is unmistakable, and hybrid work is where location data goes stale fastest. Teams can attach dynamic emergency locations to users, but nobody in Redmond validates your remote workers’ home addresses. A Teams Phone rollout with hundreds of home offices and no per-user address validation process creates exposure that the $10 license fee does not cure. Assign address ownership the same way you assign routing ownership: in writing, before go-live.

Choosing: Five Enterprise Profiles

Match the model to the estate, not to the quote. Five profiles cover most enterprise decisions:

  • Profile 1: Single-country domestic caller base. U.S. or UK/Canada footprint, lean IT, no carrier contracts worth preserving. Calling Plans win on simplicity: one vendor, one invoice, Microsoft handles numbers, minutes, and emergency calling. Compare it against our business VoIP phone system comparison before assuming Teams is the cheapest all-in seat.
  • Profile 2: Multi-country footprint with preferred regional carriers. Operator Connect. You keep carrier relationships where they matter (negotiated rates, local presence, regulated markets), manage numbers in the Teams admin center, and skip SBC operations entirely.
  • Profile 3: Existing carrier contracts or a legacy PBX to interwork. Direct Routing. Keep the contracts, keep the numbers, interwork the legacy estate through the certified SBC, and migrate on your own timeline instead of the carrier’s.
  • Profile 4: Mobile-first field workforce. Operator Connect Mobile. One number for the mobile and the Teams client, via AT&T, T-Mobile, Verizon, or Vodafone, with pricing checked on the carrier page before budgeting.
  • Profile 5: Survivability and compliance-driven voice. Direct Routing with survivable branch appliances for sites that must keep calling during a cloud interruption, or a hybrid: Calling Plans for standard offices, Direct Routing for regulated or high-availability sites. Mixed models are supported per tenant.

Many enterprises land on a hybrid. The mistake is picking the hybrid by accident, site by site, instead of designing it from these profiles up front.

Migration: Porting, Coexistence, and Number Strategy

Number migration is the part of the project that slips schedules. Porting thousands of numbers means coordinating with the losing carrier, validating the customer service record for every range, and sequencing cutovers so no site goes dark mid-port. Start the number inventory before you sign anything: every DID, toll-free, fax, alarm, and elevator line, with its current carrier and contract date.

Direct Routing earns its keep during coexistence. Because it interworks with legacy PBXs and existing trunks, you can keep the old estate on Direct Routing while standard users move to Calling Plans or Operator Connect, then decommission in phases. Buyers who skip this step port everything at once and discover, after the fact, which numbers belonged to devices nobody remembered.

Build the number strategy around where numbers live long-term. Operator Connect and Calling Plans assign numbers in the Teams admin center; Direct Routing manages numbers across the admin center and the SBC. Auto attendants and call queues ride on $0 resource accounts, so the contact-center-adjacent infrastructure does not scale with user licenses. Plan porting windows around business calendars, not vendor timelines, and keep the old trunks live until the new routing is verified under load.

When Each Model Fails

Every model has a failure mode that its sales pitch skips. Know them before the contract, not during the outage.

  • Calling Plans fail on geography and bargaining power. If Microsoft does not sell Calling Plans in a market you enter, those users need a different model, and you are now running two PSTN architectures. Single-carrier also means no competitive pressure on rates at renewal.
  • Operator Connect fails on operator variance. Per-user pricing is set by each operator and varies by market and contract, so the model you budgeted on paper can price differently in practice. Operator availability and capability differ by country. Vet the operator’s SLA and emergency routing in each market you deploy, not just headquarters. It also fails by omission: buyers frame the decision as Calling Plans versus Direct Routing and never price the middle path, which is the model that keeps the SBC off their plate.
  • Direct Routing fails on operational load. The certified SBC needs certificates, DNS, voice routing policies, monitoring, and someone who answers the page when calls stop. E911 routing is yours to build and maintain. Enterprises that buy Direct Routing for “flexibility” and staff it with nobody watch that flexibility turn into an on-call rotation for the network team. The vendor savings estimates only survive the math when this staffing already exists; without it, the SBC capital and integration spend absorbs the spread in year one.

Shared Calling is a cost mirage at enterprise scale. Microsoft’s Shared Calling lets many users share one number through a resource account, which looks like a way to skip per-user number costs. But every user still needs a Teams Phone license to be voice enabled, and the shared number rides on a resource account that needs its own license and a funded service number (Microsoft Learn, Configure Shared Calling, accessed Oct 2026). At 500 users you have saved one DID against 500 unchanged $10 licenses, while the single resource account becomes a single point of failure for inbound routing. There is an E911 tradeoff too: shared users have no dedicated number, so emergency callbacks route to the shared number and the dispatchable location must be configured per user anyway. Price Shared Calling as an operational simplification for light-call populations, not as a licensing discount.

Decision Checklist and Next Steps

Work through this checklist before requesting quotes. It takes an afternoon and saves a renewal cycle.

  • Inventory every number and its contract. DIDs, toll-free, fax, alarm, elevator. Note the carrier and expiration date on each. Numbers under contract push toward Direct Routing; clean estates open up the managed models.
  • Map countries to model availability. Confirm Calling Plan availability and Operator Connect operator presence in every country with users. One unsupported market forces a hybrid architecture.
  • Assign E911 ownership in writing. Name who maintains dispatchable-location data and who owns emergency routing under each model. If the answer is “IT will handle it,” price the hours.
  • Staff the SBC decision honestly. Direct Routing without voice-ops capacity is a risk, not a strategy. If you cannot name the person who owns the SBC, choose a managed model or a partner-operated SBC.
  • Normalize quotes to fully loaded per-user monthly cost. Same headcount, same minute profile, same three-year term: base license, phone license, PSTN, taxes, numbers, E911, hardware, and ops labor. Reject any bid that quotes the PBX layer alone.
  • Check renewal and billing-frequency exposure. Note every renewal date, quote annual and monthly billing, and model the next suite repricing into the three-year TCO.

Scored Decision Worksheet

Score each model 1 to 5 on every criterion (5 = best fit for your estate), multiply by the weight, and total the columns. Set the weights to your reality before scoring. If two models tie, pick the simpler operational model; complexity is a recurring cost that never shows up in the quote.

Criterion Weight (1-5) Calling Plan Operator Connect Direct Routing How to score it
Country coverage Your weight 1-5 1-5 1-5 5 if every user country is covered by the model; 1 if a key market is excluded.
E911 complexity Your weight 1-5 1-5 1-5 5 if the model absorbs routing and location work; 1 if you build and staff it yourself.
Existing carrier contracts Your weight 1-5 1-5 1-5 5 if the model preserves contracts and numbers cleanly; 1 if it forces early termination or renumbering.
SBC and voice-ops capacity Your weight 1-5 1-5 1-5 5 if the model needs no new headcount; 1 if it needs an SBC practice you do not have.
Three-year TCO Your weight 1-5 1-5 1-5 Score on the normalized stack only: base license, phone license, PSTN, taxes, numbers, E911, hardware, ops labor.

Bottom Line

Teams Phone is the PBX. The phone service is a separate decision, and the three PSTN models differ more in who does the work than in what they cost on paper. Normalize the full stack, assign E911 ownership in writing, and match the model to your estate instead of your quote sheet. The cheapest carrier bid is rarely the cheapest architecture.

Sources

  • Microsoft, “Pricing Updates for Microsoft 365 Copilot and Other Per User Products” (partner FAQ, April 2025): https://na.ingrammicro.com/Ingram/media/Global-Content/EN-GLOBAL/M/microsoft/docs/Copilot-and-Other-Pricing-Updates-Partner.pdf
  • Microsoft Learn, “Microsoft Teams add-on licenses”: https://learn.microsoft.com/en-us/microsoftteams/teams-add-on-licensing/microsoft-teams-add-on-licensing
  • Microsoft Learn, “PSTN connectivity options for Teams Phone extensibility” (Azure Communication Services docs): https://learn.microsoft.com/en-us/azure/communication-services/concepts/interop/tpe/teams-phone-extensibility-connectivity-cost
  • CloudTalk, “Microsoft Teams Phone Pricing 2026: The Real Stacked Cost Per User” (Aug 14, 2026): https://www.cloudtalk.io/blog/microsoft-teams-phone-system-pricing/
  • o365hq, “Microsoft Teams Phone: PSTN Options, PBX Migration and …” (Oct 2026): https://o365hq.com/blog/microsoft-teams-phone-a-new-modern-calling-solution
  • CRN, “Certain Microsoft Subscriptions Face 5 Percent Premium; Teams Phone, Power BI Price Increases Set” (Nov 2024): https://www.crn.com/news/ai/2024/certain-microsoft-subscriptions-face-5-percent-premium-teams-phone-power-bi-price-increases-set
  • entechus, “Microsoft 365 Prices Rise July 2026. Here’s What to Do” (2026): https://www.entechus.com/blogs/microsoft-365-prices-rise-july-2026.-heres-what-to-do
  • APCO International, “FCC Issues NG9-1-1 Guidance for MLTS, Service Providers and 9-1-1 Authorities” (Sep 2026, on the FCC Public Safety Bureau’s Sep 28, 2026 NG9-1-1 guidance for MLTS): https://www.apcointl.org/psc/fcc-issues-ng9-1-1-guidance-for-mlts-service-providers-and-9-1-1-authorities/
  • Microsoft Learn, “Configure Shared Calling” (accessed Oct 2026): https://learn.microsoft.com/en-us/microsoftteams/shared-calling-setup
  • Microsoft Learn, “Plan for Operator Connect” (accessed Oct 2026): https://learn.microsoft.com/en-us/microsoftteams/operator-connect-plan
  • Microsoft Learn, “Plan Direct Routing” (accessed Oct 2026): https://learn.microsoft.com/en-us/microsoftteams/direct-routing-plan
  • Microsoft Learn, “Plan and manage emergency calling” (accessed Oct 2026): https://learn.microsoft.com/en-us/microsoftteams/what-are-emergency-locations-addresses-and-call-routing
  • EPC Group (vendor-published; credits PSTN-to-Teams migration with 40 to 60 percent savings): https://www.epcgroup.net/what-is-the-difference-between-pstn-vs-pbx-which-one-do-you-need