Microsoft Teams Enable Phone Systems
Enabling Microsoft Teams Phone System transforms Teams from a collaboration platform into a full enterprise voice solution capable of replacing traditional PBX hardware. Teams Phone System provides call routing, auto attendants, call queues, voicemail transcription, and PSTN connectivity -- all managed from the cloud. This guide covers the complete process for enabling Phone System in your Microsoft 365 tenant, from licensing through PSTN connectivity, auto attendant configuration, and go-live validation. EPC Group has enabled Teams Phone for organizations ranging from 50 to 50,000 users, and this guide reflects our proven deployment methodology.
Understanding Teams Phone System Architecture
Microsoft Teams Phone System (formerly Cloud PBX) is a cloud-hosted PBX that provides enterprise calling capabilities within Microsoft Teams. The architecture consists of three layers:
- Phone System - The PBX functionality in the cloud: call control, voicemail, auto attendants, call queues, call transfer, call park, music on hold, and boss/admin delegation
- PSTN connectivity - The connection between Teams and the public telephone network. This is how users make and receive calls to/from external phone numbers
- Endpoints - The devices users make calls from: Teams desktop app, mobile app, web browser, Teams-certified IP phones, and Teams Rooms devices
Step 1: Choose Your PSTN Connectivity Option
Before enabling Phone System, decide how you will connect to the public telephone network. Microsoft offers three options:
- Microsoft Calling Plans
- Microsoft provides phone numbers and PSTN minutes
- Simplest deployment -- no additional infrastructure required
- Available in select countries (US, UK, Canada, and others)
- Best for: Organizations wanting a fully managed solution with minimal complexity
- Operator Connect
- Choose from Microsoft-certified telecom operators
- Operator provides numbers and PSTN; managed through Teams admin center
- No on-premises infrastructure needed
- Best for: Organizations wanting carrier flexibility without Direct Routing complexity
- Direct Routing
- Connect your own Session Border Controller (SBC) to Teams
- Use any SIP trunk provider worldwide
- Maximum flexibility and cost optimization
- Requires technical expertise for SBC configuration and maintenance
- Best for: Organizations with existing SIP infrastructure, multinational deployments, or specific carrier requirements
Step 2: Acquire and Assign Licenses
Phone System licensing depends on your Microsoft 365 plan and chosen PSTN option:
- Phone System license:
- Included in Microsoft 365 E5
- Available as an add-on for Microsoft 365 E3, E1, Business Premium, Business Standard, F1, F3
- Also available as the standalone "Microsoft Teams Phone Standard" license
- PSTN license (if using Microsoft Calling Plans):
- Domestic Calling Plan, International Calling Plan, or Pay-as-you-go
- Calling Plan bundles include a set number of domestic/international minutes per month
- Assign both licenses to each user in admin.microsoft.com > Users > Licenses and apps
- Verify each user has a Usage location set in their profile
Step 3: Acquire and Assign Phone Numbers
Each user who makes and receives external calls needs a phone number. The process depends on your PSTN option:
- Microsoft Calling Plans - Get numbers from the Teams admin center > Voice > Phone numbers > Add. You can request new numbers or port existing numbers from your current carrier
- Operator Connect - Acquire numbers from your chosen operator. They appear in the Teams admin center once provisioned by the carrier
- Direct Routing - Use numbers from your SIP trunk provider. Assign them to users via PowerShell:
Set-CsPhoneNumberAssignment -Identity user@contoso.com -PhoneNumber "+14255551234" -PhoneNumberType DirectRouting
Step 4: Configure Auto Attendants and Call Queues
Auto attendants and call queues handle inbound calls to your main business numbers:
Auto Attendants
- Go to Teams admin center > Voice > Auto attendants
- Click Add and configure:
- Name, time zone, and language
- Greeting message (text-to-speech or upload audio file)
- Call routing options: menu prompts, directory search by name or extension, or redirect to a specific person/queue
- Business hours schedule with different routing for after-hours and holidays
- Assign a phone number (service number) to the auto attendant
Call Queues
- Go to Teams admin center > Voice > Call queues
- Click Add and configure:
- Greeting message and music on hold
- Call answering agents (users, groups, or Teams channels)
- Routing method: Attendant (ring all), Serial (round robin), Round Robin, or Longest Idle
- Overflow handling: what happens when the queue is full or wait time exceeds the threshold
- Timeout handling: what happens when no agent answers within the configured time
Step 5: Configure Voice Policies
Voice policies control calling behavior at the tenant and per-user level:
- Calling policies - Control features like call forwarding, simultaneous ring, voicemail, call delegation, and inbound call blocking
- Caller ID policies - Configure what caller ID is displayed for outbound calls (user's number, main company number, or anonymous)
- Emergency calling policies - Configure E911 compliance including emergency addresses, notification groups, and dynamic emergency calling for mobile users
- Voice routing policies (Direct Routing only) - Define which SIP trunks handle which call patterns using voice routes and PSTN usage records
- Dial plans - Normalize dialed numbers to E.164 format, supporting internal extensions and local dialing habits
Step 6: Test and Go Live
- Select 5-10 pilot users representing different roles and locations
- Validate inbound and outbound PSTN calling for each pilot user
- Test auto attendant menus by calling the main number and navigating all options
- Test call queues by calling when agents are available, busy, and offline
- Test voicemail by leaving messages and verifying transcription delivery
- Test emergency calling (coordinate with your local authority if required)
- Review call quality in the Call Quality Dashboard (CQD)
- Train end users on making/receiving calls, transferring, voicemail, and mobile usage
- Execute number porting from the legacy system on the planned cutover date
- Monitor call quality and user feedback for the first 30 days post-launch
Why Choose EPC Group for Teams Phone System
With 28+ years of enterprise Microsoft consulting, EPC Group has enabled Teams Phone System for organizations across healthcare, finance, education, and government. We handle every phase of the deployment: PSTN connectivity evaluation, license optimization, number porting, auto attendant and call queue design, emergency calling compliance, user training, and post-launch support.
- PSTN connectivity evaluation (Calling Plans vs. Operator Connect vs. Direct Routing)
- Session Border Controller deployment and configuration for Direct Routing
- Number porting from legacy PBX, Cisco, Avaya, and other systems
- Auto attendant and call queue design mirroring your organizational call flows
- E911 and emergency calling compliance (Kari's Law and RAY BAUM's Act)
- Call Quality Dashboard monitoring and optimization
- Ongoing managed services for Teams Phone
Enable Enterprise Voice with Teams Phone System
EPC Group delivers end-to-end Teams Phone System deployments that replace legacy PBX infrastructure with a modern, cloud-managed voice solution. Contact us for a free telephony assessment and migration plan.
Frequently Asked Questions
How long does it take to enable Teams Phone System?
For organizations using Microsoft Calling Plans, basic Phone System setup can be completed in 1-2 weeks including license assignment, number provisioning, and auto attendant configuration. For Direct Routing deployments involving SBC configuration and number porting from legacy systems, plan for 4-8 weeks. Enterprise deployments with complex call flows, multiple locations, and compliance requirements typically take 8-12 weeks with EPC Group managing the project.
Can I run Teams Phone alongside my existing PBX during migration?
Yes. Most organizations run a hybrid configuration during migration, where some users are on Teams Phone and others remain on the legacy PBX. Direct Routing supports this coexistence by routing calls between Teams and the existing PBX through the Session Border Controller. This allows a phased migration where you move departments or locations one at a time.
What about emergency calling (E911) compliance?
Teams Phone System supports E911 with static and dynamic emergency calling. Static addresses are assigned to users based on their office location. Dynamic emergency calling uses network-based location detection to determine the caller's emergency address automatically, even when they move between floors or buildings. This is critical for compliance with Kari's Law and RAY BAUM's Act, which require dispatchable location information for all 911 calls from multi-line telephone systems.
What is the call quality like with Teams Phone?
Call quality depends primarily on network quality. Microsoft provides the Call Quality Dashboard (CQD) and per-call analytics in the Teams admin center to monitor metrics like jitter, packet loss, and round-trip time. For enterprise deployments, EPC Group conducts network readiness assessments and recommends QoS (Quality of Service) configurations to prioritize voice traffic on your network, ensuring consistent call quality.
Can I integrate Teams Phone with my CRM or contact center?
Yes. Teams Phone integrates with CRM platforms like Dynamics 365, Salesforce, and ServiceNow through Teams-certified contact center solutions. Microsoft also offers a native Queues app for basic contact center scenarios. For advanced contact center requirements (skills-based routing, IVR, screen pops, supervisor monitoring), certified partners like NICE, Genesys, and Five9 provide Teams-integrated solutions. EPC Group evaluates and implements the right contact center integration for your requirements.