Microsoft Teams Phone System: Enterprise Voice Migration Guide

Why Enterprises Are Moving Voice to Microsoft Teams

The traditional enterprise telephony model relies on dedicated PBX hardware, separate voice networks, and carrier-managed infrastructure. This model is quickly being replaced by cloud-based unified communications.

At the heart of this change is the Microsoft Teams Phone System. It allows organizations to:

• Consolidate voice
• Integrate video
• Streamline messaging
• Enhance collaboration

All of these features are available on a single platform that employees already use every day.

The business case for migrating to the Teams Phone System includes more than just cost savings, although those are substantial. Organizations that make the switch report:

• A 30-40% reduction in total telephony costs.
• Elimination of PBX hardware maintenance contracts and end-of-life upgrade cycles.
• A unified communication experience that boosts employee productivity.
• Simplified administration through the Teams admin center instead of legacy PBX management consoles.
• Enhanced mobility, allowing calls to follow 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 offer a complete solution where Microsoft serves as both the platform provider and the PSTN carrier. They provide:

• Phone numbers
• Calling connectivity
• Per-user domestic or international calling bundles

The advantages include:

• Simplicity (no extra infrastructure needed)
• Fast deployment
• A single vendor relationship

However, there are some disadvantages:

• Limited geographic availability (not in all countries)
• Higher per-user costs at enterprise scale
• Less control over call routing and failover
• Possible delays in number porting when switching from other carriers

Microsoft Calling Plans are ideal for organizations with fewer than 1,000 users in supported countries that value simplicity over cost optimization.

Direct Routing

Direct Routing connects your existing or new Session Border Controller (SBC) to the Teams Phone System. This setup allows you to use any PSTN carrier or SIP trunking provider. As a result, enterprises gain full control over:

• Carrier selection
• Call routing policies
• Survivability during internet outages
• Cost optimization through competitive carrier selection

Direct Routing involves using certified Session Border Controllers (SBCs). These can be physical devices from AudioCodes, Ribbon, or Oracle, or cloud-hosted options like AudioCodes Live. Although it is more technically complex, the benefits in flexibility and cost savings are substantial.

For enterprises with over 1,000 users, Direct Routing can lower PSTN costs by 40-60% compared to Microsoft Calling Plans. It also enables advanced scenarios, such as:

• Integration with existing telephony systems
• Support for multiple locations
• Enhanced call management features

• Location-based routing for regulatory compliance
• Local media optimization for branch offices
• Integration with existing contact center platforms

Operator Connect

Operator Connect is a program managed by Microsoft. It enables certified telecommunications operators to connect directly to Teams through APIs in the Teams admin center. This program combines the ease of Calling Plans with the flexibility of Direct Routing.

With Operator Connect, you can:

• Choose from participating operators.
• Manage numbers through the Teams admin center.
• Enjoy operator-managed connectivity without needing your own SBCs.

Operator Connect is gaining popularity among enterprises that seek carrier flexibility without the infrastructure costs of Direct Routing. The list of certified operators is expanding and includes major carriers like AT&T, Verizon, BT, and Deutsche Telekom.

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 starting any port requests, follow these preparation steps:

• Inventory all phone numbers. This includes 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. Port requests need exact account information.
• Identify numbers that cannot be ported. This includes analog lines connected to physical devices, which may need to stay on traditional circuits or be converted using ATAs (Analog Telephone Adapters).
• Create a porting schedule. Group numbers by department or location, starting with the pilot group.

Porting Process and Timelines

The porting process begins with submitting a Letter of Authorization (LOA) to the gaining carrier. This letter is sent to the losing carrier for verification.

Standard number ports typically take 2-4 weeks to complete. In contrast, toll-free number ports require 4-8 weeks because of additional coordination between carriers.

During the porting window, there is a short cutover period. This typically lasts under 30 minutes. During this time, incoming calls to the ported numbers start routing to the new system.

To ensure a smooth transition, consider the following:

• Schedule the cutover during low-traffic hours.
• Have a rollback plan ready in case of issues.
• Assign temporary numbers in Teams before the porting is complete. This lets users make outbound calls right away.

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 manage inbound calls using automated greetings, menu options, and smart routing. To design effective enterprise auto-attendants, follow these best practices:

• Keep menu trees shallow with no more than 3 levels to reduce caller frustration.
• Provide a direct path to a live agent at every level.
• Configure business hours and after-hours routing with different greetings and options.
• Use dial-by-name directories for callers who know their contact.
• Implement nested auto-attendants for complex organizational structures.

Auto-attendants support multiple languages, custom greetings (either recorded audio or text-to-speech), and holiday schedules. For organizations moving from legacy IVR systems, map existing call flows to Teams auto-attendant features and identify any gaps that need third-party solutions.

Configuring Call Queues

Call queues distribute inbound calls to groups of agents using configurable routing methods. Teams supports several routing modes:

• Attendant routing: Rings all agents at the same time.
• Serial routing: Rings agents in a fixed order.
• Round robin: Distributes calls evenly among agents.
• Longest idle: Routes calls to the agent who has been available the longest.

You can set up overflow handling to redirect calls when the queue reaches a maximum wait time or call count. You can also define timeout actions for calls that go unanswered. Agents have the flexibility to opt in and out of queues as needed.

For enterprise contact center needs that go beyond the basic call queue features, consider Microsoft-certified solutions from:

• NICE
• Genesys
• Five9

These solutions offer 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 system. A recording bot is automatically invited to calls with users who have a compliance recording policy. This bot captures the audio stream and metadata, including:

• Participants
• Duration
• Timestamps

The bot then streams this data to the partner's recording platform for storage, retention, and analysis. Unlike the user-initiated Teams recording feature, compliance recording is automatic. Users cannot disable it, and it captures all call types, including PSTN, peer-to-peer, and group calls. It also 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-aligned consulting expertise work 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 the Teams Phone System to a pilot group of 50-100 users. Select users who are technically comfortable and willing to provide feedback. Ensure they represent different usage patterns, including:

• Heavy callers
• Light callers
• Reception staff
• Mobile workers

The pilot will:

• Validate call quality
• Ensure feature parity with the existing PBX
• Identify any integration issues before a wider rollout

During the pilot, measure:

• Call quality metrics (MOS scores, jitter, packet loss)
• User satisfaction
• Support ticket volume

Phase 2: Department-by-Department Rollout (Weeks 5-16)

Migrate departments in waves of 200-500 users. Start with departments that have simpler calling needs. Each wave follows a clear 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
• Post-wave review before moving to the next group

Keep the legacy PBX running during the rollout phase. This acts as a safety net for rollback if critical issues arise.

Phase 3: Legacy Decommission (Weeks 17-24)

Once all users are migrated and stable on the Teams Phone System, it's time to decommission the old PBX infrastructure. This process includes:

• Canceling legacy carrier circuits and trunks
• Decommissioning PBX hardware
• Updating emergency service registrations (E911) to reflect the new platform
• Archiving legacy voicemail and call records according to retention policies

The decommission phase is where cost savings begin. You will eliminate expenses related to legacy PBX maintenance contracts, dedicated voice circuits, and hardware support.

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 many certified devices. This includes:

• Desk phones from Yealink, Poly, AudioCodes, and Crestron
• Headsets and speakerphones for soft-phone users
• Teams Rooms devices for conference rooms
• Common area phones for lobbies, break rooms, and shared spaces

For enterprise deployments, standardize on 2-3 certified device models. This will 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