Microsoft Teams Phone Licensing: Calling Plans, Operator Connect & Direct Routing

Teams Phone: The Most Misunderstood Microsoft Licence Decision

Microsoft Teams Phone has become the dominant enterprise telephony platform in new deployments — yet its licensing model remains one of the most misunderstood in the Microsoft portfolio. Organizations routinely overpay by selecting the wrong calling architecture, failing to negotiate Phone System add-on pricing into their EA, or bundling Phone System into E5 licenses for users who would be better served with a lighter add-on model.

The fundamental complexity is this: Teams Phone requires two distinct components — the Phone System licence (call control and PBX functionality) and a connectivity component (how calls reach the PSTN). These can be sourced from Microsoft, from a carrier, or from your own infrastructure. Getting this architecture decision right before signing your EA can mean the difference between an optimized telephony estate and a multi-year overpayment.

This guide covers the full licensing stack: what Phone System includes, how Calling Plans, Operator Connect, and Direct Routing differ in cost and control, and the EA negotiation angles that most organizations miss. We'll reference the Microsoft 365 E5 bundling question specifically, since Phone System is one of the four pillars of E5 that often drives upgrade conversations.

The Teams Phone Licensing Stack

Understanding Teams Phone licensing requires separating three distinct layers. Confusion between these layers is the most common source of licensing errors.

Layer 1: Teams Client Licensing

The Teams application itself — desktop, mobile, and web — is included with Microsoft 365 E3, E5, M365 Business Standard, M365 Business Premium, and Microsoft 365 Apps for Enterprise (with the EU regional caveat). Teams client licensing enables chat, meetings, and basic VoIP calling between Teams users. It does not enable PSTN calls to external phone numbers.

Layer 2: Phone System Licence

Microsoft Teams Phone (formerly Phone System) is the cloud PBX component that enables enterprise telephony features: auto attendants, call queues, call transfer, voicemail, call recording, and — critically — the ability to place and receive calls to external PSTN numbers. Phone System is included in M365 E5 and can be added to E3 or lower suites as a standalone add-on.

The Teams Phone Standard add-on is priced at approximately $8/user/month at list, with EA discounts typically reducing this to $6.50-7.00/user/month. This is a critical data point: if Phone System is your primary reason for considering an E3-to-E5 upgrade, the add-on delivers the same capability at dramatically lower cost than the full E5 premium.

Layer 3: PSTN Connectivity

Phone System alone does not enable external calls. You still need PSTN connectivity — the ability to call and receive calls from numbers outside your Microsoft tenant. This is where the three connectivity architectures diverge.

Calling Architecture Options: A Decision Framework

Option 1: Microsoft Calling Plans

Microsoft provides PSTN connectivity directly through its cloud infrastructure. You purchase calling minutes from Microsoft — domestic calling plans, international calling plans, or pay-as-you-go dial-out. This is the simplest architecture: Microsoft manages everything, and there is no carrier relationship or on-premises infrastructure required.

Calling Plan pricing (approximate list):

• Domestic Calling Plan (120 minutes/month): ~$8/user/month
• Domestic Calling Plan (3,000 minutes/month): ~$12/user/month
• International Calling Plan (600 domestic + 600 international minutes): ~$24/user/month
• Pay-As-You-Go Plan: Variable, ~$0.02-0.04/minute depending on region

When Microsoft Calling Plans make sense:

• Organizations in supported countries (currently 33 countries) that want a pure Microsoft stack with no carrier management
• Small-to-mid enterprise without existing telco infrastructure or carrier relationships
• Organizations prioritizing simplicity over cost optimization
• Companies with low call volume where per-minute pricing is cost-effective

When Calling Plans are NOT the right choice:

• Organizations with existing carrier contracts or SIP trunks that are contractually locked or competitively priced
• Operations in countries not supported by Microsoft Calling Plans (many APAC, LATAM, and Eastern European markets)
• High call volume organizations where Microsoft's per-minute rates exceed carrier alternatives
• Organizations requiring geographic number porting from non-supported regions

Option 2: Operator Connect

Operator Connect allows approved telecom carriers to provision PSTN calling directly within the Microsoft Teams admin center. The carrier manages the SIP connectivity; Microsoft manages Teams Phone System. You work with your preferred carrier, but the provisioning and management interface is native Teams.

Operator Connect partners include AT&T, BT, NTT, Vodafone, Telstra, and approximately 80+ other approved carriers globally. The architecture eliminates the need for on-premises Session Border Controllers (SBCs) while maintaining the carrier relationship and potentially competitive calling rates.

Option 3: Direct Routing

Direct Routing connects Teams Phone System to your own PSTN connectivity via a Session Border Controller (SBC). You bring your own carrier — any SIP carrier globally — and control the telephony infrastructure. This is the most flexible and often most cost-effective architecture for large enterprises with established carrier relationships and existing SBC infrastructure.

Direct Routing total cost components:

