Skip to content

Commit 1aebacc

Browse files
Merge pull request #280449 from jpeng-ms/patch-13
[ACS][Chat] Updated doc
2 parents b3016da + 0a0dabd commit 1aebacc

File tree

1 file changed

+10
-6
lines changed

1 file changed

+10
-6
lines changed

articles/communication-services/tutorials/file-sharing-tutorial-interop-chat.md

Lines changed: 10 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -13,9 +13,7 @@ ms.subservice: chat
1313

1414
# Enable file sharing using UI Library in Teams Interoperability Chat
1515

16-
[!INCLUDE [Public Preview Notice](../includes/public-preview-include.md)]
17-
18-
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](./file-sharing-tutorial-acs-chat.md). 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](../concepts/ui-library/ui-library-use-cases.md) to learn more.
16+
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](./file-sharing-tutorial-acs-chat.md). Currently, the Azure Communication Services end user is only able to receive file attachments from the Teams user. Refer to [UI Library Use Cases](../concepts/ui-library/ui-library-use-cases.md) to learn more.
1917

2018
>[!IMPORTANT]
2119
>
@@ -33,7 +31,7 @@ Access the code for this tutorial on [GitHub](https://github.com/Azure-Samples/c
3331
- [Visual Studio Code](https://code.visualstudio.com/) on one of the [supported platforms](https://code.visualstudio.com/docs/supporting/requirements#_platforms).
3432
- [Node.js](https://nodejs.org/), Active LTS and Maintenance LTS versions. Use the `node --version` command to check your version.
3533
- An active Communication Services resource and connection string. [Create a Communication Services resource](../quickstarts/create-communication-resource.md).
36-
- Using the UI library version [1.7.0-beta.1](https://www.npmjs.com/package/@azure/communication-react/v/1.7.0-beta.1) or the latest.
34+
- Using the UI library version [1.17.0](https://www.npmjs.com/package/@azure/communication-react/v/1.17.0) or the latest.
3735
- Have a Teams meeting created and the meeting link ready.
3836
- Be familiar with how [ChatWithChat Composite](https://azure.github.io/communication-ui-library/?path=/docs/composites-call-with-chat-basicexample--basic-example) works.
3937

@@ -58,7 +56,7 @@ export type CallWithChatExampleProps = {
5856
token: string;
5957
displayName: string;
6058
endpointUrl: string;
61-
locator: TeamsMeetingLinkLocator | CallAndChatLocator;
59+
locator: TeamsMeetingLinkLocator | TeamsMeetingIdLocator | CallAndChatLocator;
6260

6361
// Props to customize the CallWithChatComposite experience
6462
fluentTheme?: PartialTheme | Theme;
@@ -68,12 +66,18 @@ export type CallWithChatExampleProps = {
6866

6967
```
7068

71-
To be able to start the Composite for meeting chat, we need to pass `TeamsMeetingLinkLocator`, which looks like this:
69+
To be able to start the Composite for meeting chat, we need to pass `TeamsMeetingLinkLocator` or `TeamsMeetingIdLocator`, which looks like this:
7270

7371
```js
7472
{ "meetingLink": "<TEAMS_MEETING_LINK>" }
7573
```
7674

75+
Or
76+
77+
```js
78+
{ "meetingId": "<TEAMS_MEETING_ID>", "passcode": "<TEAMS_MEETING_PASSCODE>"}
79+
```
80+
7781
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!
7882

7983
## Permissions

0 commit comments

Comments
 (0)