Introduction: The Business Voice Discontinuation and What It Means for Your Licensing
In April 2022, Microsoft discontinued Business Voice, its simplified calling SKU for small and mid-sized businesses. Organizations that had relied on Business Voice found themselves facing a more complex licensing landscape: Teams Phone System, Teams Phone Standard, various calling plan options, Operator Connect, and Direct Routing alternatives. The transition created confusion across enterprise IT teams, especially regarding cost implications and the "right" calling solution for different organization sizes.
After twenty years of Microsoft licensing negotiations, I've watched organizations struggle with this transition because they don't understand the new licensing structure or how it compares to the Business Voice model they relied on. Many are paying 40-60% more for calling capabilities than necessary because they haven't mapped out the full cost picture or negotiated calling plans into their EAs.
This guide walks you through the post-Business Voice landscape. I'll explain Teams Phone System, Teams Phone Standard (the successor to Business Voice), the various calling plan options, alternative PSTN connectivity models, and the cost implications of each. More importantly, I'll show you how to negotiate the right calling solution into your EA at economical rates.
Business Voice Discontinuation: What Happened and Why
Business Voice (announced 2019, discontinued April 2022) was Microsoft's all-in-one calling solution for smaller organizations. It bundled Teams Phone System, calling plans, audioconferencing, and voicemail into a single $20/user/month SKU. For small businesses, it was economical and straightforward.
Why Microsoft Discontinued Business Voice
Microsoft's rationale: Business Voice masked the true cost of calling infrastructure and prevented organizations from optimizing their calling architecture based on actual needs. Some organizations needed high-volume PSTN calling; others needed only voicemail and internal Teams calling. Business Voice's bundled approach meant customers were overpaying for capabilities they didn't use.
More pragmatically, Microsoft wanted to expand its calling portfolio: Operator Connect offers carrier-supplied PSTN connectivity for large enterprises. Direct Routing enables organizations to bring their own PSTN carriers. These models generate higher margins for both Microsoft and its partners than the Business Voice bundled approach.
The discontinuation was a business decision, not a technical one. Organizations using Business Voice didn't lose any calling capabilities; they just lost the simplified all-in-one pricing model.
Business Voice Migration Path (2022-2026)
Microsoft offered a migration path for existing Business Voice customers through April 2024. Organizations could:
- Upgrade to Teams Phone System + Standard Calling Plan: Roughly equivalent to Business Voice but now with separate licensing lines ($5-8 for Teams Phone System + $12-15 for calling plan).
- Move to Operator Connect: Partner-supplied PSTN connectivity, often at lower cost than Teams Calling Plans for high-volume calling.
- Implement Direct Routing: Bring-your-own-carrier model for organizations with existing PBX investments.
If your organization is still running Business Voice licenses (post-April 2024), you've either grandfathered them or converted to one of these alternatives. Either way, understanding the new calling landscape is critical for your next EA renewal.
Teams Phone System: The Foundation
Teams Phone System is the core PBX functionality that enables voice calling in Teams. It's the successor to Skype for Business Server and replaces on-premises PBX infrastructure with cloud-native calling.
What Teams Phone System Includes
- Internal calling: Users can call other Teams users within the organization for free, unlimited internal calling.
- Call forwarding and simultaneous ring: Users can configure call forwarding to other devices or simultaneous ringing to multiple endpoints.
- Call transfer and conference: Users can transfer calls, place calls on hold, and conduct ad-hoc multi-party conferences within Teams.
- Voicemail: Integrated Teams voicemail with transcription.
- Auto-attendants and call queues: Organizations can build IVRs, call flows, and queues for inbound routing.
- Call recording and compliance: Call recording with transcription; integration with compliance workflows.
What Teams Phone System Does NOT Include
Critically, Teams Phone System does not include PSTN connectivity—the ability to make or receive calls from external telephone numbers (your traditional "phone service"). If you want users to call external numbers or receive calls from external callers, you need to add a calling plan or bring PSTN connectivity via Operator Connect/Direct Routing.
Teams Phone System Licensing
Teams Phone System is typically included in E5 Compliance and sold as a standalone add-on ($5-8/user/month for E3/E5 users, depending on EA terms). It's not included in E3 base licensing.
Critical Distinction
Teams Phone System ≠ calling. Teams Phone System is the internal phone system. To actually place calls to external numbers, you need to add a calling plan (Microsoft Teams Calling Plan) or connect via a carrier (Operator Connect / Direct Routing). This distinction confuses many organizations.
Teams Phone Standard: The Successor to Business Voice
Teams Phone Standard is Microsoft's bundled SKU that combines Teams Phone System + Standard Calling Plan + Audioconferencing. It's the spiritual successor to Business Voice, though the licensing and cost structure differ.
Teams Phone Standard Includes
- Teams Phone System: Full PBX functionality (see above).
- Unlimited National Calling: Unlimited outbound calling to numbers within the user's country. International calling is typically billed per-minute.
- Audioconferencing: Dial-in conference bridge capabilities.
- Voicemail and transcription: Unified voicemail with AI-driven transcription.
- Call analytics and monitoring: Detailed call quality and usage reports.
Teams Phone Standard Licensing and Cost
Teams Phone Standard typically costs $8-12/user/month (depending on EA terms and region). For organizations that need basic calling infrastructure (internal PBX + ability to reach external numbers), Teams Phone Standard covers the requirements at significantly lower cost than licensing Teams Phone System and calling plans separately.
Teams Phone Standard vs. Business Voice Cost Comparison
Business Voice (discontinued) was roughly $20/user/month all-in. Teams Phone Standard is $8-12/user/month. The apparent savings are offset by the reality that many organizations now realize they don't need Teams Phone System for all users—they only need it for users who take calls. This segmentation has actually driven down average costs across many organizations.
The Full Calling Landscape: Teams Calling Plans, Operator Connect, and Direct Routing
Teams Calling Plan (Standard PSTN Connectivity)
Microsoft Teams Calling Plan is Microsoft's direct PSTN connectivity offering. It's a per-minute or bundle model for outbound calling, typically priced as:
- Unlimited National Calling Plan: Unlimited outbound calling within the user's country, typically $12-15/user/month.
- International Calling Plan: Adds international dialing, typically $15-18/user/month.
- Pay-as-you-go Calling: Per-minute billing for organizations with low calling volumes. Typically $0.003-0.01 per minute.
Teams Calling Plans are included in Teams Phone Standard, so you don't pay separately for them if you license Teams Phone Standard. However, if you're licensing Teams Phone System only (without the Standard bundle), you need to add calling plans separately.
Operator Connect: Carrier-Supplied PSTN (Often Lower Cost for Large Deployments)
Operator Connect is a model where Microsoft partners with telecom carriers (e.g., Comtech, PCCW, Vodafone, etc.) to provision PSTN connectivity directly to your Teams Phone System. Instead of using Microsoft's calling plans, you're using the carrier's network.
Why Operator Connect?
- Cost savings: For high-volume calling organizations (500+ users with heavy calling), Operator Connect often delivers 20-40% cost savings vs. Teams Calling Plans because carriers compete on price.
- Carrier features: Access to carrier-native features (fax, local number provisioning, SIP trunking integration) without Microsoft's limitations.
- Licensing simplification: You license Teams Phone System from Microsoft and pay the carrier directly for PSTN connectivity—cleaner cost separation.
Operator Connect Limitations
- Carrier availability: Not all carriers and regions support Operator Connect. You're dependent on carrier availability.
- Onboarding time: Carrier provisioning takes 4-8 weeks, longer than Microsoft calling plans.
- Smaller-scale cost inefficiency: Operator Connect pricing is optimized for organizations with 100+ calling users. Below that, Microsoft calling plans are often cheaper.
Direct Routing: Bring-Your-Own-Carrier
Direct Routing allows organizations to connect their existing on-premises SIP trunks or cloud-based SIP providers directly to Teams Phone System, bypassing Microsoft and Operator Connect entirely.
Why Direct Routing?
- Cost control: Organizations with existing SIP trunks from their legacy PBX or VoIP provider can reuse those trunks with Teams Phone System.
- Feature parity: Retain advanced PBX features (call routing, IVR logic, etc.) from existing phone systems.
- Regulatory requirements: Some industries require domestic PSTN connectivity (Direct Routing can enforce this better than cloud-only solutions).
Direct Routing Limitations
- Technical complexity: Requires SIP trunk provisioning, network configuration, and ongoing management. Not suitable for organizations without telecom expertise.
- Support burden: You're responsible for troubleshooting voice quality issues—Microsoft support is limited if the SIP trunk is the problem.
- Licensing cost: While PSTN cost may be lower, you're licensing Teams Phone System from Microsoft ($5-8/user/month) in addition to your carrier costs.
Teams Rooms Licensing: The Often-Forgotten Calling Component
Organizations with conference rooms need Teams Rooms licensing for video conferencing and device management. Rooms don't typically need calling plans unless the room needs to place outbound calls (e.g., for hotline features or conference bridge calling).
Teams Rooms Pro (typically $7-10/room/month) includes Teams Phone System, but if you want the room to make external calls, you need to add a calling plan. Many organizations overlook this and discover mid-deployment that their rooms can't place calls to external numbers.
Teams Rooms Calling Best Practice
Assign calling plans only to rooms that have documented calling requirements (e.g., "this room needs to dial into customer conference bridges"). Don't blanket assign calling to all rooms—it's unnecessary cost and adds license complexity.
Negotiating Teams Phone and Calling Plans Into Your EA
Leverage Point 1: Demand Clarity on Calling Architecture
When Microsoft recommends Teams Phone + calling plans, push back with specificity: "How many users actually need PSTN calling? Are we retaining any legacy PBX systems that could use Direct Routing? Do we have conference rooms that need calling?" Force Microsoft to justify the calling architecture rather than assuming universal licensing.
Leverage Point 2: Model Operator Connect for Large Deployments
If you have 500+ users with regular calling needs, get a quote from an Operator Connect carrier (e.g., Comtech, PCCW) before accepting Microsoft's Teams Calling Plan pricing. In most enterprise scenarios, Operator Connect undercuts Microsoft's rates by 25-35%, and the carrier can negotiate favorable multi-year terms.
Leverage Point 3: Right-Size Calling to Users Who Actually Call
Many organizations assign Teams Phone + calling plans universally to all M365 users, even those who don't make external calls. Segment your population: executive and sales teams need calling. Finance and HR teams don't. This segmentation can reduce your calling licensing costs by 40-50%.
Leverage Point 4: Bundle Calling Into Base Pricing for EA Leverage
If you're in an EA renewal with a large M365 commitment (5,000+ users), propose bundling Teams Phone Standard (or Teams Phone System + calling plans) into your base EA pricing at a blended rate. Microsoft will often discount significantly to ensure predictable recurring revenue.
Common Teams Phone and Calling Licensing Mistakes
Mistake 1: Assigning Teams Phone System to All Users Without Calling Plans
Organizations license Teams Phone System across their entire user base without realizing that users also need calling plans to actually call external numbers. This results in users having the PBX infrastructure but no way to reach outside the organization. Clarify: who needs calling plans? Not everyone.
Mistake 2: Not Evaluating Operator Connect Pricing
For enterprises with 500+ calling users, Operator Connect pricing is frequently 20-35% cheaper than Teams Calling Plans, but many organizations never request quotes because they assume Microsoft is the only option. Always get competitive bids.
Mistake 3: Overlooking Conference Room Calling Requirements
Many organizations deploy Teams Rooms without planning for calling. Conference rooms are then unable to dial out to partner calls or conference bridges. Late in the deployment, teams discover missing room calling plans and scramble to add them at full retail pricing.
Mistake 4: Bundling Business Voice Licensing Without Updating Your EA
Some organizations still license Business Voice (grandfathered post-April 2024) because "it's easier than untangling the new calling model." Meanwhile, they're paying $20/user/month for calling when Teams Phone Standard ($8-12/month) would cost less. Conduct an inventory of Business Voice licenses; if you have any, plan a migration within your next EA renewal.
Conclusion: Strategic Teams Phone Licensing as a Cost Lever
The discontinuation of Business Voice created complexity, but it also created opportunity. Organizations no longer overpay for bundled calling they don't use. Instead, the new landscape—Teams Phone Standard, Operator Connect, Direct Routing—allows you to architect calling infrastructure aligned with your actual needs and budget.
The key is understanding what you actually need: Which users require external calling? What volume? What geographies? Do you have existing telecom infrastructure that could use Direct Routing? With those answers, you can choose the right calling model (Teams Calling Plan for small to mid-market, Operator Connect for large enterprises, Direct Routing for special cases) and negotiate it into your EA at favorable rates.
Most organizations don't optimize calling because it seems complex. In reality, it's a simple decision tree: identify calling needs, evaluate cost models, choose the best fit, negotiate into your EA. The savings potential is 30-40% of your current calling spend for most organizations willing to audit and optimize.
Ready to Optimize Your Teams Phone Licensing?
Our Microsoft 365 Optimization service includes a comprehensive calling architecture audit. We'll identify which users actually need calling, evaluate Operator Connect rates for cost savings opportunities, and design the optimal calling model for your EA. Engage our team for a strategic consultation on Teams Phone and calling plan licensing.
Reduce Calling Costs Through Strategic Architecture
We'll audit your Teams Phone usage, evaluate Operator Connect pricing, and design a calling model optimized for cost and performance.
Start Your Calling ReviewThe Microsoft licensing briefing — 3 minutes, every Friday
Used by 500+ procurement and IT teams. Independent analysis, no vendor spin.
No spam. Unsubscribe any time.