What Teams Phone Actually Replaces
Teams Phone is Microsoft's cloud PBX (private branch exchange) offering, licensed as an add-on that gives a user a real telephone number and the ability to place and receive calls to and from the public switched telephone network (PSTN), not just calls between Teams users on the same tenant. It replaces the traditional on-premises PBX hardware and desk-phone wiring that organizations historically maintained, moving call routing, voicemail, auto attendants, and call queues into the cloud alongside the rest of a user's Teams experience, so a single client handles chat, meetings, and phone calls without switching applications.
Cricket analogy: Teams Phone replacing an on-premises PBX is like a stadium replacing its old analog PA system with a fully digital broadcast setup that also handles instant replays and commentary from one integrated control room, instead of separate standalone boxes for each function.
PSTN Connectivity Models
Organizations connect Teams Phone to the PSTN in one of three ways: Calling Plans, where Microsoft itself acts as the telephony carrier and sells per-minute or unlimited domestic/international bundles directly through the Microsoft 365 admin center; Operator Connect, where a certified third-party carrier is pre-integrated with Teams so the admin selects the carrier and numbers from within the admin center without deploying any on-premises hardware; and Direct Routing, where the organization deploys or leases a certified Session Border Controller (SBC) that bridges Teams to any SIP trunk provider of their choosing, offering the most flexibility (and complexity) for organizations with existing carrier relationships or numbers in countries Microsoft doesn't directly support.
Cricket analogy: Calling Plans is like a board buying all its equipment directly from one official supplier with a single contract, Operator Connect is like the board selecting from a pre-vetted list of approved regional suppliers, and Direct Routing is like the board sourcing custom equipment from any supplier it chooses and integrating it itself.
Call Queues, Auto Attendants, and Voicemail
Beyond individual user calling, Teams Phone supports Call Queues, which hold and distribute inbound calls to a group of agents using routing methods like attendant (ring all simultaneously), serial (ring one at a time in order), or round-robin, and Auto Attendants, which present callers with a menu ('Press 1 for Sales, Press 2 for Support') that can route based on time-of-day or holiday schedules configured in the Teams admin center. Both features are configured through Resource Accounts — special Azure AD accounts that don't represent a real person but hold the license and phone number for the queue or auto attendant itself — and voicemail for any user or resource account can be customized per-language, transcribed automatically, and optionally routed to email as an audio attachment with the transcription in the message body.
Cricket analogy: A call queue's round-robin routing is like a bowling attack rotating overs evenly among the available bowlers rather than overusing one specialist, while an auto attendant's menu is like a stadium's automated announcement directing fans to the correct gate based on their ticket type.
# Microsoft Teams PowerShell - assign a phone number and enable Enterprise Voice
Connect-MicrosoftTeams
Set-CsPhoneNumberAssignment -Identity "jordan.lee@contoso.com" `
-PhoneNumber "+14255550123" `
-PhoneNumberType CallingPlan
Grant-CsOnlineVoiceRoutingPolicy -Identity "jordan.lee@contoso.com" `
-PolicyName $null # $null assigns the global/default policyResource Accounts used for call queues and auto attendants require a separate free license (Microsoft Teams Phone Resource Account license) plus either a Calling Plan, Operator Connect number, or Direct Routing assignment — they don't consume a standard user license even though they appear similar to a user object in Azure AD.
Direct Routing requires a Session Border Controller from Microsoft's certified list; connecting an uncertified SBC is unsupported and can cause call quality issues or failures that Microsoft support will not troubleshoot, since the certification process validates SIP signaling compatibility with Teams' calling infrastructure.
- Teams Phone is Microsoft's cloud PBX, giving users real PSTN telephone numbers within the Teams client.
- Three PSTN connectivity models exist: Calling Plans (Microsoft as carrier), Operator Connect (pre-integrated third-party carrier), and Direct Routing (self-managed SBC to any SIP trunk).
- Direct Routing offers the most flexibility but requires a certified Session Border Controller and more configuration complexity.
- Call Queues distribute inbound calls to agents via routing methods like attendant, serial, or round-robin.
- Auto Attendants present menu-driven call routing, often varying by time-of-day or holiday schedule.
- Resource Accounts hold the license and number for queues/auto attendants without representing a real person.
- Voicemail supports automatic transcription and can be routed to email with the transcript in the message body.
Practice what you learned
1. What does Teams Phone add on top of standard Teams calling between tenant users?
2. Which PSTN connectivity model requires the organization to deploy or lease a certified Session Border Controller?
3. What is a Resource Account used for in Teams Phone?
4. What routing method rings call queue agents one at a time in a fixed order?
5. Why is connecting an uncertified SBC to Direct Routing risky?
Was this page helpful?
You May Also Like
Teams Permissions and Roles
A practical guide to the role hierarchy in Microsoft Teams — from tenant admin down to channel member — and what each role can and cannot do.
Compliance and Retention Policies
How Microsoft Purview retention policies, eDiscovery, and legal hold apply to Teams chats, channels, and files to meet regulatory obligations.
Related Reading
Related Study Notes in Microsoft Technologies
Browse all study notesWindows 10 / UWP Development Study Notes
.NET · 30 topics
Microsoft TechnologiesWindows Batch Scripting Study Notes
Batch · 30 topics
Microsoft TechnologiesMFC (Microsoft Foundation Classes) Study Notes
C++ · 30 topics
Microsoft TechnologiesSilverlight Study Notes
.NET · 30 topics
Microsoft TechnologiesXAML Study Notes
.NET · 30 topics
Microsoft TechnologiesWPF (Windows Presentation Foundation) Study Notes
.NET · 30 topics