Merge pull request #249425 from ashwinder/Teams-interop

denrea · web-flow · commit 1cb80d4d488c · 2023-08-30T12:42:26.000-07:00
Update capabilities for SME consult
diff --git a/articles/communication-services/concepts/call-automation/call-automation-teams-interop.md b/articles/communication-services/concepts/call-automation/call-automation-teams-interop.md
@@ -43,39 +43,41 @@ The dataflow diagram depicts a canonical scenario where a Teams user is added to
 
 The following list presents the set of features that are currently available in the Azure Communication Services Call Automation SDKs for calls with Microsoft Teams users.
 
-| Feature Area          | Capability                                        | .NET   | Java  |
-| ----------------------| -----------------------------------------------   | ------ | ----- |
-| Pre-call scenarios    | Place new outbound call to a Microsoft Teams user  | ✔️    | ✔️    |
-|                       | Redirect (forward) a call to a Microsoft Teams user | ✔️    | ✔️    |
-|                       | Set custom display name for the callee when making a call offer to a Microsoft Teams user | Only on Microsoft Teams desktop client    | Only on Microsoft Teams desktop client    |
-| Mid-call scenarios    | Add one or more endpoints to an existing call with a Microsoft Teams user     | ✔️    | ✔️    |
-|                       | Play Audio from an audio file                     | ✔️    | ✔️    |
-|                       | Recognize user input through DTMF                 | ✔️    | ✔️    |
-|                       | Remove one or more endpoints from an existing call| ✔️    | ✔️    |
-|                       | Blind Transfer a 1:1 call to another endpoint     | ✔️    | ✔️    |
-|                       | Hang up a call (remove the call leg)              | ✔️    | ✔️    |
-|                       | Terminate a call (remove all participants and end call)| ✔️ | ✔️  |
-| Query scenarios       | Get the call state                                | ✔️    | ✔️    |
-|                       | Get a participant in a call                       | ✔️    | ✔️    |
-|                       | List all participants in a call                   | ✔️    | ✔️    |
-| Call Recording*        | Start/pause/resume/stop recording                 | ✔️    | ✔️    |
+| Feature Area          | Capability                                        | .NET   | Java  | Python | JavaScript |
+| ----------------------| -----------------------------------------------   | ------ | ----- |  ------ | ----- |
+| Pre-call scenarios    | Place new outbound call to a Microsoft Teams user  | ✔️    | ✔️    | ✔️    | ✔️    |
+|                       | Redirect (forward) a call to a Microsoft Teams user | ✔️    | ✔️    | ✔️    | ✔️    |
+|                       | Set custom display name for the callee when making a call offer to a Microsoft Teams user | Only on Microsoft Teams desktop and web client    | Only on Microsoft Teams desktop 
+ and web client    |
+| Mid-call scenarios    | Add one or more endpoints to an existing call with a Microsoft Teams user     | ✔️    | ✔️    |  ✔️    | ✔️    |
+|                       | Play Audio from an audio file                     | ✔️    | ✔️    | ✔️    | ✔️    |
+|                       | Recognize user input through DTMF                 | ❌    | ❌   | ❌    | ❌  |
+|                       | Remove one or more endpoints from an existing call| ✔️    | ✔️    | ✔️    | ✔️    |
+|                       | Blind Transfer a 1:1 call to another endpoint     | ✔️    | ✔️    | ✔️    | ✔️    |
+|                       | Hang up a call (remove the call leg)              | ✔️    | ✔️    | ✔️    | ✔️    |
+|                       | Terminate a call (remove all participants and end call)| ✔️ | ✔️  | ✔️    | ✔️    |
+| Query scenarios       | Get the call state                                | ✔️    | ✔️    | ✔️    | ✔️    |
+|                       | Get a participant in a call                       | ✔️    | ✔️    | ✔️    | ✔️    |
+|                       | List all participants in a call                   | ✔️    | ✔️    | ✔️    | ✔️    |
+| Call Recording*        | Start/pause/resume/stop recording (call recording notifications in Teams clients are supported for Teams desktop, web, iOS and Android)  | ✔️    | ✔️    | ✔️    | ✔️    |
 
 > [!IMPORTANT]
