Skip to content

Commit efb72de

Browse files
authored
Update call-automation-teams-interop.md
1 parent 0994b0a commit efb72de

File tree

1 file changed

+1
-4
lines changed

1 file changed

+1
-4
lines changed

articles/communication-services/concepts/call-automation/call-automation-teams-interop.md

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -14,9 +14,6 @@ ms.custom: public_preview
1414

1515
# Deliver expedient customer service by adding Microsoft Teams users in Call Automation workflows
1616

17-
[!INCLUDE [Public Preview Notice](../../includes/public-preview-include.md)]
18-
[!INCLUDE [Teams Phone license](../../includes/teams-phone-license-include.md)]
19-
2017
Azure Communication Services Call Automation provides developers the ability to build programmable customer interactions using real-time event triggers to perform actions on the call. This programmability enables you to build intelligent calling workflows that can adapt to customer needs in real time and be fully customized for your business logic. You can learn more about the API [here](./call-automation.md). This document describes the interoperability Call Automation supports with Microsoft Teams.
2118

2219
Developers can use Call Automation APIs to add Teams users to their calling workflows and customer interactions, helping you deliver advanced customer service solutions​ with easy-to-use REST APIs and SDKs. This interoperability is offered over VoIP to reduce telephony infrastructure overhead. Developers can add Teams users to Azure Communication Services calls using the user's Entra object ID (OID).
@@ -44,7 +41,7 @@ Now, lets look at the scenario where Contoso is already using a CCaaS provider f
4441
3. Since customer call is handled by contact center provider, they need to configure an SBC with Azure Communication Services Direct Routing in order to route/connect calls to Microsoft. With this model, only the contact center provider needs to have an SBC setup. This SBC can handle connections to multiple Teams tenants, making it easy for developers to implement per-region multitenant trunks that maximize value. Contoso doesn't have to set up Teams Direct Routing for each tenant, thus reducing the telephony overhead and Contoso's onboarding time to contact center provider.
4542
1. With Teams interop built into Call Automation, Azure Communication Services then uses the Teams user’s ObjectId to add them to the call. The Teams user receives the incoming call notification. They accept and join the call.
4643

47-
44+
[!INCLUDE [Teams Phone license](../../includes/teams-phone-license-include.md)]
4845

4946
## Capabilities
5047

0 commit comments

Comments
 (0)