Merge pull request #235308 from jpeng-ms/main

[Communication][Chat][UI Library] Added inline image references

Author: prmerger-automator[bot]

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

@@ -43,6 +43,10 @@ Get more conceptual documentation, quickstarts, and examples in the [UI Library
 | ------------ | ------------------------------------------------ |
 | 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*              |
 | Chat actions | Send a chat message                                |
 |              | Receive a chat message                             |
 | Chat events  | Show typing indicators                                |
@@ -51,6 +55,17 @@ Get more conceptual documentation, quickstarts, and examples in the [UI Library
 |              | Show changes to the chat title                               |
 | Participants | Show a participant roster                               |
 
+*Microsoft Teams allows users to share images by:
+- Copying & paste into the box at the bottom of the chat - inline images.
+- Drag & drop into the chat area.
+- Upload an image as a file via the "Upload from this device" button.
+
+Azure Communication Services currently support only option one for copying and pasting the image. Users can achieve it using keyboard shortcuts or the operating system's context menu options for copy and paste. To learn more about this, please refer to 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 encodings may not be supported by the UI library at this time, the user might receive a static image instead and this is a known issue. 
+
+*Inline image support is 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/)
+
 ## 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).