Skip to content

Commit cbe2e7c

Browse files
Merge pull request #207030 from tomaschladek/cte-10
Cte 10
2 parents b9b75c7 + b31041e commit cbe2e7c

File tree

11 files changed

+271
-103
lines changed

11 files changed

+271
-103
lines changed

articles/communication-services/concepts/interop/guest/capabilities.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
2-
title: Capabilities for Teams guests
2+
title: Capabilities for Teams external user
33
titleSuffix: An Azure Communication Services concept document
4-
description: Calling capabilities of Azure Communication Services support for Teams guests
4+
description: Calling capabilities of Azure Communication Services support for Teams external users
55
author: tomaschladek
66
ms.author: tchladek
77
ms.date: 7/9/2022
@@ -10,9 +10,9 @@ ms.service: azure-communication-services
1010
ms.subservice: teams-interop
1111
---
1212

13-
# Capabilities for Teams guests
13+
# Capabilities for Teams external users
1414

15-
In this article, you will learn which capabilities are supported for Teams guests using Azure Communication Services SDKs.
15+
In this article, you will learn which capabilities are supported for Teams external users using Azure Communication Services SDKs.
1616

1717
## Client capabilities
1818
The following table shows supported client-side capabilities available in Azure Communication Services SDKs:
@@ -43,7 +43,7 @@ The following table shows supported client-side capabilities available in Azure
4343
| Apply background effects ||
4444
| See together mode video stream ||
4545

46-
When Teams guest leaves the meeting, or the meeting ends, they can no longer send or receive new chat messages and no longer have access to messages sent and received during the meeting.
46+
When Teams external users leave the meeting, or the meeting ends, they can no longer send or receive new chat messages and no longer have access to messages sent and received during the meeting.
4747

4848
## Server capabilities
4949

@@ -70,9 +70,9 @@ The following table shows supported Teams capabilities:
7070

7171
## Next steps
7272

73-
- [Authenticate as Teams guest](../../../quickstarts/access-tokens.md)
74-
- [Join Teams meeting audio and video as Teams guest](../../../quickstarts/voice-video-calling/get-started-teams-interop.md)
75-
- [Join Teams meeting chat as Teams guest](../../../quickstarts/chat/meeting-interop.md)
73+
- [Authenticate as Teams external user](../../../quickstarts/access-tokens.md)
74+
- [Join Teams meeting audio and video as Teams external user](../../../quickstarts/voice-video-calling/get-started-teams-interop.md)
75+
- [Join Teams meeting chat as Teams external user](../../../quickstarts/chat/meeting-interop.md)
7676
- [Join meeting options](../../../how-tos/calling-sdk/teams-interoperability.md)
7777
- [Communicate as Teams user](../../teams-endpoint.md).
7878

articles/communication-services/concepts/interop/guest/limitations.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Known issues and limitations
33
titleSuffix: An Azure Communication Services concept document
4-
description: Known issues and limitations of Azure Communication Services support for Teams guests
4+
description: Known issues and limitations of Azure Communication Services support for Teams external users
55
author: tomaschladek
66
ms.author: tchladek
77
ms.date: 7/9/2022
@@ -19,8 +19,8 @@ ms.subservice: teams-interop
1919

2020
## Next steps
2121

22-
- [Authenticate as Teams guest](../../../quickstarts/access-tokens.md)
23-
- [Join Teams meeting audio and video as Teams guest](../../../quickstarts/voice-video-calling/get-started-teams-interop.md)
24-
- [Join Teams meeting chat as Teams guest](../../../quickstarts/chat/meeting-interop.md)
22+
- [Authenticate as Teams external user](../../../quickstarts/access-tokens.md)
23+
- [Join Teams meeting audio and video as Teams external user](../../../quickstarts/voice-video-calling/get-started-teams-interop.md)
24+
- [Join Teams meeting chat as Teams external user](../../../quickstarts/chat/meeting-interop.md)
2525
- [Join meeting options](../../../how-tos/calling-sdk/teams-interoperability.md)
2626
- [Communicate as Teams user](../../teams-endpoint.md).
Lines changed: 20 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
2-
title: Communication as Teams guest
2+
title: Communication as Teams external user
33
titleSuffix: An Azure Communication Services concept document
4-
description: Introduction to Azure Communication Services support for Teams guests
4+
description: Introduction to Azure Communication Services support for Teams external users
55
author: tomaschladek
66
ms.author: tchladek
77
ms.date: 7/9/2022
@@ -10,9 +10,9 @@ ms.service: azure-communication-services
1010
ms.subservice: teams-interop
1111
---
1212

13-
# Communication as Teams guest
13+
# Communication as Teams external user
1414