-> Azure Communication Services call recording notifications in Teams clients are not supported. You must obtain consent from and notify the parties of recorded communications in a manner that complies with the laws applicable to each participant. i.e., using the Play API available in Call Automation.
+> During Public preview, you won't be able to stop the call recording if it started after adding the Teams participant.
 
 ## Supported clients
 | Clients          | Support     |
 | -----------------| ----------- |
 | Microsoft Teams Desktop | ✔️ |
-| Microsoft Teams Web | ❌ |
+| Microsoft Teams Web | ✔️ |
 | Microsoft Teams iOS | ❌ |
 | Microsoft Teams Android | ❌ |
 | Azure Communications Services signed in with Microsoft 365 Identity | ❌ |
 
-## Roadmap
+Teams phone license is a must to use this feature. 
 
-1. Support for Microsoft Teams Web coming soon.
+## Roadmap
 1. Support for Azure Communications Services signed in with Microsoft 365 Identity coming soon.
+2. Support for Microsoft Teams iOS and Android clients coming soon. 
 
 ## Next steps
 
diff --git a/articles/communication-services/how-tos/call-automation/teams-interop-call-automation.md b/articles/communication-services/how-tos/call-automation/teams-interop-call-automation.md
@@ -9,7 +9,8 @@ ms.subservice: call-automation
 ms.topic: include
 ms.date: 03/28/2023
 ms.author: visho
-ms.custom: public_preview
+ms.custom: public_preview, devx-track-extended-java, devx-track-js, devx-track-python
+zone_pivot_groups: acs-js-csharp-java-python
 services: azure-communication-services
 ---
 
@@ -22,7 +23,7 @@ In this quickstart, we use the Azure Communication Services Call Automation APIs
 ## Prerequisites
 
 - An Azure account with an active subscription.
-- A Microsoft Teams tenant with administrative privileges.
+- A Microsoft Teams phone license and a Teams tenant with administrative privileges. Teams phone license is a must in order to use this feature, learn more about Teams licenses [here](https://www.microsoft.com/en-us/microsoft-teams/compare-microsoft-teams-bundle-options). Administrative privileges are required to authorize Communication Services resource to call Teams users, explained later in Step 1.  
 - A deployed [Communication Service resource](../../quickstarts/create-communication-resource.md) and valid connection string found by selecting Keys in left side menu on Azure portal.
 - [Acquire a PSTN phone number from the Communication Service resource](../../quickstarts/telephony/get-phone-number.md). Note the phone number you acquired to use in this quickstart. 
 - An Azure Event Grid subscription to receive the `IncomingCall` event.
@@ -31,16 +32,16 @@ In this quickstart, we use the Azure Communication Services Call Automation APIs
 
 ## Step 1: Authorization for your Azure Communication Services Resource to enable calling to Microsoft Teams users
 
-To enable calling through Call Automation APIs, a [Microsoft Teams Administrator](/azure/active-directory/roles/permissions-reference#teams-administrator) or [Global Administrator](/en-us/azure/active-directory/roles/permissions-reference#global-administrator) must explicitly enable the ACS resource(s) access to their tenant to allow calling.
+To enable calling through Call Automation APIs, a [Microsoft Teams Administrator](/azure/active-directory/roles/permissions-reference#teams-administrator) or [Global Administrator](/en-us/azure/active-directory/roles/permissions-reference#global-administrator) must explicitly enable the Communication Services resource(s) access to their tenant to allow calling.
 
 [Set-CsTeamsAcsFederationConfiguration (MicrosoftTeamsPowerShell)](/powershell/module/teams/set-csteamsacsfederationconfiguration)
-Tenant level setting that enables/disables federation between their tenant and specific ACS resources.
+Tenant level setting that enables/disables federation between their tenant and specific Communication Services resources.
 
 [Set-CsExternalAccessPolicy (SkypeForBusiness)](/powershell/module/skype/set-csexternalaccesspolicy)
-User policy that allows the admin to further control which users in their organization can participate in federated communications with ACS users.
+User policy that allows the admin to further control which users in their organization can participate in federated communications with Communication Services users.
 
 ## Step 2: Use the Graph API to get Azure AD object ID for Teams users and optionally check their presence
-A Teams user’s Azure Active Directory (Azure AD) object ID (OID) is required to add them to or transfer to them from an ACS call. The OID can be retrieved through 1) Office portal, 2) Azure AD portal, 3) Azure AD Connect; or 4) Graph API. The example below uses Graph API.
+A Teams user’s Azure Active Directory (Azure AD) object ID (OID) is required to add them to or transfer to them from a Communication Services call. The OID can be retrieved through 1) Office portal, 2) Azure AD portal, 3) Azure AD Connect; or 4) Graph API. The example below uses Graph API.
 
 Consent must be granted by an Azure AD admin before Graph can be used to search for users, learn more by following on the [Microsoft Graph Security API overview](/graph/security-concept-overview) document. The OID can be retrieved using the list users API to search for users. The following shows a search by display name, but other properties can be searched as well:
 
