Enable file sharing using UI Library in Teams Interoperability Chat


This feature of Azure Communication Services is currently in 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.

In a Teams Interoperability Chat ("Interop Chat"), we can enable file sharing between Azure Communication Services end users and Teams users. Note, Interop Chat is different from the Azure Communication Services Chat. If you want to enable file sharing in an Azure Communication Services Chat, refer to Add file sharing with UI Library in Azure Communication Services Chat. Currently, the Azure Communication Services end user is only able to receive file attachments from the Teams user. Please refer to UI Library Use Cases to learn more.


File sharing feature comes with the CallWithChat Composite without additional setups.

Download code

Access the code for this tutorial on GitHub.



First of all, we need to understand that Teams Interop Chat has to part of a Teams meeting currently. When the Teams user creates an online meeting, a chat thread would be created and associated with the meeting. To enable the Azure Communication Services end user joining the chat and starting to send/receive messages, a meeting participant (a Teams user) would need to admit them to the call first. Otherwise, they don't have access to the chat.

Once the Azure Communication Services end user is admitted to the call, they would be able to start to chat with other participants on the call. In this tutorial, we're checking out how inline image works in Interop chat.


Similar to how we're Adding Inline Image Support to the UI library, we need a CallWithChat Composite created. Let's follow the basic example from the storybook page to create a ChatWithChat Composite.

From the sample code, it needs CallWithChatExampleProps, which is defined as the following code snippet:

export type CallWithChatExampleProps = {
  // Props needed for the construction of the CallWithChatAdapter
  userId: CommunicationUserIdentifier;
  token: string;
  displayName: string;
  endpointUrl: string;
  locator: TeamsMeetingLinkLocator | CallAndChatLocator;

  // Props to customize the CallWithChatComposite experience
  fluentTheme?: PartialTheme | Theme;
  compositeOptions?: CallWithChatCompositeOptions;
  callInvitationURL?: string;

To be able to start the Composite for meeting chat, we need to pass TeamsMeetingLinkLocator, which looks like this:

{ "meetingLink": "<TEAMS_MEETING_LINK>" }

This is all you need - and there's no other setup needed to enable the Azure Communication Services end user to receive file attachments from the Teams user!


When file is shared from a Teams client, the Teams user has options to set the file permissions to be:

  • "Anyone"
  • "People in your organization"
  • "People currently in this chat"
  • "People with existing access"
  • "People you choose"

Specifically, the UI library currently only supports "Anyone" and "People you choose" (with email address) and all other permissions aren't supported. If Teams user sent a file with unsupported permissions, the Azure Communication Services end user might be prompted to a login page or denied access when they click on the file attachment in the chat thread.

Screenshot of a Teams client listing out file permissions.

Moreover, the Teams user's tenant admin might impose restrictions on file sharing, including disabling some file permissions or disabling file sharing option all together.

Run the code

Let's run npm run start then you should be able to access our sample app via localhost:3000 like the following screenshot:

Screenshot of an Azure Communication Services UI library.

Simply click on the chat button located in the bottom to reveal the chat panel and now if Teams user sends some files, you should see something like the following screenshot:

Screenshot of a Teams client sending one file.

Screenshot of Azure Communication Services UI library receiving one file.

And now if the user click on the file attachment card, a new tab would be opened like the following where the user can download the file:

Screenshot of Sharepoint webpage that shows the file content.

Next steps

You may also want to: