Source record · tier 2 current vendor documentation
Teams Phone extensibility overview - An Azure Communication Services article
- Publisher
- Microsoft
- URL
- https://learn.microsoft.com/en-us/azure/communication-services/concepts/interop/tpe/teams-phone-extensibility-overview
- Published
- 2026-07-16
- Updated
- unknown
- Accessed
- 2026-09-14
- HTTP status
- 200
- License
- Microsoft Learn terms of use (content copyright Microsoft); open licence for this page not verified; no-redistribution; short excerpts and locators only
Claims citing this source
- Inference: Teams Phone extensibility appears to be generally available, based on the 'general_availability' value in the ms.custom metadata of the Azure Communication Services TPE articles; none of the fetched pages states the release stage in body text. inference in context
- Teams Phone extensibility supports third-party IVR bots receiving calls from Teams Auto Attendants and from Teams Call Queues, including queue overflow, timeout and no-agent-available routing, as first-class entry points. fact in context
- Teams Phone extensibility requires a Teams Phone license for each agent and enterprise voice enabled. fact in context
- In a Teams Phone extensibility multi-persona setup, call history stays within the client the call is associated with, so the Teams client does not show CCaaS calls and the CCaaS client does not show Teams calls. fact in context
- An inbound PSTN call to the phone number on a Teams resource account triggers an Incoming Call Event Grid notification to the Azure Communication Services resource linked to that account, and the CCaaS server application answers it with the Call Automation SDK. fact in context
- A CCaaS client can place an outbound PSTN call on behalf of a Teams resource account using the Calling SDK onBehalfOfOptions parameter, so the called party sees the resource account's caller ID. fact in context
- In Teams Phone extensibility, Teams user personal phone numbers are not supported for outbound PSTN calling and can be used only for emergency calling. fact in context
- To keep agent presence in sync across Teams and CCaaS personas, the CCaaS ISV uses existing Microsoft Graph APIs to subscribe to and set Teams presence, which Microsoft says all ISVs already do in the Connect and Extend models. fact in context
- For an emergency call placed from a custom CCaaS client under Teams Phone extensibility, the PSAP callback alerts both the Teams client and the CCaaS client, whereas a call placed from the Teams client gets a callback only on the Teams client. fact in context
- Teams Phone extensibility supports Teams Calling Plans, Operator Connect and Direct Routing as PSTN connectivity options. fact in context
- The Teams resource account used for Teams Phone extensibility needs a Microsoft Teams Phone Resource Account license, which Microsoft says is included in the Teams Phone license. fact in context
- The initial Teams Phone extensibility release focuses call recording on Azure Communication Services Call Recording for CCaaS use cases on inbound and outbound calls. fact in context
- Microsoft does not recommend the Call Automation Redirect option for CCaaS scenarios, strongly recommends AddParticipant for adding CCaaS agents, and states that Redirect is not supported for on-behalf-of use cases. fact in context
- In a Teams Phone extensibility multi-persona setup there is no API to choose whether the Calling SDK client or the Teams client rings for an inbound call; Teams policy controls this. fact in context
- For the Teams Phone integration part of Teams Phone extensibility, the current release supports only Teams Phone service numbers. fact in context
Cite this source record
APA
WarmTransfer. (2026, July 16). Teams Phone extensibility overview - An Azure Communication Services article. WarmTransfer. https://warmtransfer.net/knowledge/sources/ms-learn-acs-tpe-overview
BibTeX
@misc{warmtransfer-ms-learn-acs-tpe-overview,
title = {Teams Phone extensibility overview - An Azure Communication Services article},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/sources/ms-learn-acs-tpe-overview},
note = {Microsoft, accessed 2026-09-14}
}