|
| 1 | +--- |
| 2 | +title: Govern Teams meeting experience with Azure Communication Services |
| 3 | +description: Learn how you can design Teams meeting experience for virtual appointments applications. |
| 4 | +author: tchladek |
| 5 | +manager: chpalm |
| 6 | +services: azure-communication-services |
| 7 | + |
| 8 | +ms.author: tchladek |
| 9 | +ms.date: 04/03/2023 |
| 10 | +ms.topic: tutorial |
| 11 | +ms.service: azure-communication-services |
| 12 | +ms.subservice: teams-interop |
| 13 | + |
| 14 | +--- |
| 15 | + |
| 16 | +# Govern meeting experience |
| 17 | +In this article, you learn how to use existing Microsoft 365 tools to control the experience of your virtual visits with Microsoft Teams. You learn the best practices and considerations for individual approaches. Administrators and meeting organizers can control the experience in Teams meetings by the following tools: tenant configuration, tenant policy, assigned role, meeting options, meeting templates, and sensitivity labels. You can learn more about individual tools in [this article](../guest/teams-administration.md). |
| 18 | + |
| 19 | +## Policies, roles & meeting options |
| 20 | +Teams policies, meeting roles, and meeting options are part of standard Microsoft Teams. A meeting organizer and coorganizer can customize the experience via meeting options. Organizations have two options how to prevent hosts of virtual appointments from changing the meeting experience: |
| 21 | +1. Control the experience via policy. |
| 22 | +1. Demote the host to the role presenter. |
| 23 | + |
| 24 | +We recommend using policy to control the experience of the Teams meeting. Here's how to do it: |
| 25 | +Teams administrator creates a new meeting policy that defines desired experience in the Teams meeting and assigns the meeting policy to selected Teams users that conduct virtual appointments. When a Teams user creates a Teams meeting, the assigned policy restricts, hides, or disables features in the Teams meeting for all participants. |
| 26 | + |
| 27 | +|Pros| Cons| |
| 28 | +|--|--| |
| 29 | +| Teams user can't modify the experience defined by administrator | The policy affects all meetings organized by the Teams user |
| 30 | +| If an Azure Communication Services user joins the meeting, Azure Monitor Logs get Call Summary and Call Diagnostics for the organizer. | Host can't lower the requirements if the meeting doesn't require strict requirements. |
| 31 | + |
| 32 | +Another approach is using a dedicated user account in the tenant to schedule Teams meeting for virtual appointments. This user is an organizer that shapes the experience via assigned meeting policy and then customizes the experience via meeting options. Hosts are invited as presenters and, therefore, can't control meeting options. This approach significantly reduces the flexibility of the experience and therefore isn't recommended. |
| 33 | + |
| 34 | +|Pros| Cons| |
| 35 | +|--|--| |
| 36 | +|All Teams users can have assigned relaxed policies, as part of the enforcement is done through meeting options | There's a risk that customers with the role presenter can demote the host to an attendee. |
| 37 | +|Teams user can't modify the experience defined by administrator | If the Azure Communication Services user joins the meeting, Azure Monitor Logs won't get Call Summary and Call Diagnostics for the host unless the Azure Communication Services resource is in the same tenant. |
| 38 | +||[Teams user can create only 2000 meetings a month](/graph/throttling-limits#cloud-communication-service-limits), which limits scalability of the solution. |
| 39 | +||Impacts analytics and reporting. |
| 40 | +||Host can't lower the requirements if the meeting doesn't require strict requirements. |
| 41 | + |
| 42 | +## Meeting templates – Teams premium |
| 43 | +Microsoft Premium provides a new way how to design a meeting experience. Meeting templates allow developers to configure experience just for virtual appointments. On top of meeting templates, it provides more features and controls that can control the experience of the meeting. When a Teams user schedules a virtual appointment, some meeting options can have a preselected default value, some values can be locked, and some entirely hidden. |
| 44 | + |
| 45 | +|Pros| Cons| |
| 46 | +|--|--| |
| 47 | +|Teams user can't modify the experience defined by administrator | Host can't lower the requirements if the meeting doesn't require strict requirements. |
| 48 | +|If an Azure Communication Services user joins the meeting, Azure Monitor Logs get Call Summary and Call Diagnostics for the organizer.| |
| 49 | +|Provides more meeting options to control the experience. | |
| 50 | + |
| 51 | +## Sensitivity label – Microsoft Purview |
| 52 | +Microsoft Purview allows administrators to protect information with sensitivity labels. Teams meeting can have assigned sensitivity labels via template or on the creation of the meeting. If the meeting template permits it, the meeting organizer can change the experience via a sensitivity label during the meeting and, in case of lowering the requirements, can justify this action. This tool provides more flexibility to the meeting host, which also complies with the organization's requirements. |
| 53 | + |
| 54 | +|Pros| Cons| |
| 55 | +|--|--| |
| 56 | +|Teams users can't modify the experience defined by the administrators |
| 57 | +|If an Azure Communication Services user joins the meeting, Azure Monitor Logs get Call Summary and Call Diagnostics for the organizer. |
| 58 | +|Provides more meeting options to control the experience. |
| 59 | +|Host can lower the requirements if the meeting doesn't require strict requirements. |
| 60 | + |
| 61 | +## Next steps |
| 62 | +- [Overview of virtual appointments](./overview.md) |
| 63 | +- [Build your own virtual appointments](../../../tutorials/virtual-visits/sample-builder.md) |
| 64 | +- [Learn about Teams controls](../guest/teams-administration.md). |
| 65 | +- [Plan user experience in Teams meetings](./plan-user-experience.md) |
0 commit comments