Microsoft Teams Phone: Modern Cloud Calling for Microsoft 365

Microsoft Teams Phone helps organizations replace or modernize legacy PBX systems with secure cloud calling, centralized administration, and flexible PSTN connectivity options for hybrid teams, frontline users, and distributed offices.

Why Teams Phone still matters in 2026

Chat and meetings are essential, but business still depends on reliable voice calling: customer calls, supplier coordination, reception desks, service teams, executives, field workers, and emergency scenarios. Microsoft Teams Phone extends Teams beyond internal collaboration by adding cloud PBX capabilities such as calling, transfer, hold, voicemail, auto attendants, call queues, caller ID, call park, delegation, and policy-based administration.

Instead of managing a traditional phone system separately from Microsoft 365, Teams Phone lets users place and receive calls from the Teams desktop app, browser, mobile app, certified Teams phones, and supported room or desk devices. Administration is handled through the Teams admin center, Microsoft 365 admin center, Microsoft Entra ID identity controls, and the Microsoft Teams PowerShell module.

Teams Phone licensing: what changed since Microsoft 365 Business Voice

Microsoft 365 Business Voice was a legacy SMB bundle and should no longer be used as the primary licensing reference. Current Teams voice deployments are typically built around Teams Phone licensing plus a PSTN connectivity option.

Common licensing paths include:

• Teams Phone Standard: Adds cloud PBX capabilities to eligible Microsoft 365 and Office 365 plans, such as many Business, Enterprise, Frontline, and education/government plans, depending on region and agreement.
• Teams Phone with Calling Plan: Combines Teams Phone capabilities with a Microsoft Calling Plan in supported countries/regions. This is often the simplest option for smaller organizations with standard calling needs.
• Microsoft 365 E5 or Office 365 E5: Includes Teams Phone capabilities, but does not by itself provide PSTN calling. Users still need Microsoft Calling Plans, Operator Connect, Direct Routing, Teams Phone Mobile, or another supported PSTN option.
• Audio Conferencing: Included with many Microsoft 365 and Office 365 subscriptions today, and available as an add-on for others. It should be reviewed separately from Teams Phone because licensing and availability vary by plan and geography.

For customers buying through CSP, licensing should also be reviewed in the context of the Microsoft New Commerce Experience (NCE), commitment terms, add-ons, Teams availability in your region, and whether users need dedicated phone numbers or can use shared calling scenarios.

Choose the right PSTN connectivity option

Teams Phone provides the cloud PBX. PSTN connectivity is what lets users call external phone numbers. The right model depends on geography, carrier requirements, existing contracts, compliance needs, and call routing complexity.

• Microsoft Calling Plans: Best when you want a Microsoft-managed calling option with simple setup, number acquisition or porting, and predictable administration in supported countries/regions.
• Operator Connect: Best when you want to use a participating telecom operator with carrier-managed PSTN connectivity integrated into the Teams admin center.
• Direct Routing: Best for complex environments, existing SIP trunks, on-premises voice infrastructure, phased migrations, custom routing, analog device integration, or countries where Microsoft Calling Plans and Operator Connect do not meet requirements. Direct Routing requires a certified Session Border Controller (SBC) and careful voice routing design.
• Teams Phone Mobile: Best when users need their mobile number integrated with Teams through a participating mobile operator, enabling a more native mobile calling experience while keeping Teams collaboration and policy controls.
• Shared calling: Useful for users who need occasional external calling but do not require a dedicated phone number. Suitability depends on licensing, policies, emergency calling design, and PSTN provider support.

Many organizations use more than one model—for example, Microsoft Calling Plans for headquarters, Operator Connect for regional offices, and Direct Routing for sites with specialized routing or legacy integration requirements.

Core calling features users expect

Teams Phone supports everyday calling workflows directly in the Teams client. Users can start calls from chat, contact cards, the Calls app, Outlook contacts, call history, or the dial pad if they are enabled for PSTN calling. A one-to-one call can be escalated to a group call or meeting, and users can continue collaborating with files, chat, and apps during the conversation.

Common capabilities include:

• Hold, resume, blind transfer, and consultative transfer
• Voicemail with transcription, where available
• Call forwarding, simultaneous ring, and unanswered-call settings
• Delegation for executives, assistants, and shared-line scenarios
• Call park and retrieve
• Caller ID policies and outbound calling restrictions
• Certified Teams devices for desks, common areas, meeting rooms, and shared spaces
• Teams mobile calling from iOS and Android
• Integration with Microsoft-certified contact center and compliance recording solutions