• Teams Phone Standard licence per user ($8/month list)
• Certified SBC hardware or cloud SBC (Audiocodes, Ribbon, Oracle, etc.): $15,000-80,000 one-time depending on scale
• SBC maintenance and managed service costs: 10-15% of hardware annually
• Your existing carrier rates for PSTN calls

For organizations with 500+ phone users, Direct Routing typically delivers total cost of ownership 30-45% below Microsoft Calling Plans, particularly in markets where competitive carrier pricing is available. The SBC investment amortizes quickly at scale.

Teams Phone and M365 E5: The Bundle Trap

Phone System inclusion in Microsoft 365 E5 is one of the most frequently cited justifications for E5 upgrades. The logic from Microsoft's account team is seductive: "You'll need Teams Phone anyway — might as well get all the E5 security and compliance features at the same time."

The financial reality: M365 E5 costs approximately $21/month more than E3. Teams Phone Standard as a standalone add-on costs approximately $8/month. The E5 "bundled savings" for Phone System is therefore $13/month — but only if you would have paid for E5's other components (security, compliance, analytics) at the standalone rates anyway.

For most organizations, the E5 bundle makes sense for users who need both advanced security and Phone System — typically senior executives, compliance officers, and security-exposed roles. For general office staff who need calling but not Defender for Endpoint P2 or Purview eDiscovery Premium, Teams Phone Standard + E3 is almost always cheaper than E5.

The table illustrates why blanket E5 is often not cost-effective for the calling use case: E3 + Phone Standard provides Phone System at a lower total cost, and E3 + Phone Standard + Domestic Calling Plan (3,000 minutes) is nearly identical to E5 while excluding the security and compliance features that drive E5's premium.

Audio Conferencing: Often Overlooked, Often Misunderstood

Audio Conferencing is a separate Microsoft licence that enables dial-in participation in Teams meetings via traditional PSTN numbers. It is distinct from Phone System and is required when:

• Meeting participants dial in from phone handsets rather than using Teams apps
• Participants are in regions with poor internet connectivity requiring PSTN fallback
• Your organization requires consistent PSTN dial-in numbers for external participants

Audio Conferencing is included in M365 E5 and available as an add-on (approximately $4/user/month) for E3 users who need it. A common mistake is licensing Audio Conferencing for all users, when only meeting organizers — typically 30-40% of users in most organizations — need the licence. The licence attaches to the meeting organizer, not to participants. Bulk-licensing all users for Audio Conferencing is a predictable waste.

EA Negotiation: Phone System Pricing Levers

Teams Phone licensing is negotiable within the EA framework, though Microsoft's account teams rarely surface the discounting levers unprompted.

Lever 1: Commit Volume for Discount

Teams Phone Standard as a standalone add-on qualifies for volume discounts when committed in your EA. Organizations committing 500+ Phone System users can typically negotiate 15-22% below list. This requires including Teams Phone as an explicit line item in your EA amendment or renewal rather than purchasing ad-hoc through CSP or web direct.

Lever 2: Competitive Displacement

Cisco Webex Calling, RingCentral, Zoom Phone, and Avaya Cloud Office all compete for enterprise calling deployments. Microsoft values displacement of competitive telephony and provides discretionary discounting for organizations moving to Teams Phone from identified competitors. Documented competitive bids from Cisco or RingCentral create negotiation leverage — use them explicitly. This is the same competitive displacement lever discussed in our EA negotiation tactics guide.

Lever 3: Bundle with M365 EA Renewal

Timing Teams Phone licensing to coincide with your M365 EA renewal creates maximum negotiation leverage. Microsoft's appetite for EA expansion commitments is highest when you are renewing — you have the option to go to competitors, reduce commitment, or disaggregate. Anchoring Teams Phone into the renewal bundle as a new commitment item allows you to extract discount concessions across the portfolio.

Lever 4: Communicate Architectural Alternatives

Microsoft is aware that organizations considering Teams Phone have viable alternatives: Cisco Webex Calling, 8x8, Avaya, or simply maintaining on-premises Lync/SfB infrastructure. Demonstrating that you have genuinely evaluated Direct Routing with a third-party SBC, or that you have architectural flexibility to defer Teams Phone adoption, signals to Microsoft that their discount offer needs to be competitive. This is not bluffing — it is informed negotiation.

Regional Licensing Complexity

Teams Phone licensing has significant regional variation that enterprise architects must account for in global deployments.

Microsoft Calling Plans are available in only 33 countries as of 2026. Organizations with operations in APAC, LATAM, the Middle East, or Eastern Europe typically cannot rely on Microsoft Calling Plans for regional users — Direct Routing or Operator Connect are mandatory for these geographies. Operator Connect's carrier network has grown substantially and now covers most enterprise markets, making it the preferred architecture for organizations wanting carrier diversity without on-premises SBC investment.

The EU Teams unbundling decision (effective 2023) created a separate "Teams EEA" SKU for European markets where Teams must be licensed separately from Microsoft 365 Apps. This affects organizations deploying Teams Phone in European operations that use standalone Apps licensing — a Teams licence add-on may be required before Phone System can be provisioned. See the M365 Apps licensing guide for the full EU implications.