15-
You can use Azure Communication Services to build applications that enable external users to join and participate in Teams meetings as Teams anonymous users (Guests). Customers can join Teams meetings from within your applications or websites. The main benefits are:
15+
You can use Azure Communication Services to build applications that enable external users to join and participate in Teams meetings as Teams anonymous users. Customers can join Teams meetings from within your applications or websites. The main benefits are:
1616
- No requirement to download Teams desktop, mobile or web clients for external users
1717
- External users don't lose context by switching to another application
1818
- Browser support on mobile devices
@@ -31,30 +31,32 @@ Developers can experiment with the capabilities on multiple levels to evaluate,
3131

3232
### Low code or no-code
3333

34-
You can create an identity and access token for Teams guests on Azure portal without a single line of code. [Here are steps how to do it](../../../quickstarts/identity/quick-create-identity.md).
34+
You can create an identity and access token for Teams external users on Azure portal without a single line of code. [Here are steps how to do it](../../../quickstarts/identity/quick-create-identity.md).
3535

3636
With a valid identity, access token, and Teams meeting URL, you can use [Azure Communication Services UI Library](https://azure.github.io/communication-ui-library/?path=/story/composites-call-with-chat-jointeamsmeeting--join-teams-meeting) to join Teams meeting without any code.
3737

3838
### Single-click deployment
3939

40-
The [Azure Communication Services Calling Hero Sample](../../../samples/calling-hero-sample.md) demonstrates how developers can use Azure Communication Services Calling Web SDK to join a Teams meeting from a web application as a Teams guest. You can experiment with the capability with single-click deployment to Azure.
40+
The [Azure Communication Services Calling Hero Sample](../../../samples/calling-hero-sample.md) demonstrates how developers can use Azure Communication Services Calling Web SDK to join a Teams meeting from a web application as a Teams external user. You can experiment with the capability with single-click deployment to Azure.
41+
42+
The [Azure Communication Services Authentication Hero Sample](../../../samples/trusted-auth-sample.md) demonstrates how developers can use Azure Communication Services Identity SDK to get access tokens as Teams users. You can clone the GitHub repository and follow a simple guide to set up your service for authentication in Azure.
4143

4244
### Coding
4345

44-
The data flow for joining Teams meetings is available at the [client and server architecture page](../../client-and-server-architecture.md). When implementing the experience, you must implement client logic for real-time communication and server logic for authentication. The following articles will guide you in implementing the communication for Teams guests.
46+
The data flow for joining Teams meetings is available at the [client and server architecture page](../../client-and-server-architecture.md). When implementing the experience, you must implement client logic for real-time communication and server logic for authentication. The following articles will guide you in implementing the communication for Teams external users.
4547

4648
High-level coding articles:
47-
1. [Authenticate as Teams guest](../../../quickstarts/access-tokens.md)
48-
1. [Stateful Client (Meeting)](https://azure.github.io/communication-ui-library/?path=/story/composites-meeting-basicexample--basic-example)
49+
- [Authenticate as Teams external user](../../../quickstarts/identity/access-token-teams-external-users.md)
50+
- [Stateful Client (Meeting)](https://azure.github.io/communication-ui-library/?path=/story/composites-meeting-basicexample--basic-example)
4951

5052
Low-level coding articles:
51-
1. [Join Teams meeting audio and video as Teams guest](../../../quickstarts/voice-video-calling/get-started-teams-interop.md)
52-
1. [Join Teams meeting chat as Teams guest](../../../quickstarts/chat/meeting-interop.md)
53-
1. [Join meeting options](../../../how-tos/calling-sdk/teams-interoperability.md)
53+
- [Join Teams meeting audio and video as Teams external user](../../../quickstarts/voice-video-calling/get-started-teams-interop.md)
54+
- [Join Teams meeting chat as Teams external user](../../../quickstarts/chat/meeting-interop.md)
55+
- [Join meeting options](../../../how-tos/calling-sdk/teams-interoperability.md)
5456

5557
## Supported use cases
5658

57-
The following table show supported use cases for Teams guest with Azure Communication Services:
59+
The following table show supported use cases for Teams external user with Azure Communication Services:
5860

5961
| Scenario | Supported |
6062
| --- | --- |
@@ -66,8 +68,8 @@ The following table show supported use cases for Teams guest with Azure Communic
6668
| Join Teams 1:1 or group call ||
6769
| Join Teams 1:1 or group chat ||
6870

69-
- [1] Teams guests can join a channel Teams meeting with audio and video, but they won't be able to send or receive any chat messages
70-
- [2] Teams guest users may join a Teams webinar. However, the presenter and attendee roles aren't honored for Teams guests. Thus Teams guests on Azure Communication Services SDKs could perform actions not intended for attendees, such as screen sharing, turning their camera on/off, or unmuting themselves, if your application provides UX for those actions.
71+
- [1] Teams external users can join a channel Teams meeting with audio and video, but they won't be able to send or receive any chat messages
72+
- [2] Teams external users may join a Teams webinar. However, the presenter and attendee roles aren't honored for Teams external users. Thus Teams external users on Azure Communication Services SDKs could perform actions not intended for attendees, such as screen sharing, turning their camera on/off, or unmuting themselves, if your application provides UX for those actions.
7173

7274
## Pricing
7375
Any licensed Teams users can schedule Teams meetings and share the invite with external users. External users can join the Teams meeting experience via existing Teams desktop, mobile, and web clients without additional charge. External users joining via Azure Communication Services SDKs will pay
@@ -76,8 +78,8 @@ Any licensed Teams users can schedule Teams meetings and share the invite with e
7678

7779
## Next steps
7880

79-
- [Authenticate as Teams guest](../../../quickstarts/access-tokens.md)
80-
- [Join Teams meeting audio and video as Teams guest](../../../quickstarts/voice-video-calling/get-started-teams-interop.md)
81-
- [Join Teams meeting chat as Teams guest](../../../quickstarts/chat/meeting-interop.md)
81+
- [Authenticate as Teams external user](../../../quickstarts/identity/access-token-teams-external-users.md)
82+
- [Join Teams meeting audio and video as Teams external user](../../../quickstarts/voice-video-calling/get-started-teams-interop.md)
83+
- [Join Teams meeting chat as Teams external user](../../../quickstarts/chat/meeting-interop.md)
8284
- [Join meeting options](../../../how-tos/calling-sdk/teams-interoperability.md)
8385
- [Communicate as Teams user](../../teams-endpoint.md).

articles/communication-services/concepts/interop/guest/privacy.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
2-
title: User privacy for Teams guests
2+
title: User privacy for Teams external users
33
titleSuffix: An Azure Communication Services concept document
4-
description: User privacy requirements in Azure Communication Services support for Teams guests
4+
description: User privacy requirements in Azure Communication Services support for Teams external users
55
author: tomaschladek
66
ms.author: tchladek
77
ms.date: 7/9/2022
@@ -17,14 +17,14 @@ Microsoft will indicate to you via the Azure Communication Services API that rec
1717

1818
## Chat storage
1919

20-
All chat messages sent by Teams users or Communication Services users during a Teams meeting are stored in the geographic region associated with the Microsoft 365 organization hosting the meeting. For more information, review the article [Location of data in Microsoft Teams](/microsoftteams/location-of-data-in-teams). For each Teams guest joining via Azure Communication Services SDKs in the meetings, there is a copy of the most recently sent message stored in the geographic region associated with the Communication Services resource used to develop the Communication Services application. Review the article [Region availability and data residency](./privacy.md).
20+
All chat messages sent by Teams users or Communication Services users during a Teams meeting are stored in the geographic region associated with the Microsoft 365 organization hosting the meeting. For more information, review the article [Location of data in Microsoft Teams](/microsoftteams/location-of-data-in-teams). For each Teams external user joining via Azure Communication Services SDKs in the meetings, there is a copy of the most recently sent message stored in the geographic region associated with the Communication Services resource used to develop the Communication Services application. Review the article [Region availability and data residency](./privacy.md).
2121

2222
Azure Communication Services will delete all copies of the most recently sent message per Teams retention policies. If no retention policy is defined, Azure Communication Services deletes data after 30 days. For more information about Teams retention policies, review the article [Learn about retention for Microsoft Teams](/microsoft-365/compliance/retention-policies-teams).
2323

2424
## Next steps
2525

26-
- [Authenticate as Teams guest](../../../quickstarts/access-tokens.md)
27-
- [Join Teams meeting audio and video as Teams guest](../../../quickstarts/voice-video-calling/get-started-teams-interop.md)
28-
- [Join Teams meeting chat as Teams guest](../../../quickstarts/chat/meeting-interop.md)
26+
- [Authenticate as Teams external user](../../../quickstarts/access-tokens.md)
27+
- [Join Teams meeting audio and video as Teams external user](../../../quickstarts/voice-video-calling/get-started-teams-interop.md)
28+
- [Join Teams meeting chat as Teams external user](../../../quickstarts/chat/meeting-interop.md)
2929
- [Join meeting options](../../../how-tos/calling-sdk/teams-interoperability.md)
3030
- [Communicate as Teams user](../../teams-endpoint.md).
Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
2-
title: Teams controls for Teams guest
2+
title: Teams controls for Teams external user
33
titleSuffix: An Azure Communication Services concept document
4-
description: Teams administrator controls to impact Azure Communication Services support for Teams guests
4+
description: Teams administrator controls to impact Azure Communication Services support for Teams external users
55
author: tomaschladek
66
ms.author: tchladek
77
ms.date: 7/9/2022
@@ -11,23 +11,23 @@ ms.subservice: teams-interop
1111
---
1212

1313
# Teams administrator controls
14-
Teams administrators have the following policies to control the experience for Teams guests in Teams meetings.
14+
Teams administrators have the following policies to control the experience for Teams external users in Teams meetings.
1515

1616
|Setting name|Policy scope|Description| Supported |
1717
| ---- | ----| ----| --- |
18-
| [Anonymous users can join a meeting](/microsoftteams/meeting-settings-in-teams#allow-anonymous-users-to-join-meetings) | organization-wide | If disabled, Teams guests can't join Teams meeting | ✔️ |
19-
| [Let anonymous people join a meeting](/microsoftteams/meeting-settings-in-teams#allow-anonymous-users-to-join-meetings) | per-organizer | If disabled, Teams guests can't join Teams meeting | ✔️ |
20-
| [Let anonymous people start a meeting](/microsoftteams/meeting-settings-in-teams#allow-anonymous-users-to-join-meetings)| per-organizer | If enabled, Teams guests can start a Teams meeting without Teams user | ✔️ |
21-
| [Automatically admit people](/microsoftteams/meeting-policies-participants-and-guests#automatically-admit-people) | per-organizer | If set to "Everyone", Teams guests can bypass lobby. Otherwise, Teams guests have to wait in the lobby until an authenticated user admits them.| ✔️ |
18+
| [Anonymous users can join a meeting](/microsoftteams/meeting-settings-in-teams#allow-anonymous-users-to-join-meetings) | organization-wide | If disabled, Teams external users can't join Teams meeting | ✔️ |
19+
| [Let anonymous people join a meeting](/microsoftteams/meeting-settings-in-teams#allow-anonymous-users-to-join-meetings) | per-organizer | If disabled, Teams external users can't join Teams meeting | ✔️ |
20+
| [Let anonymous people start a meeting](/microsoftteams/meeting-settings-in-teams#allow-anonymous-users-to-join-meetings)| per-organizer | If enabled, Teams external users can start a Teams meeting without Teams user | ✔️ |
21+
| [Automatically admit people](/microsoftteams/meeting-policies-participants-and-guests#automatically-admit-people) | per-organizer | If set to "Everyone", Teams external users can bypass lobby. Otherwise, Teams external users have to wait in the lobby until an authenticated user admits them.| ✔️ |
2222
| [Who can present in meetings](/microsoftteams/meeting-policies-in-teams-general#designated-presenter-role-mode) | per-user | Controls who in the Teams meeting can share screen ||
23-
| [Blocked anonymous join client types](/powershell/module/skype/set-csteamsmeetingpolicy) | per-organizer | If property "BlockedAnonymousJoinClientTypes" is set to "Teams" or "Null", the Teams guests via Azure Communication Services can join Teams meeting | ✔️ |
23+
| [Blocked anonymous join client types](/powershell/module/skype/set-csteamsmeetingpolicy) | per-organizer | If property "BlockedAnonymousJoinClientTypes" is set to "Teams" or "Null", the Teams external users via Azure Communication Services can join Teams meeting | ✔️ |
2424

2525
Your custom application should consider user authentication and other security measures to protect Teams meetings. Be mindful of the security implications of enabling anonymous users to join meetings. Use the [Teams security guide](/microsoftteams/teams-security-guide#addressing-threats-to-teams-meetings) to configure capabilities available to anonymous users.
2626

2727
## Next steps
2828

29-
- [Authenticate as Teams guest](../../../quickstarts/access-tokens.md)
30-
- [Join Teams meeting audio and video as Teams guest](../../../quickstarts/voice-video-calling/get-started-teams-interop.md)
31-
- [Join Teams meeting chat as Teams guest](../../../quickstarts/chat/meeting-interop.md)
29+
- [Authenticate as Teams external user](../../../quickstarts/access-tokens.md)
30+
- [Join Teams meeting audio and video as Teams external user](../../../quickstarts/voice-video-calling/get-started-teams-interop.md)
31+
- [Join Teams meeting chat as Teams external user](../../../quickstarts/chat/meeting-interop.md)
3232
- [Join meeting options](../../../how-tos/calling-sdk/teams-interoperability.md)
3333
- [Communicate as Teams user](../../teams-endpoint.md).

0 commit comments

Comments
 (0)