For mobile users, the Teams app can place Teams calls and PSTN calls when the user is licensed and enabled. Teams Phone Mobile goes further by integrating a user’s mobile identity with Teams through supported operators.

Auto attendants, call queues, and front-office routing

Teams Phone can replace many traditional PBX front-office features with cloud-managed call flows.

Auto attendants can answer calls, play greetings, route callers by menu option or voice input, support business hours and holidays, and transfer calls to people, resource accounts, call queues, voicemail, or external numbers when configured.

Call queues can distribute calls to groups such as sales, support, reception, billing, or service desks. They support greetings, music on hold, overflow and timeout handling, agent opt-in/out settings, presence-based routing options, and reporting capabilities depending on configuration and licensing.

For more advanced needs—such as skills-based routing, CRM screen pops, omnichannel support, workforce management, or regulated recording—organizations should evaluate Microsoft-certified contact center integrations for Teams.

Number management, porting, and emergency calling

Phone numbers can be acquired, assigned, ported, and managed from the Teams admin center or through provider-specific workflows, depending on the PSTN connectivity model. Microsoft Calling Plans support number acquisition and porting in supported countries/regions. Operator Connect and Direct Routing follow the carrier or SBC provider process.

Emergency calling must be planned early. Admins should configure validated emergency addresses, assign locations to users and numbers where required, and review dynamic emergency calling for offices and networks that support it. Emergency calling rules vary by country/region and by PSTN provider, so organizations should validate local requirements before rollout.

Toll-free numbers, service numbers, conferencing bridge numbers, and resource account numbers are also country/region dependent. Billing and funding for toll-free usage may vary depending on whether you use Microsoft Calling Plans, Operator Connect, Direct Routing, or another provider model.

Administration and automation

Teams Phone is managed primarily from the Teams admin center under Voice settings, including phone numbers, users, calling policies, caller ID policies, emergency policies, auto attendants, call queues, resource accounts, and voice routing configuration.

For repeatable administration and larger deployments, IT teams can use the current Microsoft Teams PowerShell module to automate user enablement, policy assignment, phone number assignment, voice route configuration, emergency policy deployment, and reporting tasks. Identity and access should be governed through Microsoft Entra ID, including conditional access, multifactor authentication, privileged role management, and lifecycle processes for joiners, movers, and leavers.

Good governance matters: define who can manage voice settings, standardize naming conventions, document call flows, test emergency calling, and maintain a rollback plan for number porting events.

A practical rollout plan

A successful Teams Phone project is not just a license assignment. A typical rollout includes:

1. Discovery: Review current PBX, carriers, contracts, phone numbers, analog devices, call flows, compliance requirements, and user personas.
2. Licensing design: Map users to Teams Phone Standard, Teams Phone with Calling Plan, E5, shared calling, common area phone, resource account, or contact center requirements.
3. PSTN design: Choose Microsoft Calling Plans, Operator Connect, Direct Routing, Teams Phone Mobile, or a hybrid model.
4. Network readiness: Validate bandwidth, firewall rules, quality of service, endpoint readiness, and office network locations for emergency calling.
5. Pilot: Test calling, number assignment, auto attendants, call queues, voicemail, emergency calling, devices, and reporting with a controlled user group.
6. Number porting and migration: Schedule porting windows, communicate changes, and keep fallback plans ready.
7. Adoption and support: Train users on transfers, voicemail, mobile calling, call delegation, and support escalation paths.
8. Optimization: Review call quality analytics, queue performance, policies, and license usage after go-live.

Key takeaways

• Microsoft 365 Business Voice is retired branding; current deployments should use Teams Phone licensing and a separate PSTN connectivity strategy.
• Microsoft 365 E5 and Office 365 E5 include Teams Phone capabilities, but external calling still requires Microsoft Calling Plans, Operator Connect, Direct Routing, Teams Phone Mobile, or another supported PSTN option.
• The best PSTN model depends on country availability, carrier preference, compliance needs, existing contracts, and routing complexity.
• Emergency calling, number porting, auto attendants, call queues, and user adoption should be planned before migration—not after go-live.
• Teams Phone can support simple SMB calling scenarios as well as complex enterprise voice architectures when licensing, network readiness, and governance are designed correctly.

Need help deciding between Microsoft Calling Plans, Operator Connect, Direct Routing, or Teams Phone Mobile? IT Partner can assess your current phone environment, review Microsoft 365/NCE licensing, plan number porting, configure Teams Phone, and support user adoption for a smooth cloud voice migration.