@@ -73,8 +74,10 @@ Response:
 
 ```
 
-## Step 3: Add a Teams user to an existing ACS call controlled by Call Automation APIs
-You need to complete the prerequisite step and have a web service app to control an ACS call. Using the callConnection object, add a participant to the call.
+## Step 3: Add a Teams user to an existing Communication Services call controlled by Call Automation APIs
+You need to complete the prerequisite step and have a web service app to control a Communication Services call. Using the callConnection object, add a participant to the call.
+
+::: zone pivot="programming-language-csharp"
 
 ```csharp
 CallAutomationClient client = new CallAutomationClient('<Connection_String>');
@@ -85,22 +88,128 @@ await answer.Value.CallConnection.AddParticipantAsync(
         SourceDisplayName = "Jack (Contoso Tech Support)"
     });
 ```
+
+::: zone-end
+
+::: zone pivot="programming-language-java"
+
+```java
+CallAutomationClient client = new CallAutomationClientBuilder().connectionString("<resource_connection_string>").buildClient();
+AnswerCallResult answer = client.answerCall(incomingCallContext, "<Callback_URI>"));
+answer.getCallConnection().addParticipant(
+    new CallInvite(new MicrosoftTeamsUserIdentifier("<Teams_User_Guid>"))
+        .setSourceDisplayName("Jack (Contoso Tech Support)"));
+```
+
+::: zone-end
+
+::: zone pivot="programming-language-javascript"
+
+```typescript
+const client = new CallAutomationClient("<resource_connection_string>");
+const answer = await client.answerCall(incomingCallContext, "<Callback_URI>"));
+answer.callConnection.addParticipant({
+    targetParticipant: { microsoftTeamsUserId: "<Teams_User_Guid>" },
+    sourceDisplayName: "Jack (Contoso Tech Support)"
+});
+```
+
+::: zone-end
+
+::: zone pivot="programming-language-python"
+
+```python
+call_automation_client = CallAutomationClient.from_connection_string("<resource_connection_string>")
+answer = call_automation_client.answer_call(incoming_call_context = incoming_call_context, callback_url = "<Callback_URI>")
+call_connection_client = call_automation_client.get_call_connection(answer.call_connection_id)
+call_connection_client.add_participant(target_participant = CallInvite(
+    target = MicrosoftTeamsUserIdentifier(user_id="<USER_ID>"),
+    source_display_name = "Jack (Contoso Tech Support)"))
+```
+
+::: zone-end
+
+-----
+
 On the Microsoft Teams desktop client, Jack's call will be sent to the Microsoft Teams user through an incoming call toast notification.
 
 ![Screenshot of Microsoft Teams desktop client, Jack's call is sent to the Microsoft Teams user through an incoming call toast notification.](./media/incoming-call-toast-notification-teams-user.png)
 
-After the Microsoft Teams user accepts the call, the in-call experience for the Microsoft Teams user will have all the participants displayed on the Microsoft Teams roster.
+After the Microsoft Teams user accepts the call, the in-call experience for the Microsoft Teams user will have all the participants displayed on the Microsoft Teams roster. Note that your application that is managing the call using Call Automation API will remain hidden to Teams user on the call screen. 
 ![Screenshot of Microsoft Teams user accepting the call and entering the in-call experience for the Microsoft Teams user.](./media/active-call-teams-user.png)
 
-## Step 4: Remove a Teams user from an existing ACS call controlled by Call Automation APIs
+## Step 4: Remove a Teams user from an existing Communication Services call controlled by Call Automation APIs
+
+::: zone pivot="programming-language-csharp"
+
 ```csharp
 await answer.Value.CallConnection.RemoveParticipantAsync(new MicrosoftTeamsUserIdentifier('<Teams_User_Guid>'));
 ```
 
-### Optional feature: Transfer to a Teams user from an existing ACS call controlled by Call Automation APIs
+::: zone-end
+
+::: zone pivot="programming-language-java"
+
+```java
+answer.getCallConnection().removeParticipant(new MicrosoftTeamsUserIdentifier("<Teams_User_Guid>"));
+```
+
+::: zone-end
+
+::: zone pivot="programming-language-javascript"
+
+```typescript
+answer.callConnection.removeParticipant({ microsoftTeamsUserId: "<Teams_User_Guid>" });
+```
+
+::: zone-end
+
+::: zone pivot="programming-language-python"
+
+```python
+call_connection_client.remove_participant(target_participant = MicrosoftTeamsUserIdentifier(user_id="<USER_ID>"))
+```
+
+::: zone-end
+
+-----
+
+### Optional feature: Transfer to a Teams user from an existing Communication Services call controlled by Call Automation APIs
+
+::: zone pivot="programming-language-csharp"
+
 ```csharp
