Microsoft Teams International Calling: What It Costs and When It Works

Microsoft Teams international calling runs about $20-$32 per user per month once you stack the required pieces: a Teams Phone license (around $8/user/month), plus a calling plan. The Domestic and International Calling Plan is $24/user/month and includes pooled minutes to roughly 196 countries. The Pay-As-You-Go plan is $8/user/month plus published per-minute rates. Teams Phone is built for companies already on Microsoft 365 that want one unified phone system. For an individual abroad who just needs to call a US number, the licensing math doesn't work, and a browser dialer at $0.02/minute beats it cleanly.

This guide covers what Teams Phone is, the three calling-plan options, real per-user cost math, when Operator Connect and Direct Routing make sense, and where Teams Phone is the right answer vs. where it isn't.

What Microsoft Teams International Calling Actually Is

Teams international calling is a paid add-on layer on top of Microsoft Teams. Teams by itself (the free or M365-bundled version) handles internal voice, video, and chat between Teams users at no extra cost. The minute it touches a phone number on the PSTN (the regular phone network), Microsoft requires a Teams Phone license and a calling plan.

Here's the stack:

Layer | What It Does | What It Costs

Microsoft 365 (Business or Enterprise) | Teams app, email, Office | Already in place for most buyers

Teams Phone (add-on license) | Lets a Teams user place/receive PSTN calls | ~$8/user/month standalone

Calling Plan (Domestic / Domestic+Intl / PAYG) | Buys the actual minutes | $8-$24/user/month + per-minute overage

