How Much Is A Teams Phone License? | The Price Parts That Bite

You’re shopping for Teams calling and you keep seeing a tangle of names: “Phone Standard,” “Calling Plan,” “pay-as-you-go,” “Operator Connect,” “Direct Routing.” The price question looks simple. The bill rarely is.

Here’s the clean way to think about it: there are two layers. One layer turns Teams into a real phone system (PBX-style calling features). The other layer connects you to the public phone network so people can dial normal numbers (PSTN), with phone numbers, minutes, and taxes in the mix.

Once you split it like that, the license math gets calmer. You can price it per user, spot the add-ons, and stop paying twice for the same thing.

Start With The Two Layers: Phone Features Vs PSTN Calling

Teams can do meetings and in-app calls without touching the phone network. A Teams phone setup adds PBX features: voicemail, call transfer, call forwarding, call queues, auto attendants, and the ability to use desk phones or the Teams app as your main business line.

That PBX layer is what the “Phone Standard” style add-on covers. The PSTN layer is what gives you real phone numbers and the ability to call regular landlines and mobile numbers.

So when someone asks “What’s the Teams phone price?” they’re often mixing the two. A plan can include the PBX layer, the PSTN layer, or both.

Where The Per-User Price Starts

Microsoft sells Teams Phone Standard as a per-user add-on. On Microsoft’s business pricing page, Teams Phone Standard is listed at $10.00 user/month with annual billing, and Microsoft notes that a separate Teams license is required.

From there, you pick how you want PSTN calling handled. Microsoft’s pricing page lists these common bundles for the US “country zone 1” view:

• $13.00 user/month (annual billing) for pay-as-you-go calling
• $17.00 user/month (annual billing) for a domestic calling plan bundle
• $34.00 user/month (annual billing) for domestic + international calling

Those bundles roll the PBX layer and a PSTN approach into one SKU. You still need a Teams base license assigned to the user.

What Actually Changes Your Total Cost

The sticker price is only one piece. The final per-user cost shifts when any of these show up:

• Calling pattern: lots of outbound calls vs mostly inbound
• Geography: which countries you need numbers in, and where you need outbound minutes
• Phone number needs: one number per user, shared numbers, toll-free, extra DIDs
• Call routing model: Microsoft Calling Plans vs Operator Connect vs Direct Routing
• Advanced call flows: call queues, auto attendants, after-hours menus, shared voicemail
• Compliance and recording: if you must capture calls or keep long retention

If you already have a carrier contract you like, you may lean toward Operator Connect or Direct Routing. If you want one vendor and a simpler procurement path, Calling Plans can be the cleanest start.

How Much Is A Teams Phone License? Real Cost Math By Scenario

Let’s put real shape on it. The table below uses Microsoft’s listed per-user prices for the add-on and bundles, then shows what you still need to account for.

Scenario	What You Buy	What You Still Pay For
PBX features only (no PSTN minutes included)	Teams Phone Standard: $10 user/month (annual billing)	Phone numbers + PSTN via Calling Plans, Operator Connect, or Direct Routing
Metered PSTN calling through Microsoft	Teams Phone with pay-as-you-go calling: $13 user/month (annual billing)	Usage charges for outbound calls (metered), plus number-related items as applicable
Bundled domestic calling through Microsoft	Teams Phone with Calling Plan: $17 user/month (annual billing)	Edge cases: extra numbers, toll-free, special destinations, compliance add-ons
Bundled domestic + international calling through Microsoft	Teams Phone with domestic and international calling: $34 user/month (annual billing)	Extra numbers, toll-free, destination limits, and any specialized compliance items
Existing carrier stays in place (Operator Connect)	Teams Phone Standard: $10 user/month (annual billing)	Carrier per-user seat, numbers, usage, and any porting fees
SIP trunk with SBC (Direct Routing)	Teams Phone Standard: $10 user/month (annual billing)	SIP trunk costs + SBC licensing/hosting + numbers + implementation effort
Licenses that already include phone system capability	Some enterprise suites include the phone system app, depending on your tenant licensing	You still need a PSTN path: Calling Plans, Operator Connect, or Direct Routing
Frontline model (shared devices, shift work)	Frontline-eligible licensing + a Teams Phone option designed for frontline users	PSTN method, numbers, and call flow design still apply

