Microsoft teams phone
Verified 2026-09-24 · 58 sources · tier 2 · 1 disputed
Microsoft describes Teams Phone as its technology for call control and PBX capabilities delivered in the Microsoft 365 cloud 5. By default, calls between Teams users in the same organization are handled natively within Teams and never go to the PSTN 23.
Architecture and PSTN Connectivity
A PSTN solution is separate from a Teams Phone license: the PSTN solution supplies phone numbers and domestic, international, and emergency PSTN access, while the Teams Phone license entitles the user to enhanced calling capabilities and access to that PSTN solution 34. To use PSTN telephony with Teams Phone, a user account must be licensed with the Teams Phone application and equipped with a PSTN solution from a PSTN service provider 58. A single Teams tenant can have more than 1 PSTN integration, and Microsoft states that any combination of PSTN solutions is supported 27.
Microsoft lists 4 PSTN connectivity models for Teams Phone: Microsoft Teams Calling Plan, Operator Connect, Teams Phone Mobile, and Direct Routing 19.
- Microsoft Teams Calling Plan: Microsoft acts as the operator and supplies PSTN access, phone numbers, US emergency screening, and support with a 99.999% reliability SLA; this model requires a Calling Plan license 4. If Microsoft provides PSTN access and numbers, the user requires a Microsoft Calling Plan license in addition to Teams Phone licensing 3.
- Operator Connect: Uses certified third-party operators that have completed PSTN integration with Microsoft 32. The customer contracts with the operator and enables them in the Teams admin center without deploying a customer Session Border Controller (SBC) 32. Operator Connect requires users to hold Teams Phone licenses and be configured in Teams Only mode, and a certified operator must serve the target countries or regions 31. The operator handles PSTN connectivity, number provisioning, porting, calling services, and PSTN support, while Microsoft is responsible for Teams services, Teams Phone administration, the Teams admin center, and the integration layer 30.
- Direct Routing: Allows an organization to use any PSTN operator by connecting through a certified SBC procured, installed, and managed by the customer, an integrator, or a Direct-Routing-as-a-Service provider 7. Direct Routing is not supported in Islands coexistence mode 13. When using a PSTN operator other than Microsoft, Microsoft requires no further licensing beyond Teams Phone 3.
- Teams Phone Mobile: Supports user phone numbers only 26. Unlike Calling Plan, Operator Connect, and Direct Routing, it does not support Audio Conferencing or voice application (auto attendant and call queue) numbers 26.
Direct Routing Infrastructure
Direct Routing requires a Microsoft-certified SBC, PSTN trunks to the SBC, users homed online, a public IP address, an SBC FQDN in a verified tenant domain (excluding *.onmicrosoft.com) with public DNS, and a publicly trusted TLS certificate 11. Microsoft supports Teams Phone with Direct Routing only when certified SBCs are used, expects the SBC vendor to investigate first and escalate, and may decline support requests involving non-certified SBCs 9.
For Microsoft 365, Office 365, and GCC, the SBC connects to sip.pstnhub.microsoft.com, sip2.pstnhub.microsoft.com, and sip3.pstnhub.microsoft.com in priority order over SIP/TLS to port 5061 14. GCC High connects to sip.pstnhub.gov.teams.microsoft.us, and DoD connects to sip.pstnhub.dod.teams.microsoft.us 14.
Media exchange between Microsoft media processors and the SBC uses UDP/SRTP ports 3478–3481 and 49152–53247 in both directions 12. Microsoft recommends allocating at least 2 media ports per concurrent call on the SBC 12. Supported codecs between Teams and the SBC are SILK, G.711, G.722, G.729, and AMR-WB; AMR-WB is supported only without media bypass 10.
Survivable Branch Appliance
A Survivable Branch Appliance (SBA) uses Microsoft-supplied code distributed through SBC vendors and requires the SBC to be configured for media bypass so branch clients exchange media directly with the SBC 41. SBA mode is supported on Teams Windows and macOS desktop clients on physical machines, as well as on Teams Phones; VMs and web clients are not supported 38. SBA configuration—such as creating SBAs, creating and assigning branch survivability policies, and registering an Entra ID application—is performed exclusively via Teams PowerShell because the Teams admin center does not yet support it 40.
SBA accepts expired client authentication tokens for up to 7 days, cannot validate a client that has not connected to it within the last 24 hours, and remains operational for approximately 30 minutes if the tenant uses Continuous Access Evaluation tokens 42. Under SBA mode, emergency calls can be placed, but location information is not shared, and SBA does not support emergency call routing policies 39. Emergency dial strings bypass normalization and fail unless the regular voice routing policy includes a matching pattern 39.
Licensing and Resource Accounts
End-user Teams Phone access can be provisioned through license combinations such as Teams Enterprise plus Microsoft 365 E5 (no Teams), Teams Enterprise plus Teams Phone Standard, a legacy Microsoft 365 E5, or Office 365 F3 plus Teams Phone Standard for Frontline Workers 24. When any Microsoft 365 E5 license is used, assigning the stand-alone Microsoft Teams Phone Standard license is not necessary 16.
Microsoft Teams Phone Standard and Teams Phone with Calling Plan require a prerequisite license from a list that includes Microsoft 365 Business Basic, Business Standard, Business Premium, F1, F3, E3, and A3; Microsoft Teams EEA; Microsoft Teams Enterprise; Microsoft Teams Essentials (AAD Identity); and Office 365 F3, E1, E3, A1, and A3 55. Microsoft Teams Phone Standard for Frontline Workers requires Microsoft 365 F1, Microsoft 365 F3, or Office 365 F3 20. India PSTN requirements demand an India-specific Microsoft Teams Phone license obtained through a licensed operator in India via Operator Connect for India 22.
Shared devices and application accounts use distinct licensing models:
- Shared Devices: The Microsoft Teams Shared Device license (for common area phones) and the Microsoft Teams Rooms Pro license include the Microsoft 365 Phone System application 49. Shared Device licenses are supported only on telephone devices 49. Common Area Phones using Direct Routing do not require a Calling Plan license 8. A Microsoft Teams Enterprise license is not required for shared devices or voice applications 29.
- Resource Accounts: Every resource account for an auto attendant or call queue requires a Teams Phone Resource Account license, regardless of whether a telephone number is assigned 37. Microsoft states these licenses no longer cost anything, though administrators must still complete a purchase step at zero cost through their existing subscription purchasing channel; this is disputed, because other Microsoft documentation describes buying additional licenses at a cost 36. A Calling Plan is needed on a resource account only if it must dial out 37. Teams Phone Standard must never be assigned to resource accounts; when converting, administrators must remove Teams Phone Standard and assign the Resource Account license in the same action to prevent service interruptions to associated auto attendants and call queues 28.
Calling Features and Shared Calling
Auto attendants and call queues require Teams Phone licensing and resource accounts with Teams Phone Resource Account licenses, rather than a standalone Teams Enterprise license 1. Call park and retrieve requires Teams Phone; parking a call generates a unique code used by the parker or another user to retrieve it 2. Call delegation (shared line appearance) requires Teams Phone and supports barge and shared history 6. Users do not need a Teams Phone license to receive transferred calls, but a license is required to transfer calls to PSTN numbers 56. Teams Phone is also required for placing calls by extension or PSTN number, PSTN forwarding, simultaneous ring to PSTN numbers, dial plans, emergency calling, unassigned number routing, and PSTN call blocking 33. SMS in Teams is available for users with numbers acquired through a Microsoft Calling Plan in the United States (including Puerto Rico) or Canada 54.
Under Shared Calling, users do not receive dedicated numbers; inbound PSTN calls reach an auto attendant through a resource account's number, and outbound calls present that auto attendant's caller ID 45. Users need only a Teams Phone license without dedicated numbers or calling plans, though a resource account using a Microsoft service number requires a pay-as-you-go Calling Plan license 44. Shared Calling is available in public clouds only and is not available in GCC High and DoD 47.
Microsoft's Shared Calling setup order is: license users for Teams Phone and enable voice without assigning numbers; assign a number to the resource account; associate it with an auto attendant; assign it an emergency location; configure service numbers; create a voice routing policy without PSTN usages; enable emergency calling; create the Shared Calling policy; assign it to users; optionally configure extension dialing 48.
Managing Shared Calling via TeamsSharedCallingRoutingPolicy cmdlets requires Teams PowerShell Module version 5.5.0 or later, or configuration via the Teams admin center 46.
SIP Gateway
SIP Gateway supports compatible SIP devices, including Cisco IP phones, provided Cisco enterprise firmware is first converted to multiplatform (MPP) firmware 50. To use SIP Gateway, Teams users must have a phone number with PSTN calling enabled, plus Microsoft Teams, Skype for Business Online (Plan 2), Microsoft Phone System and PSTN connectivity 52. SIP Gateway is not yet available for DoD 52.
Stale devices are offboarded automatically: paired (signed-in) devices after 30 days without connection, and unpaired (signed-out) devices after 14 days 53. Offboarded devices can be onboarded again after a factory reset 53. SIP devices can act as call queue agents; however, SIP Gateway does not publish presence, preventing the use of presence-based routing 51.
Emergency Calling
Dynamic emergency calling routes emergency calls and notifies security personnel using the client's current location, supported across Calling Plans, Operator Connect, Teams Phone Mobile, and Direct Routing 15. Direct Routing requires specific emergency call routing policies, whereas other PSTN models rely on the carrier for much of the routing configuration 17.
To associate an emergency location with a network identifier for dynamic emergency calling, the emergency address must be validated and carry a geo code; addresses generated through the Teams admin center map search receive both automatically 18. Security desk notifications are supported for Microsoft Calling Plans, Operator Connect, and Direct Routing, conferencing security personnel into the call according to the emergency calling policy 43.
See also
- See also Microsoft teams direct routing.
- See also Setting up Microsoft Teams Direct Routing.
- See also Teams sip gateway.
- See also CUCM to Teams Phone migration.
Applicability
Managing Shared Calling via PowerShell requires Teams PowerShell Module version 5.5.0 or later 46. In GCC High and DoD clouds, several features are not yet available: secondary ringer, voicemail, enhanced delegation call settings, transfer to voicemail mid-call, dialing numbers from the search bar, Entra ID reverse number lookup, Private Line, Multi-line, skip internal VoIP reverse number lookup, and Shared Calling 21. SIP Gateway is not yet available in DoD clouds 52. SMS via Calling Plans is restricted to the United States (including Puerto Rico) and Canada 54. Operator Connect for India requires an India-specific license obtained through an in-country operator 22.
What remains uncertain
The timeline for making Shared Calling, SIP Gateway, and other GCC High and DoD gap features available in sovereign government clouds is not covered by the sources below.
See also
Configures
- Setting up Microsoft Teams Direct Routing — Inbound relationship: teams-direct-routing-setup configures microsoft-teams-phone. Direct Routing is one of four PSTN connectivity options for Teams Phone.
Migrates to
- CUCM to Teams Phone migration — Inbound relationship: cucm-to-teams-phone migrates-to microsoft-teams-phone. Teams Phone is the target system of that migration guide.
Referenced by
- Setting up Microsoft Teams Direct Routing — Target platform of the guide
- Setting up Microsoft Teams auto attendants and call queues — Guide configures the auto attendant and call queue voice applications of Teams Phone; licensing and PSTN-model vocabulary comes from that topic.
- Setting up dynamic emergency calling in Microsoft Teams — Configuration guide for the dynamic emergency calling feature of Teams Phone across Calling Plan; Operator Connect and Direct Routing
- Building a hybrid Unified CM and Teams Phone environment for a phased migration — Reuses the Teams Phone licensing; PSTN-model; Direct Routing infrastructure and emergency-calling claims recorded for that topic.
- CUCM to Teams Phone migration — The target system. No topic packet exists for Teams Phone yet; the registry's Direct Routing; SIP Gateway; SBA; emergency calling and licensing claims already sit under this guide's topic id.
Sources
- 1Auto attendants and call queues are not available with a Teams Enterprise license alone; they require Teams Phone licensing, with resource accounts using Teams Phone Resource Account licenses.Teams Phone features · Teams Phone features, table 'Teams calling features', rows 'Auto attendants' and 'Call queues' · Checked 2026-09-24
- 2Call park and retrieve requires Teams Phone; when a call is parked the service generates a unique code that the parker or another user can use to retrieve it.Teams Phone features · Teams Phone features, table 'Teams calling features', row 'Call park and retrieve' · Checked 2026-09-24
- 3If Microsoft provides PSTN access and numbers, the user needs a Microsoft Calling Plan license in addition to Teams Phone licensing; if a PSTN operator other than Microsoft is used, Microsoft requires no further licensing because PSTN costs come from that operator.Teams Phone licensing · Teams Phone licensing, section 'Licensing Teams Phone - adding PSTN' · Checked 2026-09-24
- 4With Microsoft Teams Calling Plan, Microsoft is the operator and supplies PSTN access, phone numbers, US emergency screening and support with a 99.999% reliability SLA; it requires a Calling Plan license.PSTN connectivity options · PSTN connectivity options, bullet 'Microsoft Teams Calling Plan' · Checked 2026-09-24
- 5Microsoft describes Teams Phone as its technology for call control and PBX capabilities delivered in the Microsoft 365 cloud.What is Teams Phone · What is Teams Phone, opening paragraph · Checked 2026-09-24
- 6Call delegation, which Microsoft also calls shared line appearance, requires Teams Phone and supports barge and shared history.Teams Phone features · Teams Phone features, table 'Teams calling features', row 'Call delegation' · Checked 2026-09-24
- 7Direct Routing lets an organization use any PSTN operator by connecting it through a certified SBC that is procured, installed and managed by the customer, an integrator or a Direct-Routing-as-a-Service provider.PSTN connectivity options · PSTN connectivity options, bullet 'Direct Routing' · Checked 2026-09-24
- 8When Direct Routing is used, a Calling Plan license is not required for Common Area Phones.Plan Direct Routing · Plan Direct Routing, section 'Supported endpoints' · Checked 2026-09-24
- 9Microsoft supports Teams Phone with Direct Routing only when certified SBCs are used, expects the SBC vendor to investigate first and escalate, and may decline support requests involving non-certified SBCs.Plan Direct Routing · Plan Direct Routing, sections 'Supported Session Border Controllers (SBCs)' and 'Support boundaries' · Checked 2026-09-24
- 10Direct Routing supports SILK, G.711, G.722, G.729 and AMR-WB between Teams and the SBC, with AMR-WB supported only without media bypass.Plan Direct Routing · Plan Direct Routing, section 'Supported codecs' · Checked 2026-09-24
- 11Direct Routing requires a Microsoft-certified SBC, PSTN trunks to it, users homed online, a public IP, an SBC FQDN in a verified tenant domain (not *.onmicrosoft.com) with public DNS, and a publicly trusted TLS certificate.Plan Direct Routing · Plan Direct Routing, section 'Infrastructure requirements' table and section 'SBC domain names' · Checked 2026-09-24
- 12Direct Routing media between Microsoft media processors and the SBC uses UDP/SRTP ports 3478-3481 and 49152-53247 in both directions, and Microsoft recommends at least two media ports per concurrent call on the SBC.Plan Direct Routing · Plan Direct Routing, section 'Media ports' table and Tip · Checked 2026-09-24
- 13Direct Routing is not supported in Islands coexistence mode.Plan Direct Routing · Plan Direct Routing, section 'Licensing requirements', Note · Checked 2026-09-24
- 14For Microsoft 365, Office 365 and GCC, the SBC connects to sip.pstnhub.microsoft.com, sip2.pstnhub.microsoft.com and sip3.pstnhub.microsoft.com in priority order over SIP/TLS to port 5061; GCC High uses sip.pstnhub.gov.teams.microsoft.us and DoD uses sip.pstnhub.dod.teams.microsoft.us.Plan Direct Routing · Plan Direct Routing, sections 'SIP signaling: FQDNs', 'SIP signaling: GCC High', 'SIP signaling: DoD', 'SIP signaling ports' · Checked 2026-09-24
- 15Dynamic emergency calling, which routes emergency calls and notifies security personnel based on the Teams client's current location, is available for Microsoft Calling Plans, Operator Connect, Teams Phone Mobile and Direct Routing.Plan and manage emergency calling · Plan and manage emergency calling, section 'Dynamic emergency calling' · Checked 2026-09-24
- 16Where any Microsoft 365 E5 license is used, it is not necessary to also assign the stand-alone Microsoft Teams Phone Standard license.Teams Phone licensing · Teams Phone licensing, section 'Licensing Teams Phone - for end users', paragraph after the example list · Checked 2026-09-24
- 17Direct Routing requires specific emergency call routing policies, whereas with the other PSTN options the carrier handles much of the emergency call routing configuration.Plan and manage emergency calling · Plan and manage emergency calling, section 'Emergency call routing' · Checked 2026-09-24
- 18To assign an emergency location to a network identifier for dynamic emergency calling, the emergency address must be validated and carry a geo code; addresses created with the Teams admin center map search get both automatically.Plan and manage emergency calling · Plan and manage emergency calling, sections 'Emergency address validation' and 'Emergency address geo codes', Important block · Checked 2026-09-24
- 19Microsoft lists four PSTN connectivity models for Teams Phone: Microsoft Teams Calling Plan, Operator Connect, Teams Phone Mobile and Direct Routing.PSTN connectivity options · PSTN connectivity options, section 'PSTN connectivity options' · Checked 2026-09-24
- 20Microsoft Teams Phone Standard for Frontline Workers requires Microsoft 365 F1, Microsoft 365 F3 or Office 365 F3 as its prerequisite license.Teams Phone licensing · Teams Phone licensing, prerequisite license table row 'Microsoft Teams Phone Standard for Frontline Workers' · Checked 2026-09-24
- 21In GCC High and DoD clouds, Microsoft lists as not yet available: secondary ringer, voicemail and enhanced delegation call settings; transfer to voicemail mid-call; calling a number from the search bar; Entra ID reverse number lookup; Private Line and Multi-line; skip internal VoIP reverse number lookup; and Shared Calling.Teams Phone features · Teams Phone features, section 'Availability in GCC High and DoD clouds' · Checked 2026-09-24
- 22India PSTN requirements need a separate, India-specific Microsoft Teams Phone license obtained from a licensed telecom operator in India (Operator Connect for India).Teams Phone licensing · Teams Phone licensing, section 'Licensing Teams Phone - adding PSTN', India paragraph · Checked 2026-09-24
- 23By default, calls between Teams users in the same organization are handled natively within Teams and never go to the PSTN.What is Teams Phone · What is Teams Phone, second paragraph · Checked 2026-09-24
- 24Examples of license combinations that grant Teams Phone to end users include Teams Enterprise plus Microsoft 365 E5 (no Teams), Teams Enterprise plus Teams Phone Standard, a legacy Microsoft 365 E5, and Office 365 F3 plus Teams Phone Standard for Frontline Workers.Teams Phone licensing · Teams Phone licensing, section 'Licensing Teams Phone - for end users', example list · Checked 2026-09-24
- 25Which base licenses a Teams Phone deployment actually holds (a with-Teams suite, a no-Teams suite plus Teams Enterprise, or Teams EEA) likely depends on when and where the tenant bought its suite, because Microsoft changed suite packaging in October 2023 (EEA), April 2024 (worldwide) and November 2025; migration licensing should be checked against the tenant's real SKUs.inferredEvolving our productivity offerings to resolve European competition concerns about Teams · Synthesis of global-availability paragraph with Teams Phone licensing prerequisite table · Checked 2026-09-24
- 26Teams Phone Mobile supports user phone numbers only; unlike Calling Plan, Operator Connect and Direct Routing, it does not support Audio Conferencing or voice application (auto attendant and call queue) numbers.PSTN connectivity options · PSTN connectivity options, Note after the four models and comparison table row 'Supports Audio Conferencing and voice application numbers' · Checked 2026-09-24
- 27A single Teams tenant can have more than one PSTN integration, and Microsoft states that any combination of PSTN solutions is supported.What is Teams Phone · What is Teams Phone, add-on options list, PSTN operator solution sub-bullets · Checked 2026-09-24
- 28Teams Phone Standard must not be assigned to resource accounts; when converting, remove Teams Phone Standard and assign the Resource Account license in the same license activity, otherwise the resource account (and its auto attendants and call queues) may stop working.Microsoft Teams Phone Resource Account licenses · Microsoft Teams Phone Resource Account licenses, section 'Change an existing resource account to use a Microsoft Teams Phone Resource Account license', Warning block · Checked 2026-09-24
- 29A Microsoft Teams Enterprise license is not required when licensing Teams Phone for shared devices or for voice applications.Teams Phone licensing · Teams Phone licensing, section 'Considerations', first paragraph · Checked 2026-09-24
- 30Under Operator Connect, the operator is responsible for PSTN connectivity, number provisioning and porting, calling services and PSTN-related support; Microsoft is responsible for Teams services, Teams Phone administration, the Teams admin center and the Teams-to-operator integration.Plan for Operator Connect · Plan for Operator Connect, section 'Support boundaries' · Checked 2026-09-24
- 31Operator Connect requires users to have Teams Phone licenses and to be configured in Teams Only mode, and a certified operator must serve the countries or regions being deployed.Plan for Operator Connect · Plan for Operator Connect, section 'Step 1: Verify prerequisites' · Checked 2026-09-24
- 32Operator Connect uses certified third-party operators that have already completed PSTN integration with Microsoft; the customer needs a contract with the operator and enables the operator in the Teams admin center, with no customer-deployed SBC.Plan for Operator Connect · Plan for Operator Connect, introduction and section 'Step 4: Configure Operator Connect' · Checked 2026-09-24
- 33Placing calls by extension or PSTN number, forwarding and simultaneous ring to PSTN numbers, dial plans, emergency calling, unassigned number routing and call blocking of PSTN numbers are all listed as requiring Teams Phone.Teams Phone features · Teams Phone features, table 'Teams calling features', rows 'Call answer/initiate (by extension or PSTN phone number)', 'Call forwarding options and simultaneous ring', 'Dial plans', 'Emergency calling', 'Unassigned number routing', 'Call blocking' · Checked 2026-09-24
- 34A PSTN solution is separate from a Teams Phone license: the PSTN solution supplies phone numbers and domestic, international and emergency PSTN access, while the Teams Phone license entitles the user to enhanced calling capabilities and access to that PSTN solution.What is Teams Phone · What is Teams Phone, Note block after the add-on options list · Checked 2026-09-24
- 35Effective 1 November 2025, new customers worldwide can again buy Microsoft 365 and Office 365 suites either with or without Teams, and the minimum price difference for E3 and E5 is EUR 8.00 (USD 8.55) per user per month, held for a seven-year enforcement period.Evolving our productivity offerings to resolve European competition concerns about Teams · Evolving our productivity offerings to resolve European competition concerns about Teams, global-availability and pricing paragraphs · Checked 2026-09-24
- 36Microsoft states there is no longer any cost for Teams Phone Resource Account licenses, but the admin must still complete a Buy step at zero cost through the same purchasing channel used for the subscription containing Teams Phone.disputedMicrosoft Teams Phone Resource Account licenses · Microsoft Teams Phone Resource Account licenses, opening Note and section 'How to obtain Microsoft Teams Phone Resource Account licenses' step 9 Note · Checked 2026-09-24
- 37Every resource account for an auto attendant or call queue must be assigned a Teams Phone Resource Account license, whether or not it will be assigned a telephone number; a Calling Plan is needed only if the resource account must dial out.Microsoft Teams Phone Resource Account licenses · Microsoft Teams Phone Resource Account licenses, paragraphs 1-2 and second Note · Checked 2026-09-24
- 38SBA mode is supported on the Teams Windows and macOS desktop clients and on Teams Phones, and only on desktop clients running on a physical machine; VMs and web clients are not supported.Survivable Branch Appliance for Direct Routing · Direct Routing SBA, sections 'Supported Teams clients' and 'How it works' · Checked 2026-09-24
- 39In SBA mode, emergency calls can still be placed but location information is not shared, and SBA does not support emergency call routing policies; emergency dial strings bypass normalization, so they fail unless the regular voice routing policy has a matching pattern.Survivable Branch Appliance for Direct Routing · Direct Routing SBA, section 'Known issues and considerations', 'In SBA mode, the following user actions aren't supported' · Checked 2026-09-24
- 40SBA configuration (creating SBAs, creating and assigning the branch survivability policy, and registering an Entra ID application) is done only with Teams PowerShell; the Teams admin center does not yet support the feature.Survivable Branch Appliance for Direct Routing · Direct Routing SBA, section 'Configuration' · Checked 2026-09-24
- 41A Survivable Branch Appliance is Microsoft-supplied code distributed through SBC vendors, and it requires the SBC to be configured for media bypass so branch Teams clients can exchange media directly with the SBC.Survivable Branch Appliance for Direct Routing · Direct Routing SBA, section 'Prerequisites' · Checked 2026-09-24
- 42SBA accepts expired client authentication tokens for up to 7 days, cannot validate a client that has not connected to it in the last 24 hours, and stays operational for only about 30 minutes if the tenant uses Continuous Access Evaluation tokens.Survivable Branch Appliance for Direct Routing · Direct Routing SBA, section 'Known issues and considerations' · Checked 2026-09-24
- 43Microsoft lists security desk notifications for emergency calls as available with Microsoft Calling Plans, Operator Connect and Direct Routing; the security desk is conferenced into the call as set by the Teams emergency calling policy.Plan and manage emergency calling · Plan and manage emergency calling, section 'Security desk notifications' · Checked 2026-09-24
- 50SIP Gateway supports compatible SIP devices including Cisco IP phones, but Cisco devices running enterprise firmware must first be converted to multiplatform (MPP) firmware.Plan SIP Gateway · Plan SIP Gateway, introduction and section 'Compatible devices', Cisco row remark · Checked 2026-09-24
- 51SIP devices on SIP Gateway can be call queue agents, but SIP Gateway does not publish presence for them, so presence-based routing is not supported.Plan SIP Gateway · Plan SIP Gateway, section 'Benefits of SIP Gateway', bullet 'Call Queues and voice apps support' · Checked 2026-09-24
- 52To use SIP Gateway, Teams users must have a phone number with PSTN calling enabled, plus Microsoft Teams, Skype for Business Online (Plan 2), Microsoft Phone System and PSTN connectivity; SIP Gateway is not yet available for DoD.Plan SIP Gateway · Plan SIP Gateway, section 'Requirements to use SIP Gateway' and subsection 'Hardware, software, and licenses' · Checked 2026-09-24
- 53SIP Gateway automatically offboards stale devices: paired (signed-in) devices after 30 days without a connection and unpaired (signed-out) devices after 14 days, and an offboarded device can be onboarded again after a factory reset.Plan SIP Gateway · Plan SIP Gateway, section 'Benefits of SIP Gateway', bullet 'Off board stale devices' · Checked 2026-09-24
- 54SMS in Teams is offered for users assigned a number acquired through a Microsoft Calling Plan in the United States (including Puerto Rico) or Canada.Teams Phone features · Teams Phone features, section 'Additional Teams Phone functionality', 'SMS in Teams overview' · Checked 2026-09-24
- 55Microsoft Teams Phone Standard and Teams Phone with Calling Plan each require a prerequisite license; the listed prerequisites include Microsoft 365 Business Basic, Business Standard, Business Premium, F1, F3, E3 and A3, Microsoft Teams EEA, Microsoft Teams Enterprise, Microsoft Teams Essentials (AAD Identity), and Office 365 F3, E1, E3, A1 and A3.Teams Phone licensing · Teams Phone licensing, section 'Licensing Teams Phone - for end users', prerequisite license table rows 1 and 3 · Checked 2026-09-24
- 56Users do not need a Teams Phone license to receive calls transferred from another user, but they do need one to transfer calls to PSTN numbers.Teams Phone features · Teams Phone features, table 'Teams calling features', row 'Transfer a call, including consultative transfer to another user' · Checked 2026-09-24
- 57On 1 April 2024 Microsoft began offering commercial Microsoft 365 and Office 365 suites without Teams, plus a standalone Microsoft Teams Enterprise offering, in regions outside the EEA and Switzerland, while existing subscribers could keep, renew and add seats to their current plans.Realigning global licensing for Microsoft 365 · Realigning global licensing for Microsoft 365, opening announcement paragraph and existing-customer FAQ · Checked 2026-09-24
- 58To use PSTN telephony with Teams Phone, a user account must be licensed with the Teams Phone application and also be equipped with a PSTN solution from a PSTN service provider.PSTN connectivity options · PSTN connectivity options, section 'What is the Public Switched Telephone Network (PSTN)?' · Checked 2026-09-24
Documents
Evolving our productivity offerings to resolve European competition concerns about Teams
Microsoft Teams Phone Resource Account licenses
Plan and manage emergency calling
Plan Direct Routing
Plan for Operator Connect
Plan for Shared Calling
Plan SIP Gateway
PSTN connectivity options
Realigning global licensing for Microsoft 365
Survivable Branch Appliance for Direct Routing
Teams Phone features
Teams Phone licensing
What is Teams Phone
Cite this page
APA
WarmTransfer. (2026, September 24). Microsoft teams phone. WarmTransfer. https://warmtransfer.net/knowledge/microsoft-teams-phone
BibTeX
@misc{warmtransfer-microsoft-teams-phone,
title = {Microsoft teams phone},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/microsoft-teams-phone},
note = {Verified 2026-09-24}
}