Without Teams Phone, the Teams app can't dial a phone number. With Teams Phone but no calling plan, you have a Teams number that can't route minutes (you'd need Operator Connect or Direct Routing to bring your own carrier).

Teams Phone is included at no extra license cost in Microsoft 365 E5. If your company already pays for E5 across the org, the $8/user line item disappears, and you only pay for the calling plan. That's a meaningful piece of the math.

The Three Calling Plan Options

Microsoft sells three calling plans on top of Teams Phone. They differ in what minutes are included.

Plan | Monthly Price | What's Included | Best For

Domestic Calling Plan | $12/user | ~3,000 minutes/month, US and Canada only | Teams used inside North America

Domestic and International Calling Plan | $24/user | Domestic pool + international minutes to ~196 countries | Teams users who call abroad regularly

Pay-As-You-Go Calling Plan | $8/user | No included minutes; per-minute rates apply | Light users, occasional international calls

The Domestic and International plan is the right pick for companies doing real outbound international volume. The international minute pool is shared across the tenant; if you license 10 users, the pool covers the team. Microsoft's per-minute rates kick in once the pool is exhausted, varying by destination country.

The Pay-As-You-Go plan is the closest Microsoft offers to a per-minute model. You pay the $8/user/month license, then pay per-minute rates for every call. Microsoft's rates run from a few cents per minute for major destinations (UK landline, Canada) to over $1/minute for satellite or remote-country mobile.

What It Costs Per User Per Month

Real-world Teams Phone cost depends on whether Teams Phone is bundled in your M365 license and which calling plan you pick.

Scenario | Monthly Cost | What You Get

M365 E5 + Domestic Calling Plan | $12/user | E5 includes Teams Phone; calling plan adds 3,000 min US/CA

M365 E5 + Domestic and Intl Plan | $24/user | E5 includes Teams Phone; calling plan adds pooled international minutes

M365 E3 + Teams Phone + Domestic and Intl Plan | $32/user | Teams Phone standalone (~$8) + calling plan ($24)

Teams Phone Standalone + PAYG | $16/user + per-minute | Cheapest entry; per-minute rates apply

A 50-person company on M365 E3 picking Teams Phone + the international plan lands at roughly $1,600/month for phone capability alone, before per-minute overage. On E5, the same setup is $1,200/month because the Teams Phone license is bundled.

The international minute pool is the variable. A team using 20 hours/month across 50 users (about 24 min/user) stays inside the pool. A sales team making 4-5 hours/user/week burns the pool by mid-month and pays per-minute rates after that.

Microsoft also charges separately for phone numbers (user DIDs, toll-free numbers, conference bridges). That's another $1-$5/user/month, plus toll-free numbers carry inbound per-minute charges.

Operator Connect and Direct Routing

Operator Connect and Direct Routing are the two ways to bring an outside carrier into Teams Phone instead of buying Microsoft's calling plans. Both target larger deployments where carrier flexibility matters more than convenience.

Operator Connect is a Microsoft-managed integration with about 100 certified carriers (Verizon, BT, Lumen, Tata, Telstra, others). You keep your existing carrier contract for minutes; Microsoft handles the integration. Companies use Operator Connect when they have negotiated carrier rates that beat Microsoft's calling plans (common at scale) or need a specific in-country carrier for regulatory reasons.

Direct Routing is the do-it-yourself version. You connect a Session Border Controller (SBC) to Teams Phone and route calls through any SIP carrier. Most flexible, most operationally heavy: you need network engineering to maintain the SBC and carrier relationships. Common at telecom-heavy enterprises (banks, large healthcare networks, multinationals).

Both paths still require Teams Phone per user. The savings come from replacing Microsoft's calling plan with cheaper carrier minutes.

Path | Best For | Operational Lift

Microsoft Calling Plans | <500-user companies, single-country | Low — Microsoft handles everything

Operator Connect | Mid-market and enterprise with existing carrier | Medium — carrier contracts + Microsoft integration

Direct Routing | Large enterprise, multinational, regulated | High — SBC + carrier engineering required

For most readers searching "Teams international calling," Operator Connect and Direct Routing aren't the starting point. They're worth knowing if you're sizing a 1,000+ seat deployment with finance asking hard questions about per-minute cost at scale.

When Teams Phone Is the Right Answer

Teams Phone is the right answer when your company already runs on Microsoft 365 and wants a single unified communications platform.

Specifically, Teams Phone fits when:

Microsoft 365 is the primary productivity stack and Teams is already the daily-driver chat/meeting tool
You want one app for chat, video, meetings, and PSTN calling instead of stitching Zoom Phone or RingCentral onto Teams
IT wants a single admin surface for user provisioning, number management, and call analytics
Your company has E5 licenses (Teams Phone is bundled, removing one cost line)
You're consolidating from a legacy PBX and want to retire on-premises hardware

For an established Microsoft 365 customer at 100+ seats, Teams Phone is the path of least resistance. The licensing premium pays for itself in admin time and tool consolidation. New features (Copilot voice, transcription, post-call summaries) land in Teams first.

When Teams Phone Isn't the Right Answer

Teams Phone isn't the right answer for individual users, occasional callers, small teams without M365 commitment, or anyone who just needs to make one or two international calls without standing up a phone system.

It's overbuilt for:

An individual abroad needing to call a US number — there's no consumer-facing Teams Phone path. You can't buy a single Teams Phone license without a Microsoft 365 tenant behind it.
A 5-person startup not yet on Microsoft 365 — adopting Teams Phone forces a Microsoft 365 commitment that may not fit the rest of the stack.
An occasional caller (5-10 calls/year) — paying $20-$32/user/month for a service used a few times a year is wrong-shaped pricing.
A non-Microsoft shop — Google Workspace, Apple, or Linux-heavy teams are better served by Google Voice, Zoom Phone, or a per-minute service.
Employees abroad whose Teams license doesn't include Phone — common at companies that bought E3 + Teams base without adding Teams Phone, where one or two roaming employees need to call US numbers occasionally.

The last case is the most common one we see: someone working abroad whose company runs Teams, but whose license doesn't include the Phone add-on, who needs to call a US landline. Asking IT to add Teams Phone for occasional calls is a slow conversation. A per-minute browser dialer fills that gap without a procurement cycle.

Cheaper Alternatives for the Individual-Caller Case

If you landed here looking for "how do I call the US cheaply from abroad" and Teams Phone is overkill, three honest alternatives are worth knowing.

Service | Cost | Best For

Google Voice | Free US-to-US calling; international rates published by Google | Free for US-to-US legs if you have a US Google account already

WhatsApp | Free, app-to-app only | Both parties have WhatsApp; can't dial regular phone numbers

WorldDialer | $0.02/min to US landlines | Outside-US caller needing to dial a US landline from a browser

Google Voice works if you already have a US Google account and can keep a US phone number active. It doesn't work for outside-US users without a US account behind it.

WhatsApp is free, but only between two WhatsApp accounts (useless for calling US businesses, banks, government agencies, or anyone without the app). The broader picture is in the best international calling app comparison.

For an outside-US caller who needs a regular US landline (doctor's office, bank, government agency, a relative without WhatsApp), a per-minute browser service like WorldDialer covers the gap. $0.02/minute, no app, no subscription, no minimum buy-in. The full breakdown of per-minute vs. subscription pricing is in cheap international calls; the technical side of how this routing works lives in VoIP calling explained.

Teams Phone and WorldDialer aren't really competitors. They're products for two different buyers. Teams Phone serves the company building a unified communications platform. WorldDialer serves the individual who needs one phone call to a US number from outside the US, today, without a procurement cycle.

Make the Call

If your company already runs on Microsoft 365 and wants its phone system inside Teams, Teams Phone is a reasonable answer. Budget $20-$32/user/month plus per-minute overage, and expect a real implementation lift if you go the Operator Connect or Direct Routing route.

If you're an individual abroad who just needs to call a US landline, Teams Phone isn't the right shape. WorldDialer routes that call from anywhere for $0.02/minute. Browser-based, no app, no subscription, no minimums.

→ Try WorldDialer

---