Microsoft Teams Phone System: Enterprise Deployment Guide 2026
Replace your legacy PBX with cloud-native enterprise voice. Direct Routing, Operator Connect, E911, compliance recording, and a proven migration roadmap.
Why Enterprises Are Replacing PBX with Teams Phone
Featured Snippet: Microsoft Teams Phone System is a cloud-based enterprise telephony solution that replaces traditional on-premises PBX hardware. It provides dial tone, call routing, auto attendants, call queues, voicemail with transcription, and PSTN connectivity — all within the Teams client your employees already use. Teams Phone eliminates PBX hardware refresh cycles, reduces telephony costs by 30-60%, and unifies voice, video, chat, and collaboration on a single platform. PSTN connectivity is delivered through Microsoft Calling Plans, Direct Routing with your own SBC and carrier, or Operator Connect through certified telecom providers.
The enterprise PBX is dying. Avaya, Cisco, and Mitel still power millions of desk phones, but organizations are migrating to cloud telephony at an accelerating pace. By 2026, Gartner estimates that 60% of enterprise voice traffic will run on UCaaS platforms — and Microsoft Teams Phone is the dominant choice for organizations already invested in the Microsoft 365 ecosystem.
The business case is straightforward: why maintain a separate PBX infrastructure with its own hardware, licensing, trunks, and support contracts when Teams can deliver the same calling capabilities as part of the platform your organization already pays for? Teams Phone eliminates the capital expenditure of PBX hardware refreshes (typically $200-$500 per user every 5-7 years), reduces ongoing telecom costs through SIP trunking and competitive carrier options, and consolidates your communication stack from three or four tools into one.
EPC Group has migrated enterprises from Avaya, Cisco CUCM, Mitel, NEC, and Shoretel PBX systems to Microsoft Teams Phone. Our Microsoft 365 consulting practice handles every phase — from network readiness assessment and SBC design through number porting, auto attendant configuration, compliance recording, and user training. This guide covers everything you need to plan and execute an enterprise Teams Phone deployment.
Cost Reduction Reality: A 1,000-user organization maintaining an on-premises PBX typically spends $15-25/user/month on maintenance, trunks, and amortized hardware costs. Teams Phone with Direct Routing costs approximately $10/user/month (E3 add-on + SIP trunk) — saving $60,000-$180,000 annually while gaining unified communications, mobile softphone, and cloud resilience.
What is Microsoft Teams Phone System?
A cloud PBX built into Microsoft 365 that delivers enterprise-grade calling through the Teams client.
Inbound & Outbound PSTN Calling
Make and receive calls to/from any phone number worldwide through the Teams desktop, mobile, or web client.
Cloud Voicemail with Transcription
AI-powered voicemail transcription delivers messages to email and Teams with full text searchability.
Auto Attendants & Call Queues
Automated call routing, IVR menus, hold music, and agent-group distribution — no third-party tools needed.
Enhanced 911 (E911)
Dynamic emergency calling with civic address delivery to PSAPs, network-based location detection, and security desk notification.
Compliance Recording
Policy-based call recording through certified partners (NICE, Verint, Dubber) for HIPAA, FINRA, and MiFID II.
Certified Desk Phones & Devices
Support for Poly, Yealink, and AudioCodes desk phones, conference phones, and Teams Rooms systems.
Calling Plans vs Direct Routing vs Operator Connect
Three paths to PSTN connectivity — choose based on your size, geography, and carrier requirements.
Microsoft Calling Plans
Best for: Small/mid-size, single-country deployments
$8-$24/user/month
Advantages
- Simplest deployment — no SBC or carrier management
- Phone numbers provisioned directly in Teams admin center
- Bundled minutes included (domestic or domestic + international)
- Microsoft manages PSTN connectivity end-to-end
Considerations
- Available in 33 countries only
- Limited carrier flexibility (Microsoft is the carrier)
- Higher per-user cost at scale vs Direct Routing
- Number porting can be slower through Microsoft
Direct Routing
Best for: Enterprise, multi-country, existing carrier contracts
$2-5/user/month + SBC ($5K-$50K)
Advantages
- Use any SIP trunk provider — maximum carrier flexibility
- Lowest per-minute cost at high volume
- Support for survivable branch appliances (local PSTN if Teams is down)
- Integration with existing on-premises telephony infrastructure
Considerations
- Requires SBC deployment and management
- Telecom expertise needed for SIP trunk configuration
- SBC represents a single point of failure (mitigate with HA)
- More complex initial deployment
Operator Connect
Best for: Enterprise wanting carrier flexibility without SBC management
$5-15/user/month (carrier dependent)
Advantages
- Carrier-managed — no SBC to deploy or maintain
- Provisioned directly in Teams admin center
- Multiple certified operators (AT&T, Verizon, BT, Lumen, etc.)
- Carrier provides number management and PSTN connectivity
Considerations
- Not all carriers participate in every country
- Less granular control than Direct Routing
- Carrier pricing varies and may include markups
- Dependent on carrier for troubleshooting PSTN issues
EPC Group Recommendation: For enterprises with 500+ users, multiple offices, or existing carrier contracts, Direct Routing delivers the best combination of cost control and flexibility. For organizations wanting simplicity with carrier choice, Operator Connect is the fastest path. Microsoft Calling Plans work well for single-country deployments under 500 users where Microsoft handles everything. Many enterprise deployments use a hybrid approach — Operator Connect for domestic offices and Direct Routing for international sites.
Auto Attendants & Call Queues
Enterprise call routing without third-party IVR tools. Built into Teams Phone at no additional cost.
Auto Attendants
- Multi-level IVR menus with business hours and after-hours routing
- Speech recognition and dial-by-name directory
- Holiday schedule management with custom greetings
- Transfer to users, call queues, external numbers, or voicemail
- Nested auto attendants for department-level routing
- Custom audio prompts or text-to-speech greetings
Call Queues
- Routing methods: first-in-first-out, round robin, longest idle, attendant
- Presence-based routing — skip agents in DND, busy, or offline status
- Configurable hold music and position announcements
- Overflow routing after maximum wait time or queue depth
- Opt-out to voicemail for callers who do not want to hold
- Real-time and historical queue analytics in Teams admin center
Cloud Voicemail & AI Transcription
Teams Phone cloud voicemail replaces legacy PBX voicemail systems with AI-powered transcription and unified delivery. Every voicemail is automatically transcribed using Microsoft speech recognition, delivered to the user's email inbox and Teams client simultaneously, and stored in Exchange Online for compliance retention and eDiscovery.
AI Transcription
Automatic speech-to-text transcription with high accuracy across multiple languages. Users read voicemails instead of listening to them.
Unified Delivery
Voicemail audio and transcript delivered to Outlook email and Teams. Users choose their preferred consumption method.
Compliance Retention
Voicemails stored in Exchange Online, subject to retention policies, legal hold, and eDiscovery search for regulatory compliance.
Custom Greetings & Rules
Per-user or policy-based voicemail greetings, out-of-office rules, and call answering rules for delegation scenarios.
Emergency Calling (E911) Configuration
Compliance Requirement: Federal law (Ray Baxter Act / Kari's Law) mandates that multi-line telephone systems allow direct 911 dialing without a prefix and provide notification to a central location (e.g., security desk). Teams Phone supports both requirements natively, but administrators must configure them. Failure to comply carries legal liability.
Static Location (Office)
- Register civic addresses in Teams admin center
- Map network subnets, WAPs, and switches to locations
- Floor-level accuracy for multi-story buildings
- Automatic PSAP routing based on registered address
Dynamic Location (Remote/Mobile)
- Microsoft Dynamic Emergency Calling detects network
- Users prompted to confirm emergency address
- Third-party location services for enhanced accuracy
- Policies enforce address updates for remote workers
Compliance Recording for Regulated Industries
Teams Phone compliance recording is policy-based and automatic — administrators assign recording policies to users, and all calls are captured with no ability for the user to stop, pause, or delete recordings. This differs from Teams convenience recording which is user-initiated and visible to all participants.
Healthcare (HIPAA)
Record patient-facing calls, store with PHI-appropriate retention, produce for HHS audits
Financial Services (FINRA/SEC)
Record all trade confirmation and advisory calls, 6-year retention, tamper-proof storage
Government (FedRAMP)
Record calls in GCC/GCC High environments, meet NIST 800-53 controls for audit trail integrity
European Finance (MiFID II)
Record investment advice and order execution calls, 5-year retention, rapid retrieval for regulator requests
Certified Recording Partners: NICE, Verint, Dubber, ASC Technologies, CallCabinet, and Red Box are Microsoft-certified compliance recording providers. EPC Group evaluates recording platform requirements and deploys the solution that matches your regulatory obligations, storage needs, and budget.
Pricing & Licensing
| Component | Cost (per user/month) | Notes |
|---|---|---|
| Teams Phone Standard (E5 included) | $0 (included) | Included with Microsoft 365 E5 or Office 365 E5 |
| Teams Phone Standard (E3 add-on) | $8/user/month | Add-on for M365 E3, E1, F1, F3 plans |
| Domestic Calling Plan (120 min) | $8/user/month | Microsoft-provided PSTN, US/Canada/UK/EU |
| Domestic Calling Plan (unlimited) | $12/user/month | Unlimited domestic minutes |
| International Calling Plan | $24/user/month | Domestic unlimited + 600 international min |
| Direct Routing (SIP trunk) | $2-5/user/month | Carrier-dependent, plus SBC one-time cost |
| Operator Connect | $5-15/user/month | Carrier-dependent, no SBC required |
| Common Area Phone | $8/user/month | Lobby phones, conference rooms, break rooms |
| Audio Conferencing | $4/user/month | Dial-in numbers for meetings (E5 included) |
Enterprise Cost Example: 1,000 users on M365 E3 ($36/user/month) + Teams Phone add-on ($8/user/month) + Direct Routing SIP trunk ($3/user/month) = $47/user/month total. Annual Teams Phone cost: $132,000. Compared to legacy PBX at $15-25/user/month ($180,000-$300,000/year), Teams Phone saves $48,000-$168,000 annually — with no hardware refresh capital expenditure.
International Calling & Multi-Country Deployment
Global enterprises require local phone number presence in every country where they operate. Teams Phone supports international deployment through three strategies, often combined in a single organization:
Microsoft Calling Plans (33 countries)
Available in the US, Canada, UK, Germany, France, Australia, Japan, and 26 other countries. Microsoft provides local phone numbers and PSTN connectivity. Simplest option where available.
Global SIP Trunk via Direct Routing
Partner with a global SIP trunk provider (Colt, BICS, Tata Communications) to deliver PSTN connectivity in 100+ countries through a single contract and centralized SBC deployment.
Local Operator Connect by Country
Use country-specific Operator Connect carriers for local number presence and competitive rates. Managed through the Teams admin center with no local SBC required.
Hybrid Multi-Country Strategy
Combine approaches: Calling Plans for US/UK headquarters, Operator Connect for major European offices, and Direct Routing via global SIP trunk for APAC and emerging markets.
Implementation Roadmap
EPC Group's proven 5-phase methodology for enterprise PBX-to-Teams Phone migration.
Discovery & Assessment
2-3 weeks
- Audit current PBX system — model, firmware, capacity, trunk configuration
- Inventory all phone numbers (DIDs, main lines, toll-free, fax)
- Document auto attendant trees and call flow logic
- Map call queue configurations and agent groups
- Assess network readiness (bandwidth, QoS, firewall rules)
- Identify analog devices (fax, elevator phones, door buzzers)
- Survey user calling patterns and international calling needs
Design & Architecture
2-3 weeks
- Select PSTN connectivity model (Calling Plans, Direct Routing, or Operator Connect)
- Design auto attendant and call queue architecture
- Plan emergency calling (E911) configuration for all sites
- Specify compliance recording requirements (if applicable)
- Design network QoS policies for voice traffic prioritization
- Select and size SBC hardware/software (if Direct Routing)
- Define number porting strategy and carrier coordination plan
Infrastructure & Configuration
2-4 weeks
- Deploy and configure SBC (Direct Routing) or Operator Connect integration
- Configure Teams Phone policies (calling, voicemail, caller ID)
- Build auto attendants with business hours, menus, and routing
- Configure call queues with agent groups and overflow rules
- Set up E911 with civic addresses and network-to-location mapping
- Deploy compliance recording policies (regulated industries)
- Configure common area phones and conference room devices
Pilot & Number Porting
3-4 weeks
- Pilot with 25-50 users on temporary phone numbers
- Validate call quality, auto attendant routing, and voicemail
- Submit number porting requests for all DIDs and main lines
- Train pilot users on Teams Phone features (call park, transfer, delegation)
- Test E911 from every office location and floor
- Validate compliance recording capture and retrieval
- Collect pilot feedback and remediate issues
Site-by-Site Cutover
4-8 weeks
- Execute site-by-site migration (one office per cutover window)
- Port phone numbers on scheduled FOC dates
- Run parallel PBX and Teams Phone during transition (2-4 weeks)
- Deploy desk phones and common area devices at each site
- Conduct site-specific user training and go-live support
- Validate all call flows, queues, and auto attendants post-cutover
- Decommission legacy PBX trunks and hardware after validation
Common Migration Challenges & Solutions
Every PBX migration encounters these issues. Here is how EPC Group handles each one.
Analog Devices (Fax, Elevator Phones, Door Buzzers)
Deploy analog telephony adapters (ATAs) from AudioCodes or Poly to bridge analog devices to Teams Phone SIP trunks. For fax, migrate to cloud fax services (eFax, RingCentral Fax) or use ATAs with T.38 fax relay. Elevator and safety phones require dedicated ATA deployment with battery backup.
Network Quality and Bandwidth
Each concurrent Teams Phone call requires approximately 100 Kbps of bandwidth. Implement QoS (Quality of Service) policies to prioritize voice traffic over data. Mark Teams voice packets with DSCP EF (Expedited Forwarding). Ensure less than 150ms round-trip latency and less than 1% packet loss to Microsoft 365 endpoints. EPC Group performs pre-migration network assessments using Microsoft Network Assessment Tool.
Contact Center Integration
Teams Phone native call queues handle basic contact center scenarios (up to 200 agents). For advanced requirements (skills-based routing, IVR, CRM integration, workforce management), deploy a Teams-certified contact center solution from NICE, Genesys, Five9, or Anywhere365. These integrate via Direct Routing or Azure Communication Services and provide the Teams client as the agent interface.
International Calling and Multi-Country Deployment
For multi-country deployments, use a hybrid PSTN strategy: Direct Routing with a global SIP trunk provider (Colt, BICS, Tata) for countries not covered by Calling Plans, combined with local Operator Connect or Calling Plans where available. This ensures local number presence, competitive per-minute rates, and compliance with local telecom regulations.
User Resistance and Training
The shift from desk phones to softphones is the biggest change management challenge. Provide certified desk phones (Poly CCX series, Yealink T-series) for users who prefer physical handsets. Deliver role-based training: receptionists need call park and transfer, executives need delegation and boss-admin, and all users need mobile client and voicemail-to-text. Champions network and floor-walking support during the first two weeks post-cutover.
Survivability During Internet Outage
Deploy Survivable Branch Appliances (SBA) at critical sites. AudioCodes and Ribbon offer SBA-capable SBCs that provide local PSTN calling if the connection to Microsoft 365 goes down. Users can make and receive calls through the local SBC gateway until Teams connectivity is restored. Essential for healthcare facilities, emergency services, and mission-critical operations.
Frequently Asked Questions
What is Microsoft Teams Phone System and how does it replace PBX?
Microsoft Teams Phone System is a cloud-based enterprise telephony solution built into Microsoft 365. It replaces traditional on-premises PBX hardware by providing dial tone, call routing, auto attendants, call queues, voicemail, and PSTN connectivity directly within the Teams client. Unlike legacy PBX systems that require dedicated hardware, trunk lines, and ongoing maintenance contracts, Teams Phone operates as a software service — reducing capital expenditure by 40-60% and eliminating end-of-life hardware refresh cycles. Teams Phone supports desk phones (certified Poly, Yealink, AudioCodes devices), softphone clients (desktop, mobile, web), and Microsoft Teams Rooms for conference rooms. EPC Group has migrated organizations from Avaya, Cisco, Mitel, and NEC PBX systems to Teams Phone across healthcare, finance, and government.
What is the difference between Calling Plans, Direct Routing, and Operator Connect?
Microsoft offers three PSTN connectivity options: 1) Microsoft Calling Plans — Microsoft provides the phone numbers and PSTN connectivity as a bundled service ($8-$12/user/month domestic, $24/user/month international). Simplest to deploy but limited to 33 countries with less carrier flexibility. 2) Direct Routing — connect your own SBC (Session Border Controller) to Teams Phone, using your existing telecom carrier or SIP trunk provider. Maximum flexibility and typically lowest per-minute cost for high-volume calling. Requires SBC hardware/software and telecom expertise. 3) Operator Connect — a managed option where Microsoft-certified telecom operators (AT&T, Verizon, BT, etc.) provide PSTN connectivity directly through the Teams admin center. Easier than Direct Routing but with carrier flexibility. EPC Group recommends Direct Routing for enterprises with 500+ users and existing carrier relationships, and Operator Connect for organizations wanting simplicity without Microsoft Calling Plan limitations.
How much does Microsoft Teams Phone System cost?
Teams Phone licensing: Teams Phone Standard is included in Microsoft 365 E5 ($57/user/month). For E3 customers ($36/user/month), add Teams Phone Standard at $8/user/month. PSTN connectivity is additional: Microsoft Calling Plans range from $8/user/month (domestic, 120 min) to $24/user/month (domestic + international). Direct Routing costs depend on your SBC and carrier — typically $2-5/user/month for SIP trunk plus one-time SBC cost ($5,000-$50,000 depending on capacity). Operator Connect pricing varies by carrier, typically $5-15/user/month. Common area phone licenses are $8/user/month. For a 1,000-user deployment on E3 with Direct Routing: base licensing adds approximately $10/user/month ($120,000/year) versus maintaining a PBX at $15-25/user/month ($180,000-$300,000/year) — saving 30-60% annually while eliminating hardware refresh costs every 5-7 years.
How long does a PBX to Teams Phone migration take?
Migration timeline depends on complexity: Small organizations (50-200 users, single site): 4-6 weeks. Mid-size organizations (200-1,000 users, 2-5 sites): 6-12 weeks. Enterprise organizations (1,000-10,000+ users, multiple sites, international): 3-6 months with phased site-by-site cutover. Key timeline factors: number porting (2-4 weeks per carrier), SBC deployment for Direct Routing (1-2 weeks), auto attendant and call queue configuration (1-2 weeks), user training (1 week per site), and parallel running period (2-4 weeks recommended). EPC Group uses a site-by-site cutover approach for enterprise migrations — migrating one office at a time with a parallel running period where both PBX and Teams Phone are active, ensuring zero downtime during transition.
What happens to my existing phone numbers when migrating to Teams Phone?
Your existing phone numbers are ported (transferred) to Microsoft or your Direct Routing/Operator Connect carrier. Number porting preserves all existing DIDs, main line numbers, and toll-free numbers. The porting process takes 2-4 weeks depending on the losing carrier. During porting: 1) Submit a Letter of Authorization (LOA) and Customer Service Record (CSR) to the gaining carrier. 2) The losing carrier validates and approves the port request. 3) A firm order commitment (FOC) date is set for the actual transfer. 4) Numbers transfer on the FOC date — typically with less than 60 seconds of downtime. EPC Group manages the entire number porting process including carrier coordination, LOA preparation, and testing to ensure zero disruption to inbound calling.
How does emergency calling (E911) work with Teams Phone?
Teams Phone supports Enhanced 911 (E911) to route emergency calls to the correct Public Safety Answering Point (PSAP) with caller location information. For static locations (offices): administrators register civic addresses in the Teams admin center and associate them with network subnets, WAPs, or Ethernet switches. When a user dials 911 from a registered network, Teams sends the registered address to the PSAP. For dynamic/remote locations: Microsoft Dynamic Emergency Calling uses network topology to estimate location. Users working from home or mobile locations are prompted to confirm their emergency address. Compliance requirements: Ray Baxter Act (Kari Law) requires direct 911 dialing without prefix and notification to a designated security desk. Teams Phone supports both requirements natively. EPC Group configures E911 for every deployment, including multi-building campuses with floor-level location accuracy.
Can Teams Phone handle compliance recording for regulated industries?
Yes. Teams Phone supports policy-based compliance recording through certified recording partners (NICE, Verint, Dubber, ASC, CallCabinet, Red Box). Unlike convenience recording (user-initiated), compliance recording is policy-based — automatically recording all calls for specified users with no ability for the user to stop or pause recording. This meets requirements for HIPAA (healthcare call documentation), FINRA/SEC Rule 17a-4 (financial services trade confirmation calls), MiFID II (European financial recording mandates), and Dodd-Frank (swap dealer call recording). Recordings are stored in the compliance recording partner platform with tamper-proof audit trails, retention policies, and search capabilities. EPC Group deploys compliance recording for healthcare organizations, financial services firms, and government agencies where call recording is a regulatory requirement.
What SBC is recommended for Direct Routing?
Microsoft certifies SBCs from AudioCodes, Ribbon (formerly GENBAND/Sonus), Oracle, and TE-Systems. Top recommendations by scenario: AudioCodes Mediant series (most popular, widest carrier compatibility, available as hardware or virtual SBC on Azure). Ribbon SBC 5000/7000 series (high-capacity enterprise, carrier-grade reliability). Oracle Enterprise SBC (for organizations already using Oracle communications). For cloud-first deployments, AudioCodes Live (cloud SBC service) or Ribbon SBC as a Service eliminates on-premises hardware entirely. Key sizing: an AudioCodes Mediant 800 handles up to 150 concurrent calls ($3,000-$5,000), while a Mediant Virtual Edition on Azure handles 500+ concurrent calls. EPC Group partners with AudioCodes and Ribbon to design, deploy, and manage Direct Routing SBC infrastructure.
How do auto attendants and call queues work in Teams Phone?
Auto attendants are the automated greeting and call routing system (press 1 for sales, press 2 for support). Teams auto attendants support: multi-level menus, business hours/after-hours routing, dial-by-name directory, speech recognition, holiday schedules, and call transfer to internal users, call queues, external numbers, or voicemail. Call queues distribute incoming calls to groups of agents — supporting first-in-first-out, round robin, longest idle, and attendant routing methods. Features include: hold music, overflow routing (redirect after X callers waiting or Y minutes), timeout routing, opt-out to voicemail, agent presence-based routing (skip agents in DND/busy), and real-time queue analytics. Both auto attendants and call queues use resource accounts with virtual phone numbers — no additional user licenses required. EPC Group has built multi-tier auto attendant trees handling 50,000+ monthly calls for enterprise contact centers.
Replace Your PBX with Teams Phone
Start with a Teams Phone Readiness Assessment. EPC Group audits your current PBX, network infrastructure, calling patterns, and compliance requirements — then delivers a migration roadmap with timeline, licensing cost model, and PSTN connectivity recommendation. Fixed-fee engagement starting at $15,000.