Notice what’s missing from the table on purpose: a single “all-in” number that fits everyone. The same $10 add-on can turn into a tidy bill for one firm and a surprise bill for another, based on minutes, geography, and call routing choices.

The Three PSTN Paths And When Each Makes Sense

Microsoft Calling Plans

This is Microsoft acting as the PSTN carrier. You buy the bundle and you get a phone number plus a pool of outbound minutes based on the plan. It’s a clean procurement path when you want fewer vendors and you’re fine with Microsoft’s availability and minutes model.

On Microsoft’s Teams Phone page, the domestic calling plan bundle is described as including 3,000 outbound domestic minutes for the US, UK, and Canada, and 1,200 outbound domestic minutes for other markets where it’s sold. That’s the sort of detail that matters if you have mixed regions on one tenant.

Operator Connect

This keeps your carrier relationship, but plugs it into Teams with less infrastructure than a classic SBC build. It’s a strong fit when you need carrier-grade PSTN services, local number options, or regional coverage that beats what a single global plan provides.

You still need the phone add-on per user, and you’ll still pay the carrier for the PSTN side. The upside is flexibility and, often, better alignment with how your business already buys voice services.

Direct Routing

This is the “you bring the trunk” route. Your Teams users connect to the PSTN through a Session Border Controller (SBC), either hosted by you or a provider. It’s a good match for complex call routing, legacy PBX coexistence, contact center integrations, or strict regional telecom requirements.

The trade-off is more moving parts: trunking, SBC licensing, firewall rules, high availability planning, and ongoing monitoring. It can still pencil out well, but it’s not the simplest starting point.

How To Avoid Paying Twice For The Same Capability

Duplicate spend sneaks in through overlap. A few common traps:

• Buying a Calling Plan bundle for users who never call out. If they mostly receive calls, a metered option can land lower.
• Assigning phone add-ons to shared accounts. In many orgs, shared calling is better handled with resource accounts, call queues, and a smaller set of licensed users who actually place calls.
• Keeping old PBX seats while also assigning full Teams voice seats. During a migration it’s normal, but let it linger and the overlap becomes permanent.
• Ignoring number sprawl. Extra numbers, toll-free, and unused DIDs add up quietly.

A fast test: make a list of users who place outbound calls weekly. That list is often smaller than expected. Price those users first. Then design inbound call handling (main number, departments, after-hours menus) with shared call flows rather than giving every mailbox a public DID.

Licensing Requirements That Can Change The Answer

Teams Phone is not a stand-alone world. The user needs a Teams base license, and the phone capability can come from different combinations depending on your tenant. Microsoft lays out accepted licensing combinations in its Teams Phone licensing documentation, including paths where a Teams Enterprise license is paired with a phone add-on, and paths where a suite includes the phone system app.

This is the part people skip, then wonder why the admin center won’t let them assign phone features. If you want one official page to sanity-check the combinations, open Teams Phone licensing and match it against what you already own.

What You Pay For Beyond The License

The license line item is the loudest one. The quieter costs are the ones that bite when you didn’t budget for them.

Phone Numbers And Porting

Moving numbers from an old carrier can be smooth, or it can turn into a calendar problem. Porting timelines vary by carrier and region. It also affects cutover planning: you may pay for overlap while you keep the old trunks live until the port completes.

If you’re starting fresh with new numbers, you still need to decide: does every user get a direct line, or do you rely more on a main number plus extensions and call routing? That decision alone can swing monthly spend.

Call Queues, Auto Attendants, And Shared Call Handling

These features are why a “phone system” license matters. If you’ve run a PBX before, you know the basics: one public number, a menu, business hours, department queues, and fallback behavior when no one picks up.

