Why Enterprises Are Moving Voice to Microsoft Teams
The traditional enterprise telephony model of dedicated PBX hardware, separate voice networks, and carrier-managed infrastructure is rapidly giving way to cloud-based unified communications. Microsoft Teams Phone System is at the center of this transformation, enabling organizations to consolidate voice, video, messaging, and collaboration onto a single platform that employees already use daily.
The business case for Teams Phone System migration goes beyond cost savings, though those are significant. Organizations that complete the migration report 30-40% reduction in total telephony costs, elimination of PBX hardware maintenance contracts and end-of-life upgrade cycles, unified communication experience that improves employee productivity, simplified administration through the Teams admin center rather than legacy PBX management consoles, and enhanced mobility with calls following users across desk phones, computers, and mobile devices.
With over 320 million monthly active Teams users globally, Microsoft has invested heavily in making Teams Phone System an enterprise-grade voice platform. The question for most organizations is not whether to migrate, but how to execute the migration efficiently while maintaining business continuity. EPC Group has led enterprise Teams deployments for organizations with 10,000+ users, and this guide reflects those real-world implementation patterns.
Understanding PSTN Connectivity Options
The most important architectural decision in a Teams Phone System deployment is how to connect to the Public Switched Telephone Network (PSTN). Microsoft offers three options, each with distinct trade-offs for enterprise environments.
Microsoft Calling Plans
Microsoft Calling Plans provide an all-in-one solution where Microsoft acts as both the platform provider and the PSTN carrier. Microsoft provides phone numbers, calling connectivity, and per-user domestic or international calling bundles. The advantages are simplicity (no additional infrastructure required), fast deployment, and a single vendor relationship. The disadvantages are limited geographic availability (not available in all countries), higher per-user costs at enterprise scale, less control over call routing and failover, and potential number porting delays when moving from existing carriers. Microsoft Calling Plans are best suited for organizations under 1,000 users in supported countries who prioritize simplicity over cost optimization.
Direct Routing
Direct Routing connects your existing or new Session Border Controller (SBC) to Teams Phone System, enabling you to use any PSTN carrier or SIP trunking provider. This gives enterprises full control over carrier selection, call routing policies, survivability during internet outages, and cost optimization through competitive carrier selection. Direct Routing requires deploying and managing certified SBCs (physical appliances from AudioCodes, Ribbon, or Oracle, or cloud-hosted SBCs like AudioCodes Live). The technical complexity is higher, but the flexibility and cost savings are substantial. For enterprises with 1,000+ users, Direct Routing typically reduces PSTN costs by 40-60% compared to Microsoft Calling Plans. Direct Routing also supports advanced scenarios like location-based routing for regulatory compliance, local media optimization for branch offices, and integration with existing contact center platforms.
Operator Connect
Operator Connect is a Microsoft-managed program where certified telecommunications operators connect directly to Teams through APIs in the Teams admin center. It offers a middle ground between the simplicity of Calling Plans and the flexibility of Direct Routing. You choose from participating operators, manage numbers through the Teams admin center, and benefit from operator-managed connectivity without deploying your own SBCs. Operator Connect is increasingly popular with enterprises that want carrier flexibility without the infrastructure overhead of Direct Routing. The growing list of certified operators includes major carriers like AT&T, Verizon, BT, and Deutsche Telekom.
| Feature | Calling Plans | Direct Routing | Operator Connect |
|---|---|---|---|
| Infrastructure | None (Microsoft-managed) | Customer-managed SBC | Operator-managed |
| Carrier Flexibility | Microsoft only | Any SIP trunk provider | Certified operators |
| Enterprise Cost (1,000+ users) | $$$ (highest) | $ (lowest) | $$ (middle) |
| Setup Complexity | Low | High | Medium |
| Survivability | Cloud-dependent | Local SBC failover | Operator-dependent |
Number Porting: Planning and Execution
Number porting is often the most anxiety-inducing part of a voice migration because phone numbers are critical business assets. However, with proper planning, porting is a routine process with minimal risk.
Pre-Porting Preparation
Before initiating any port requests, complete the following preparation steps. Inventory all phone numbers including main lines, direct dial numbers, toll-free numbers, fax lines, and analog lines for elevators, security systems, and alarms. Document the current carrier and account details for each number block, as port requests require exact account information. Identify numbers that cannot be ported, such as analog lines connected to physical devices, which may need to remain on traditional circuits or be converted using ATAs (Analog Telephone Adapters). Create a porting schedule that groups numbers by department or location, with the pilot group porting first.
Porting Process and Timelines
The porting process involves submitting a Letter of Authorization (LOA) to the gaining carrier, which is then sent to the losing carrier for verification. Standard number ports typically complete in 2-4 weeks, while toll-free number ports take 4-8 weeks due to additional carrier coordination. During the porting window, there is a brief cutover period (usually under 30 minutes) where incoming calls to the ported numbers begin routing to the new system. Schedule this cutover during low-traffic hours and have a rollback plan in case of issues. Temporary numbers can be assigned in Teams before porting completes, allowing users to start making outbound calls immediately.
Auto-Attendants and Call Queues
Auto-attendants and call queues are the Teams Phone System features that replace traditional PBX IVR (Interactive Voice Response) and ACD (Automatic Call Distribution) functionality.
Designing Auto-Attendants
Teams auto-attendants handle inbound calls with automated greetings, menu options, and intelligent routing. Best practices for enterprise auto-attendant design include keeping menu trees shallow with no more than 3 levels to avoid caller frustration, providing a direct path to a live agent at every level, configuring business hours and after-hours routing with different greetings and options, using dial-by-name directories for callers who know their contact, and implementing nested auto-attendants for complex organizational structures. Auto-attendants support multiple languages, custom greetings (recorded audio or text-to-speech), and holiday schedules. For organizations migrating from legacy IVR systems, map existing call flows to Teams auto-attendant capabilities and identify any gaps that require third-party solutions.
Configuring Call Queues
Call queues distribute inbound calls to groups of agents based on configurable routing methods. Teams supports several routing modes: attendant routing (rings all agents simultaneously), serial routing (rings agents in a fixed order), round robin (distributes evenly across agents), and longest idle (routes to the agent who has been available longest). Configure overflow handling to redirect calls when the queue exceeds a maximum wait time or call count. Set timeout actions for calls that remain unanswered. Enable agents to opt in and out of queues for flexibility. For enterprise contact center requirements beyond native call queue capabilities, Microsoft-certified contact center solutions from NICE, Genesys, and Five9 provide advanced features like skills-based routing, workforce management, and real-time analytics.
Compliance Recording for Regulated Industries
For organizations in financial services, healthcare, and other regulated industries, compliance recording is a non-negotiable requirement. Teams Phone System supports policy-based compliance recording through Microsoft's compliance recording partner program.
How Compliance Recording Works
Compliance recording in Teams uses a bot-based architecture where a recording bot is automatically invited to calls involving users who have a compliance recording policy assigned. The recording bot captures both the audio stream and metadata (participants, duration, timestamps) and streams it to the partner's recording platform for storage, retention, and analysis. Unlike the user-initiated Teams recording feature, compliance recording is automatic, cannot be disabled by users, captures all call types (PSTN, peer-to-peer, group), and integrates with archival and eDiscovery systems.
Regulatory Requirements by Industry
- Financial Services (MiFID II, Dodd-Frank) - Requires recording and retention of all client-facing communications for 5-7 years with tamper-proof storage and audit access.
- Healthcare (HIPAA) - Calls containing Protected Health Information must be recorded, encrypted, access-controlled, and retained per organizational policy. Healthcare organizations must ensure BAAs cover the recording platform.
- Government (FedRAMP) - Recording solutions must meet FedRAMP authorization requirements for government cloud deployments.
PBX Migration Strategy: Phased Approach
Enterprise PBX migration should follow a phased approach that minimizes risk and allows for iterative learning. Do not attempt a big-bang cutover for organizations with more than 500 users.
Phase 1: Pilot (Weeks 1-4)
Deploy Teams Phone System to 50-100 users in a controlled pilot group. Select pilot users who are technically comfortable, willing to provide feedback, and represent different usage patterns (heavy callers, light callers, reception staff, mobile workers). The pilot validates call quality, feature parity with the existing PBX, and identifies any integration issues before broader rollout. Measure call quality metrics (MOS scores, jitter, packet loss), user satisfaction, and support ticket volume during the pilot.
Phase 2: Department-by-Department Rollout (Weeks 5-16)
Migrate departments in waves of 200-500 users, prioritizing departments with simpler calling requirements first. Each wave follows a repeatable pattern: pre-migration user communication and training, number porting or cutover during low-traffic hours, same-day validation of inbound and outbound calling, 48-hour intensive support window with dedicated help desk resources, and post-wave review before proceeding to the next group. Maintain the legacy PBX in parallel operation during the rollout phase. This provides a safety net for rollback if critical issues emerge.
Phase 3: Legacy Decommission (Weeks 17-24)
After all users have been migrated and stabilized on Teams Phone System, decommission the legacy PBX infrastructure. This includes canceling legacy carrier circuits and trunks, decommissioning PBX hardware, updating emergency service registrations (E911) to reflect the new platform, and archiving legacy voicemail and call records per retention policies. The decommission phase is where the cost savings materialize. Legacy PBX maintenance contracts, dedicated voice circuits, and hardware support costs are eliminated.
Call Quality and Network Requirements
Voice is the most latency-sensitive application on any network. Teams Phone System call quality depends on proper network preparation, and quality issues after migration are almost always traceable to network infrastructure gaps rather than platform problems.
- Bandwidth - Allocate 100 Kbps per concurrent call for audio. Enterprise environments should plan for 10-15% simultaneous call ratio at peak.
- Latency - End-to-end latency should be under 50ms for optimal call quality. Latency above 150ms causes noticeable conversation delay.
- Jitter - Should be under 30ms. QoS (Quality of Service) policies that prioritize voice traffic are essential on congested networks.
- Packet loss - Should be under 1%. Even 2-3% packet loss causes audible degradation in voice quality.
Implement QoS policies that mark voice packets with DSCP EF (Expedited Forwarding) and prioritize them through your network infrastructure. For branch offices, consider local internet breakout with SD-WAN to optimize the path to Microsoft's network.
Devices and Meeting Room Integration
Teams Phone System supports a wide range of certified devices including desk phones from Yealink, Poly, AudioCodes, and Crestron, headsets and speakerphones for soft-phone users, Teams Rooms devices for conference rooms, and common area phones for lobbies, break rooms, and shared spaces. For enterprise deployments, standardize on 2-3 certified device models to simplify provisioning, support, and spare parts inventory. Use Teams device management in the admin center for zero-touch provisioning and remote management at scale.
Frequently Asked Questions
What is the difference between Microsoft Calling Plans, Direct Routing, and Operator Connect?
Microsoft Calling Plans are a fully managed PSTN solution where Microsoft provides the phone numbers and calling connectivity, ideal for organizations under 1,000 users who want simplicity. Direct Routing connects your existing SBC (Session Border Controller) to Teams Phone System, giving you full control over carrier relationships and call routing, best for enterprises with existing telecom contracts or complex routing requirements. Operator Connect is a hybrid where Microsoft-certified carriers connect directly to Teams through the Teams admin center, offering carrier flexibility with simpler setup than Direct Routing. Most enterprises with 1,000+ users choose Direct Routing or Operator Connect for cost control and flexibility.
How long does it take to migrate an enterprise PBX to Microsoft Teams Phone System?
A typical enterprise PBX to Teams Phone System migration takes 3-6 months for organizations with 1,000-10,000 users. The timeline includes 2-4 weeks for assessment and design, 2-4 weeks for infrastructure setup (SBC configuration for Direct Routing, or Operator Connect provisioning), 2-3 weeks for number porting preparation, 4-8 weeks for phased user migration in groups of 200-500, and 2-4 weeks for post-migration optimization. Complex environments with analog devices, elevator phones, fax lines, contact center integrations, or multi-country deployments can extend the timeline to 9-12 months.
How does number porting work when migrating to Teams Phone System?
Number porting transfers your existing phone numbers from your current carrier to Microsoft (for Calling Plans) or to your new carrier (for Direct Routing/Operator Connect). The process involves submitting a Letter of Authorization (LOA) with your current carrier details, number inventory, and authorized signature. Porting typically takes 2-4 weeks for standard numbers and 4-8 weeks for toll-free numbers. During the port, there is a brief cutover window (usually minutes, not hours) where calls route to the new system. Best practice is to port in batches by department or location, starting with a pilot group, to minimize risk.
Does Teams Phone System support compliance recording for regulated industries?
Yes, Teams Phone System supports policy-based compliance recording through certified third-party solutions. Microsoft provides a compliance recording API that certified partners (NICE, Verint, ASC Technologies, Dubber, and others) use to capture, store, and analyze all voice communications. For regulated industries, compliance recording can be configured as policy-based (automatic recording of all calls for specified users) or on-demand. Recordings are stored in the partner platform with retention policies that meet HIPAA, MiFID II, Dodd-Frank, FCA, and other regulatory requirements. This is different from the built-in Teams meeting recording feature, which is user-initiated and not suitable for compliance purposes.
What licensing is required for Microsoft Teams Phone System?
Teams Phone System requires a Teams Phone license (formerly Phone System license) which is included in Microsoft 365 E5 or available as an add-on to E1/E3 plans at approximately $8/user/month. Additionally, you need PSTN connectivity: Microsoft Calling Plans ($12-$24/user/month depending on domestic/international), or your own PSTN connectivity via Direct Routing (SBC costs plus carrier charges), or Operator Connect (carrier-dependent pricing). Common calling add-ons include Audio Conferencing ($4/user/month, included in E5), Communication Credits for toll-free and international overage, and Teams Phone with Calling Plan bundle for simplified purchasing. For 5,000+ user enterprises, Direct Routing typically costs 40-60% less than Microsoft Calling Plans.
Migrate Your Enterprise Voice to Microsoft Teams
EPC Group's Microsoft Teams consulting practice has led voice migrations for organizations with 10,000+ users across healthcare, financial services, and government. We handle the full lifecycle from PSTN architecture to compliance recording to PBX decommission.
Schedule Teams Voice AssessmentErrin O'Connor
CEO & Chief AI Architect at EPC Group with 28+ years of experience in enterprise Microsoft solutions. Bestselling Microsoft Press author specializing in Microsoft Teams, Azure architecture, and large-scale enterprise communications transformations.