Merge pull request #251892 from jpeng-ms/patch-5

[ACS][Chat] Refactor File Sharing and Inline Image Documentations for UI Library

Author: denrea

.openpublishing.redirection.json

@@ -1,5 +1,10 @@
 {
     "redirections": [
+	{
+            "source_path": "articles/communication-services/tutorials/file-sharing-tutorial.md",
+            "redirect_URL": "/azure/communication-services/tutorials/file-sharing-tutorial-acs-chat",
+            "redirect_document_id": false
+        },
         {
           "source_path": "articles/azure-resource-manager/bicep/bicep-import-providers.md",
           "redirect_URL": "bicep-import",

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

@@ -154,12 +154,15 @@ To make testing easier, we've published a sample app [here](https://github.com/A
 **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 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:
 - Communication Services users can only initiate chats. 
--    Communication Services users can't send or receive GIFs, images, or files. Links to files and images can be shared.
+-    Communication Services users can't send images, or files to the Teams user. But they can receive images and files from the Teams user. Links to files and images can also be shared.
 -    Communication Services users can delete the chat. This action 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're currently displayed as External, but their people cards show inconsistent data. 
+- Known issue: Communication Services users aren't displayed correctly in the participant list. They're currently displayed as External, but their people cards show inconsistent data. In addition, their displayname might not be shown properly in the Teams client.
+- Known issue: The typing event from Teams side might contain a blank display name.
 - 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 isn't supported. 
 
+Please refer to [Chat Capabilities](../interop/guest/capabilities.md) to learn more. 
+
 ## Privacy
 Interoperability between Azure Communication Services and Microsoft Teams enables your applications and users to participate in Teams calls, meetings, and chats. 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.
 

articles/communication-services/concepts/ui-library/includes/web-ui-use-cases.md

@@ -39,35 +39,24 @@ Get more conceptual documentation, quickstarts, and examples in the [UI Library
 
 ## Chat use cases
 
-| Area         | Use cases                                        |
-| ------------ | ------------------------------------------------ |
-| Chat types   | Join a Microsoft Teams meeting chat                        |
-|              | Join an Azure Communication Services chat thread |
-| Teams interoperability  | Send and receive chat messages                                               |
-|  | Send typing indicators                                            |
-|                     | Receive rich text messages              |
-|                     | Receive inline images*              |
-|                     | Receive file attachments*              |
-| Chat actions | Send a chat message                                |
-|              | Receive a chat message                             |
-| Chat events  | Show typing indicators                                |
-|              | Show a read receipt                                     |
-|              | Show when a participant is added or removed                        |
-|              | Show changes to the chat title                               |
-| Participants | Show a participant roster                               |
-
-\*Microsoft Teams allows users to share attached image files that are stored behind authenticated servers, which may require additional configuration when using the UI Library. To learn more about this, see the storybook page for [Teams Inline Image](https://azure.github.io/communication-ui-library/?path=/docs/examples-teamsinterop-inlineimage--inline-image#inline-images).
-
-\*Certain GIF images might not be supported by the UI library at this time. The user might receive a static image instead, and this is a known issue. In addition, the Web UI library doesn't support videos at this time.
-
-The Web UI library currently supports the following file permissions:
-  - "Anyone", and
-  - "People you choose" (with email address)
-  
-The Teams user (sender) should be made aware that all other permissions (such as "People in your organization") aren't supported. The Teams user should double-check if the default permission is supported after uploading the file in their Teams client. In addition, The Teams admin could impose policies that limit or disable this feature entirely (such as having file sharing disabled or having certain permissions disabled).
+
+| Area         | Azure Communication Services Chat                | Teams Interoperability Chat                 |
+| ------------ | ------------------------------------------------ | ------------------------------------------- |
+| Chat types   | Join an Azure Communication Services chat thread | Join a Microsoft Teams meeting chat         |
+| Chat actions | Send and receive text messages                      | Send and receive text messages                 |
+|              | Receive rich text messages                          | Receive rich text messages                     |
+|              | -                                                | [Receive inline images\*](../../../tutorials/inline-image-tutorial-interop-chat.md)                        |
+|              | [Send and receive file attachments](../../../tutorials/file-sharing-tutorial-acs-chat.md)                   | [Receive file attachments\*](../../../tutorials/file-sharing-tutorial-interop-chat.md)                 |
+| Chat events  | Send and receive typing indicators                  | Send and receive typing indicators\*\*             |
+|              | Send and receive read receipts                      | Send and receive read receipts                 |
+|              | Show when a participant is added or removed      | Show when a participant is added or removed |
+| Participants | Show a participant roster                        | Show a participant roster                   |
+
 
 \*Inline image and file attachment support are currently in public preview. Preview APIs and SDKs are provided without a service-level agreement. We recommend that you don't use them for production workloads. Some features might not be supported, or they might have constrained capabilities. For more information, review [Supplemental Terms of Use for Microsoft Azure Previews.](https://azure.microsoft.com/support/legal/preview-supplemental-terms/)
 
+\*\*The display name of typing event from the Teams user might not be shown properly.
+
 ## Supported identities
 
 To initialize a composite, and authenticate to the service, a user must have an Azure Communication Services identity. For more information, see [Authenticate to Azure Communication Services](../../authentication.md) and [Quickstart: Create and manage access tokens](../../../quickstarts/identity/access-tokens.md).
@@ -86,6 +75,8 @@ If you use UI components to deliver Teams interoperability experiences, begin by
 - [Lobby example](https://azure.github.io/communication-ui-library/?path=/story/examples-teams-interop--lobby). A sample lobby where a participant can wait to be admitted to a call.
 - [Compliance banner](https://azure.github.io/communication-ui-library/?path=/story/examples-teams-interop--compliance-banner). A sample banner that shows the user if the call is being recorded.
 - [Teams theme](https://azure.github.io/communication-ui-library/?path=/story/examples-themes--teams). A sample theme that makes UI Library elements look like Microsoft Teams.
+- [Image sharing\*](../../../tutorials/inline-image-tutorial-interop-chat.md). A sample of Azure Communication Service end user can receive images sent by the Teams user.
+- [File sharing\*](../../../tutorials/file-sharing-tutorial-interop-chat.md). A sample of Azure Communication Service end user can receive file attachments sent by the Teams user. 
 
 ## Customization
 

articles/communication-services/toc.yml

@@ -396,8 +396,12 @@ items:
       href: tutorials/trusted-service-tutorial.md
     - name: Add a bot to your chat app
       href: quickstarts/chat/quickstart-botframework-integration.md
-    - name: Add file sharing to your application with UI Library
-      href: tutorials/file-sharing-tutorial.md
+    - name: Add file sharing with UI Library in Azure Communication Service Chat
+      href: tutorials/file-sharing-tutorial-acs-chat.md
+    - name: Add file sharing with UI Library in Teams Interoperability Chat
+      href: tutorials/file-sharing-tutorial-interop-chat.md
+    - name: Add inline image support with UI Library in Teams Interoperability Chat
+      href: tutorials/inline-image-tutorial-interop-chat.md
     - name: Integrate with data loss prevention policies
       href: how-tos/chat-sdk/data-loss-prevention.md
     - name: Connect to Teams