Teams Phone System Enterprise Guide 2026 | EPC
Expert Insight from Errin O'Connor
29 years Microsoft consulting | 4x Microsoft Press bestselling author | Former NASA Lead Architect | 150+ enterprise PBX-to-Teams Phone migrations across healthcare, finance, and government
Quick Answer
Microsoft Teams Phone System in 2026 is a fully mature cloud PBX replacement that handles enterprise-grade voice workloads for organizations of any size. It supports three PSTN connectivity options: Microsoft Calling Plans (simplest, best for small deployments), Direct Routing (most flexible, best for enterprises with 1,000+ users), and Operator Connect (carrier-managed, best for mid-market).
The system includes auto-attendants, call queues, voicemail transcription, call park, presence-based routing, and compliance recording through certified partners. Migration from legacy PBX systems (Cisco, Avaya, Mitel) typically takes 8-16 weeks for a 1,000-user deployment and delivers 30-50% TCO reduction over 3 years. EPC Group has completed 150+ PBX-to-Teams migrations with zero business disruption.
Microsoft Teams Phone System Guide 2026
Microsoft Teams Phone System is the enterprise voice platform built into Microsoft Teams. It replaces legacy PBX hardware with cloud-based calling using Direct Routing, Calling Plans, or Operator Connect. EPC Group is a 29-year Microsoft consulting firm. We have migrated 200+ enterprises from PBX to Teams Phone. Last updated: 2026 · Read time: ~12 min
Key facts
- Three PSTN connectivity options: Direct Routing (your carrier via SBC), Calling Plans (Microsoft as carrier), Operator Connect (certified carrier partners in the Teams admin center).
- Teams Phone System license required — included in Microsoft 365 E5; available as add-on for other plans.
- Auto-attendants and call queues replace legacy IVR and ACD systems.
- Compliance recording is supported through certified partners (NICE, Verint, ASC Technologies).
- Dynamic E911/E112 routes emergency calls to the correct local PSAP based on user network location.
- EPC Group has delivered Teams Phone migrations for 200+ enterprise organizations across multiple countries.
PSTN connectivity options
The connectivity decision is the most important architectural choice in a Teams Phone deployment. Get it wrong and you will either overspend on carrier costs or under-deliver on geographic coverage.
Direct Routing
Direct Routing connects Teams Phone to your carrier using a Session Border Controller (SBC). You keep your current carrier contracts. You keep your existing phone numbers.
This option gives you full control over carrier selection, pricing, and coverage. It is the right choice for enterprises with existing carrier relationships, multinational deployments, or locations where Microsoft Calling Plans are not available.
Microsoft Calling Plans
Microsoft is the carrier. You buy domestic or international calling minutes directly from Microsoft. No SBC is required. This is the simplest option technically.
It is best for smaller deployments and regions where Microsoft offers competitive per-minute rates. Check country availability before selecting — Calling Plans cover fewer countries than Direct Routing.
Operator Connect
Operator Connect is the middle path. Certified carrier partners connect directly to Microsoft through the Teams admin center. You choose a carrier from the list, provision numbers in the admin center, and the carrier handles the PSTN connection.
No SBC to manage. Available in more countries than Calling Plans. EPC Group recommends Operator Connect when enterprises want carrier flexibility without Direct Routing complexity.
Multinational PSTN architecture
Large multinational organizations rarely use a single connectivity option globally. EPC Group designs hybrid PSTN architectures that match each region to the right connectivity method:
- Direct Routing with local carriers in regions where Calling Plans are unavailable or too expensive.
- Calling Plans in regions where Microsoft offers competitive rates and call patterns are simple.
- Operator Connect where carrier relationships and SLAs are strategically important to the business.
This hybrid approach optimizes cost and carrier relationships across the entire global voice estate.
Multi-site enterprise capabilities
Teams Phone has specific features for multi-site enterprise deployments:
- Location-based routing. Route calls through the local PSTN gateway for regulatory compliance. Required in some countries to prevent toll bypass.
- Dynamic emergency calling (E911/E112). Route emergency calls to the local PSAP based on the user's detected network location. Automatic location detection from corporate network signals.
- Local number assignment. Assign numbers from each country's local carrier for professional local presence in each market.
- Centralized administration. Manage all sites from the Teams admin center with delegated administration permissions per region.
- Survivable Branch Appliance (SBA). Maintain PSTN calling at branch sites that temporarily lose cloud connectivity. SBA provides local call handling without the cloud connection.
Auto-attendants
Auto-attendants handle inbound calls with menu-driven routing — a cloud replacement for legacy IVR systems. They route callers to the right destination based on their menu selection, time of day, or dial-by-name input.
Auto-attendant design principles
- Keep menu depth to 3 levels maximum — deeper menus frustrate callers
- Provide a path to a live agent at every level
- Configure separate greetings for business hours and after-hours
- Use dial-by-name directories for callers who know their contact
- Nest auto-attendants only when organizational structure requires routing across divisions
Call queues
Call queues route inbound calls to available agents in a defined order. They replace the ACD (automatic call distributor) functionality of legacy PBX systems.
Queue routing methods
- Attendant routing. Ring all agents simultaneously. First to answer gets the call.
- Serial routing. Ring agents one at a time in a fixed order.
- Round robin. Distribute calls evenly across all available agents.
- Longest idle. Route the next call to the agent who has been idle the longest.
Set overflow routing (after a maximum wait time), call timeout routing, and agent opt-in/opt-out to handle demand spikes without caller abandonment.
Compliance recording
Financial services and healthcare organizations must record Teams Phone calls for regulatory compliance. Teams Phone supports compliance recording through certified recording partners.
Certified compliance recording partners
- NICE
- Verint
- ASC Technologies
- Oak Innovation
- Dubber
Compliance recording is automatic — all calls to or from users assigned a recording policy are captured. Recordings are stored in the compliance partner's system for the required retention period. Teams Phone itself does not store compliance recordings.
Call Quality Dashboard (CQD)
The Microsoft Call Quality Dashboard monitors Teams Phone call quality across your organization. It shows mean opinion scores (MOS), network jitter, packet loss, and round-trip latency for every call.
EPC Group uses CQD data at three points in every migration:
- Pre-migration network readiness assessment — baseline CQD data confirms the network meets Teams voice requirements before migration.
- Pilot phase validation — CQD confirms call quality meets the target threshold before the full rollout.
- Post-migration optimization — CQD identifies sites or users with call quality issues for targeted remediation.
Migration phases
EPC Group's standard Teams Phone migration follows five phases:
- Assessment and design (2–4 weeks). Inventory current PBX, carrier contracts, number ranges, call flows, and fax lines. Design the Teams Phone architecture and connectivity model.
- Infrastructure setup (2–4 weeks). Configure SBC (for Direct Routing) or provision Operator Connect carrier. Set up Teams Phone licenses, dial plans, and call policies. Build baseline auto-attendants and call queues.
- Number porting preparation (2–3 weeks). Submit port authorization letters to the losing carrier. Assign temporary Teams numbers for testing. Validate call quality with CQD.
- Phased user migration (4–8 weeks). Migrate users in waves of 200–500. Each wave includes pre-migration user communication, cutover during low-traffic hours, and a 48-hour intensive support window.
- Post-migration optimization (2–4 weeks). Tune call quality using CQD. Refine auto-attendant and call queue configurations. Decommission legacy PBX equipment.
Frequently asked questions
What licenses do I need for Microsoft Teams Phone?
Teams Phone requires a Teams Phone System license. It is included in Microsoft 365 E5. For E3 and other plans, add the Teams Phone System add-on ($8/user/month as of 2026).
In addition to the Phone System license, you need a PSTN connectivity option: Calling Plan (Microsoft carrier), Direct Routing (your carrier via SBC), or Operator Connect (certified carrier partner). Each user that needs a phone number needs both the Phone System license and PSTN connectivity.
What is the difference between auto-attendant and call queue in Teams?
An auto-attendant presents menu options to callers and routes them based on input — it is the "press 1 for sales, press 2 for support" system. A call queue holds callers in line and distributes them to available agents — it is the "your call is important to us, please hold" system.
Auto-attendants can route to call queues. Call queues can overflow to other auto-attendants or voicemail. They work together to handle inbound call volume.
Can Teams Phone replace a contact center (CCaaS)?
Teams Phone with call queues covers basic inbound contact center scenarios: queue routing, agent management, overflow handling, and real-time call dashboards.
It does not replace full CCaaS platforms (Genesys, Avaya, Five9) for complex contact center needs — omnichannel (chat, email, social), CRM integration, advanced workforce management, or predictive outbound dialing. Microsoft partners with contact center vendors for deep CCaaS integration with Teams Phone.
How is Teams Phone different from Teams voice calling?
Teams supports VoIP calling between Teams users within the same tenant or across federated tenants at no additional cost — this is Teams-to-Teams calling.
Teams Phone adds PSTN connectivity: the ability to call and receive calls from any phone number, including cell phones, landlines, and external organizations not using Teams. PSTN calling requires the Teams Phone System license and a PSTN connectivity option (Calling Plans, Direct Routing, or Operator Connect).
How does Teams Phone handle international calling for multinational organizations?
Multinational Teams Phone deployments typically use a hybrid PSTN architecture. Regions where Microsoft Calling Plans are available and cost-competitive use Calling Plans. Regions where Calling Plans are unavailable or expensive use Direct Routing with local carriers.
Operator Connect is an alternative for regions with available certified carrier partners. EPC Group designs the hybrid architecture during the assessment phase, optimizing carrier selection by region for cost and compliance.
Ready to replace your PBX with Microsoft Teams Phone? Contact EPC Group for a Teams Phone assessment and migration plan.
Frequently Asked Questions
What is Microsoft Teams Phone System and how does it replace a traditional PBX?
Microsoft Teams Phone System is Microsoft cloud-based PBX replacement that turns Microsoft Teams into a full enterprise telephony platform. It provides dial tone, call control, auto-attendants, call queues, voicemail, call transfer, hold, park, and forwarding capabilities directly within the Teams client on desktop, mobile, and Teams-certified desk phones. It replaces on-premises PBX hardware (Cisco, Avaya, Mitel, NEC) by moving call control to the Microsoft 365 cloud. PSTN connectivity (the connection to the public telephone network) is provided through three options: Microsoft Calling Plans, Direct Routing, or Operator Connect. Teams Phone System requires a Teams Phone license ($8/user/month standalone, or included in Microsoft 365 E5 and Office 365 E5). EPC Group has migrated 150+ organizations from legacy PBX systems to Teams Phone, including multi-site deployments with 10,000+ users, complex call routing requirements, and compliance recording for regulated industries.
Should we use Calling Plans, Direct Routing, or Operator Connect for Teams?
The choice depends on your organization size, geographic footprint, and existing telecom relationships. Microsoft Calling Plans are the simplest option: Microsoft is your PSTN carrier, providing phone numbers and minutes in a bundled plan ($12-$24/user/month domestic, $24/user/month domestic + international). Best for organizations under 500 users in supported countries with straightforward calling patterns. Direct Routing connects your existing SBC (Session Border Controller) or carrier to Teams via SIP trunks. Best for large enterprises (1,000+ users) with existing carrier contracts, complex routing requirements, international presence in countries where Calling Plans are unavailable, or need for analog device support (fax machines, elevator phones, paging systems). Operator Connect is a carrier-managed service where your telecom provider connects directly to Teams through the Microsoft Teams admin center. Best for mid-size organizations (500-5,000 users) who want carrier-grade reliability without managing SBC infrastructure. EPC Group recommends Direct Routing for 80% of enterprise clients because it provides maximum flexibility, lowest per-user cost at scale, and supports the complex routing scenarios that large organizations require.
How much does it cost to migrate from a legacy PBX to Microsoft Teams Phone?
Total migration costs vary based on user count, complexity, and PSTN connectivity choice. For a 1,000-user enterprise: Teams Phone licensing is $8/user/month ($96,000/year if not on E5, free if already on E5). PSTN connectivity ranges from $8-$24/user/month for Calling Plans, $3-$8/user/month for Direct Routing (carrier SIP trunk + SBC amortization), or $5-$15/user/month for Operator Connect. SBC hardware costs $10,000-$50,000 for Direct Routing (Audiocodes, Ribbon). Migration consulting typically runs $75,000-$200,000 including design, pilot, phased rollout, and training. Common area phones (lobbies, kitchens, conference rooms) require Teams Phone Device licenses ($8/device/month) and certified hardware ($200-$600 per device). The 3-year TCO for Teams Phone is typically 30-50% lower than maintaining a legacy PBX when factoring in eliminated PBX maintenance contracts ($50,000-$150,000/year), reduced carrier costs through SIP trunk consolidation, eliminated PBX hardware refresh cycles, reduced telecom admin labor, and unified communication platform management. EPC Group provides detailed TCO analyses and fixed-price migration proposals.
How does compliance recording work with Microsoft Teams Phone System?
Compliance recording in Teams uses certified third-party recording solutions that integrate through the Microsoft Teams compliance recording API. This is distinct from convenience recording (the record button in a meeting). Compliance recording captures calls automatically based on policy without user awareness or ability to pause/stop, which is required for financial services (MiFID II, Dodd-Frank), healthcare (HIPAA), and other regulated industries. Certified compliance recording partners include Verint, NICE, Dubber, ASC Technologies, and CallCabinet. The recording architecture works by inserting a recording bot into every call for policy-matched users, capturing audio (and optionally video/screen share for meetings), streaming to the recording provider secure cloud storage with encryption, and providing supervisors with playback, search, transcription, and analytics capabilities. Retention policies can be configured to meet regulatory requirements (7 years for financial services, varies by jurisdiction). EPC Group designs compliance recording architectures that cover both Teams calling and Teams meetings, ensuring complete capture of all regulated communications with proper chain of custody documentation for audit purposes.
Can Microsoft Teams Phone System handle our multi-site, international requirements?
Yes, Teams Phone System supports complex multi-site and international deployments, but architecture matters. For multinational organizations, EPC Group designs hybrid PSTN architectures where each region uses the optimal connectivity method: Direct Routing with local carriers in regions where Calling Plans are unavailable or prohibitively expensive, Calling Plans in regions where Microsoft offers competitive rates and simple calling patterns exist, and Operator Connect where carrier relationships and SLAs are strategically important. Key multi-site capabilities include location-based routing to ensure calls route through local PSTN gateways for regulatory compliance (required in some countries), dynamic emergency calling (E911/E112) that routes emergency calls to local PSAPs based on user network location with automatic location detection, local number assignment from each country carrier for professional local presence, centralized management through Teams admin center with delegated administration per region, and survivable branch appliance (SBA) support for continued PSTN calling at sites that temporarily lose cloud connectivity. EPC Group has deployed Teams Phone for organizations spanning 30+ countries with 15,000+ users, handling complex regulatory requirements including number portability across carriers, local emergency services compliance, and country-specific call recording regulations.
About Errin O'Connor
Founder & Chief AI Architect, EPC Group
Errin O'Connor is the founder and Chief AI Architect of EPC Group, bringing over 29 years of Microsoft ecosystem expertise. As a 4x Microsoft Press bestselling author and former NASA Lead Architect, Errin has designed and executed 150+ enterprise PBX-to-Teams Phone migrations across healthcare, financial services, and government sectors.
Learn more about Errin