Design this on paper before you buy seats. If you map your call flows first, you can often license fewer people while still giving callers a clean experience.

Emergency Calling And Location Needs

Emergency calling obligations vary by region, and a hybrid workforce adds complexity. If people use Teams from home, you need a plan for location handling and user guidance. This isn’t a “nice to have.” It’s part of rolling out voice responsibly.

Devices

Some teams live inside the Teams desktop and mobile apps and never touch a desk phone. Others want physical handsets in reception areas, warehouses, or shared spaces. Devices can be a one-time purchase, but they also affect rollout and training time.

Second-Order Costs Checklist

This table is a budgeting cheat sheet. Use it to scan for costs that often land outside the license line item.

Cost Driver	When It Shows Up	How To Keep It In Check
Outbound minutes	Sales teams, dispatch, heavy external dialing	Match plan type to real calling behavior; don’t bundle minutes for low-call users
Number sprawl	One DID per user, unused lines after org changes	Audit numbers quarterly; use shared call flows where it fits
Toll-free usage	Customer-facing inbound lines with high volume	Track inbound volume and compare toll-free pricing across PSTN paths
Carrier contract overlap	Migration periods, staged ports	Plan cutover waves; align port dates with training and device delivery
SBC and trunking (Direct Routing)	Legacy PBX coexistence or complex routing needs	Price managed SBC options; design for high availability from day one
Compliance recording	Regulated industries, trading desks, formal retention needs	Confirm requirements early; select a recording approach before rollout
Admin time and change control	Large orgs with frequent moves/adds/changes	Standardize call flow templates; document porting and number assignment rules

Pricing Examples You Can Reuse

These aren’t promises. They’re a way to think in “per-user blocks” while you budget.

Example 1: Knowledge Workers With Light Outbound Calling

If most users rarely dial out and you mainly need inbound routing plus internal calling features, you might buy the $10 per-user phone add-on for only the users who truly need external calling. Then choose a PSTN path that matches your region and call volume.

This is where teams often trim spend: a smaller licensed group handles external calls, while the rest keep Teams for meetings and internal collaboration.

Example 2: Sales Team With Consistent Outbound Calling

If the sales group dials external numbers daily, a per-user bundle like $17 (domestic) can be simpler to manage than metered calling. It also makes budgeting steadier because the outbound minute pool is built into the plan.

The sanity check is usage: if a big chunk of the group barely calls out, put them on a different track rather than paying a bundle for everyone.

Example 3: Multi-Region Org With Local Number Needs

If you need local numbers in several countries, or you already have a carrier that covers your footprint well, Operator Connect or Direct Routing may fit better than a one-vendor approach. The phone add-on cost stays the same per user, but the PSTN costs follow the carrier model you choose.

What To Check Before You Buy Anything

Run this list and you’ll avoid the “we bought it and it still doesn’t work” moment:

• Confirm each user has a Teams base license assigned.
• Decide which users truly need PSTN calling vs internal-only calling.
• Pick your PSTN path: Microsoft Calling Plans, Operator Connect, or Direct Routing.
• Inventory your current phone numbers, including main lines, DIDs, and toll-free.
• Sketch call flows: business hours, after-hours, queue behavior, and voicemail routing.
• Plan device needs: app-only, headsets, desk phones, shared area phones.
• Set a migration plan that avoids long overlap with your old PBX seats.

If you want a single official page that shows Microsoft’s current per-user Teams Phone pricing tiers in one place, use Microsoft’s Teams business pricing comparison and scroll to the Teams Phone section.

A Simple Way To Explain The Bill To A Non-IT Buyer

When someone asks for “the Teams Phone price,” give them this sentence:

You pay per user to add phone-system features, then you pay again for phone numbers and the ability to call regular phone numbers, with the second part changing based on minutes and carrier choices.

That’s the whole story. The rest is just picking the PSTN path that matches how your staff actually calls.