-await answer.Value.CallConnection.TransferCallToParticipantAsync(new CallInvite(new MicrosoftTeamsUserIdentifier('<Teams_User_Guid>')));
+await answer.Value.CallConnection.TransferCallToParticipantAsync(new MicrosoftTeamsUserIdentifier('<Teams_User_Guid>'));
+```
+
+::: zone-end
+
+::: zone pivot="programming-language-java"
+
+```java
+answer.getCallConnection().transferCallToParticipant(new MicrosoftTeamsUserIdentifier("<Teams_User_Guid>"));
+```
+
+::: zone-end
+
+::: zone pivot="programming-language-javascript"
+
+```typescript
+answer.callConnection.transferCallToParticipant({ microsoftTeamsUserId: "<Teams_User_Guid>" });
+```
+
+::: zone-end
+
+::: zone pivot="programming-language-python"
+
+```python
+call_connection_client.transfer_call_to_participant(target_participant = MicrosoftTeamsUserIdentifier(user_id = "<USER_ID>"))
 ```
+
+::: zone-end
+
+-----
+
 ### How to tell if your Tenant isn't enabled for this preview?
 ![Screenshot showing the error during Step 1.](./media/teams-federation-error.png)
 
@@ -110,7 +219,8 @@ If you want to clean up and remove a Communication Services subscription, you ca
 
 ## Next steps
 
+- Learn how to [record your calls](../../quickstarts/voice-video-calling/get-started-call-recording.md).
 - Learn more about [Call Automation](../../concepts/call-automation/call-automation.md) and its features.
-- Learn more about capabilities of [Teams Interoperability support with ACS Call Automation](../../concepts/call-automation/call-automation-teams-interop.md)
+- Learn more about capabilities of [Teams Interoperability support with Azure Communication Services Call Automation](../../concepts/call-automation/call-automation-teams-interop.md)
 - Learn about [Play action](../../concepts/call-automation/play-Action.md) to play audio in a call.
 - Learn how to build a [call workflow](../../quickstarts/call-automation/callflows-for-customer-interactions.md) for a customer support scenario. 
