You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Azure Communication Services is interoperable with Microsoft Teams. This is especially helpful for business-to-consumer use cases, where an external customer in a custom, branded Azure-powered app or website communicates with an employee using Microsoft Teams. This allows the external customer to enjoy a custom experience, and the employee to have all their communication needs satisfied in a single hub: Teams.
17
17
Azure Communication Services can interoperate with Teams in three ways:
18
-
1. Azure clients can add an individual Teams user to a 1:1 and group calls. This is ideal for customer service situations where your application is adding a Teams-hosted subject matter experts to a call to help agents improve their first call resolution rates.
18
+
- Azure clients can add an individual Teams user to a 1:1 and group calls. This is ideal for customer service situations where your application is adding Teams-hosted subject matter experts to a call to help agents improve their first call resolution rates.
19
19
2. Azure clients can directly call a Teams Voice App, such as Auto Attendant and Call Queues. Azure Communication Services enables you to connect customers from your website or application to Teams Voice Apps to handle requests and later handoff to Teams agents as configured in Teams admin center.
20
20
3. Azure clients can join Teams meetings. This type of interoperability is described on a separate page.
21
21
22
-
This page details capabilities for Teams (or M365) users in a call with Communication Services users (scenario #1). Your service can orchestrate and manage these calls, including adding Teams users to these calls, using Call automation SDK. Read more about it [here](../call-automation/call-automation-teams-interop.md).
22
+
This page details capabilities for Teams (or Microsoft 365) users in a call with Communication Services users (scenario #1). Your service can orchestrate and manage these calls, including adding Teams users to these calls, using Call automation SDK. Read more about it [here](../call-automation/call-automation-teams-interop.md).
Copy file name to clipboardExpand all lines: articles/communication-services/concepts/pricing/teams-interop-pricing.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -59,7 +59,7 @@ Teams meeting organizer's license covers the usage generated by Teams users join
59
59
| Teams users participate in Teams meeting with audio, video, screen sharing, and TURN services | Teams web, mobile, desktop client | $0 per minute |
60
60
61
61
### Teams Phone features
62
-
Most features require you to assign the Teams Phone license, and ensure that users are "enterprise voice enabled." To assign the license, use the [Set-CsPhoneNumberAssignment cmdlet](/powershell/module/teams/set-csphonenumberassignment) and set the **EnterpriseVoiceEnabled**paramter to $true. For additional information see [Set up Teams Phone in your organization](/microsoftteams/setting-up-your-phone-system).
62
+
Most features require you to assign the Teams Phone license, and ensure that users are "enterprise voice enabled." To assign the license, use the [Set-CsPhoneNumberAssignment cmdlet](/powershell/module/teams/set-csphonenumberassignment) and set the **EnterpriseVoiceEnabled**parameter to $true. For additional information see [Set up Teams Phone in your organization](/microsoftteams/setting-up-your-phone-system).
0 commit comments