Skip to content

Commit d4bc677

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

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

articles/communication-services/how-tos/call-automation/teams-interop-call-automation.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,8 +16,6 @@ services: azure-communication-services
1616

1717
# Add a Microsoft Teams user to an existing call using Call Automation
1818

19-
[!INCLUDE [Public Preview Notice](../../includes/public-preview-include.md)]
20-
2119
In this quickstart, we use the Azure Communication Services Call Automation APIs to add, remove and transfer call to a Teams user.
2220

2321
## Prerequisites
@@ -40,6 +38,9 @@ Tenant level setting that enables/disables federation between their tenant and s
4038
[Set-CsExternalAccessPolicy (SkypeForBusiness)](/powershell/module/skype/set-csexternalaccesspolicy)
4139
User policy that allows the admin to further control which users in their organization can participate in federated communications with Communication Services users.
4240

41+
Note that Teams user needs to have Phone license to use this feature. 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).
42+
43+
4344
<a name='step-2-use-the-graph-api-to-get-azure-ad-object-id-for-teams-users-and-optionally-check-their-presence'></a>
4445

4546
## Step 2: Use the Graph API to get Microsoft Entra object ID for Teams users and optionally check their presence

0 commit comments

Comments
 (0)