Merge pull request #178209 from ashwinder/patch-7

Refining supported features for chat

Author: denrea

articles/communication-services/concepts/interop/calling-chat.md

@@ -28,10 +28,10 @@ To enable calling and chat between your Communication Services users and your Te
 
 Custom applications built with Azure Communication Services to connect and communicate with Teams users can be used by end users or by bots, and there's no differentiation in how they appear to Teams users, unless explicitly indicated by the developer of the application.
 
-To start a call or chat with a Teams user, the user’s Azure Active Directory (AAD) object ID is required. This can be obtained using [Microsoft Graph API](/graph/api/resources/users) or from your on-premises directory if you are using [Azure AD Connect](../../../active-directory/hybrid/how-to-connect-sync-whatis.md) (or some other mechanism) to synchronize between your on-premises directory and AAD.
+To start a call or chat with a Teams user, the user’s Azure Active Directory (Azure AD) object ID is required. This can be obtained using [Microsoft Graph API](/graph/api/resources/users) or from your on-premises directory if you are using [Azure AD Connect](../../../active-directory/hybrid/how-to-connect-sync-whatis.md) (or some other mechanism) to synchronize between your on-premises directory and Azure AD.
 
 ## Calling
-With the Calling SDK, a Communication Services user or endpoint can start a 1:1 call with Teams users, identified by their Azure Active Directory (AAD) object ID. You can easily modify an existing application that calls other Communication Services users to instead call a Teams user.
+With the Calling SDK, a Communication Services user or endpoint can start a 1:1 call with Teams users, identified by their Azure Active Directory (Azure AD) object ID. You can easily modify an existing application that calls other Communication Services users to instead call a Teams user.
 
 [Manage calls - An Azure Communication Services how-to guide | Microsoft Docs](../../how-tos/calling-sdk/manage-calls.md?pivots=platform-web)
 
@@ -54,12 +54,10 @@ const call = callAgent.startCall([teamsCallee]);
 - Advanced call routing capabilities such as call forwarding, group call pickup, simulring, and voice mail are not supported.
 - Teams users can't set Communication Services users as forwarding/transfer targets.
 - There are a number of features in the Teams client that do not work as expected during 1:1 calls with Communication Services users.
-- Third party [devices for Teams](/MicrosoftTeams/devices/teams-ip-phones) and [Skype IP phones](/skypeforbusiness/certification/devices-ip-phones) are not supported.
+- Third-party [devices for Teams](/MicrosoftTeams/devices/teams-ip-phones) and [Skype IP phones](/skypeforbusiness/certification/devices-ip-phones) are not supported.
 
 ## Chat
-With the Chat SDK, Communication Services users or endpoints can start 1:n chat with Teams users, identified by their Azure Active Directory (AAD) object ID. You can easily modify an existing application that creates chats with other Communication Services users, to instead create chats with Teams users:
-                                            
-[Quickstart: Add Chat to your App](../../quickstarts/chat/get-started.md?pivots=programming-language-javascript)
+With the Chat SDK, Communication Services users or endpoints can have group chats with Teams users, identified by their Azure Active Directory (AAD) object ID. You can easily modify an existing application that creates chats with other Communication Services users, to instead create chats with Teams users. Below is an example on how to use the Chat SDK to add Teams users as participants. To learn how to use Chat SDK to send a message, manage participants and more, see our [quickstart](../../quickstarts/chat/get-started.md?pivots=programming-language-javascript).
 
 Creating a chat with a Teams user:
 ```js
@@ -75,26 +73,16 @@ createChatThreadRequest, createChatThreadOptions );
 const threadId = createChatThreadResult.chatThread.id; return threadId; }
 ```                                         
 
-**Supported functionality**
--	Send/receive messages (type: text, rich text, emoticons) 
--	Communication Services user can edit sent messages
--	Delete sent messages
--	Receive real-time notifications (thread and message related events supported by ACS currently)
--	Send & receive Typing indicators
--	Send & receive Read receipts
--	Add participant and share message history: Teams user can add Teams users only. Communication Services user can add Teams and Communication Services users.
--	Remove existing participant from chat
--	Leave chat
--	Update chat topic
--	Communication Services user can delete the chat.
-
-
-**Limitations and known issues**
-- Editing of messages by the Teams user fails.
-- Deletion of a thread by the Communication Services user removes the message history for the Teams user and removes the Teams user from the thread.
-- The Teams client UI for external users is inconsistent.
-- Using the Teams client, a call cannot be initiated with the chat participants
+To make it easier to test, we have published a sample app [here](https://github.com/Azure-Samples/communication-services-web-chat-hero/tree/teams-interop-chat-adhoc). Update the app with your Communication Services resource and interop enabled Teams tenant to get started. 
 
+**Limitations and known issues** </br>
+While in private preview, a Communication Services user can do various actions using the Communication Services Chat SDK, including sending and receiving of plain and rich text messages, typing indicators, read receipts, real-time notifications and more. However, most of the Teams chat features aren't supported. Here are some key behaviors and known issues:
+-	Chats can only be initiated by Communication Services users. 
+-	Communication Services users can't send or receive gifs, images, or files. Links to files and images can be shared.
+-	Communication Services users can delete the chat. This removes the Teams user from the chat thread and hides the message history from the Teams client.
+- Known issue: Communication Services users aren't displayed correctly in the participant list. They are currently displayed as External but their people card might be inconsistent. 
+- Known issue: A chat can't be escalated to a call from within the Teams app. 
+- Known issue: Editing of messages by the Teams user is not supported. 
 
 ## Privacy
 Interoperability between Azure Communication Services and Microsoft Teams enables your applications and users to participate in Teams calls, meetings, and chat. It is your responsibility to ensure that the users of your application are notified when recording or transcription are enabled in a Teams call or meeting.