diff --git a/Teams/app-powered-tasks-in-planner.md b/Teams/app-powered-tasks-in-planner.md index a08d608bd7..02a7642c95 100644 --- a/Teams/app-powered-tasks-in-planner.md +++ b/Teams/app-powered-tasks-in-planner.md @@ -98,7 +98,7 @@ POST https://graph.microsoft.com/beta/solutions/businessScenarios/{your-business "{reference URL}": { "@odata.type": "microsoft.graph.plannerExternalReference", "alias": "{destination app name}", - "previewPriority": "!", + "previewPriority": " !", "type": "TeamsHostedApp" } } @@ -119,7 +119,7 @@ To define the attachment, specify the following properties in `"references"` in "{reference-URL}": { "@odata.type": "microsoft.graph.plannerExternalReference", "alias": "{destination app name}", - "previewPriority": "!", + "previewPriority": " !", "type": "TeamsHostedApp" } } @@ -213,7 +213,7 @@ POST https://graph.microsoft.com/beta/solutions/businessScenarios/ccd5aa8aebd048 "https://teams%2Emicrosoft%2Ecom/l/stage/com%2Emicrosoft%2Eteamspace%2Etab%2Eyoutube/0?context=%7B%22contentUrl%22%3A%22https%3A%2F%2Ftabs%2Eteams%2Emicrosoft%2Ecom%2FyoutubeContentStage%3FvideoId%3DHBGmSy1iVmY%22%2C%22name%22%3A%22Security%2520talk%22%2C%22openMode%22%3A%22modal%22%7D": { "@odata.type": "microsoft.graph.plannerExternalReference", "alias": "Security practices presentation", - "previewPriority": "!", + "previewPriority": " !", "type": "TeamsHostedApp" } } diff --git a/Teams/configure-lobby-sensitive-meetings.md b/Teams/configure-lobby-sensitive-meetings.md index ea2534ff98..af4d00922b 100644 --- a/Teams/configure-lobby-sensitive-meetings.md +++ b/Teams/configure-lobby-sensitive-meetings.md @@ -6,7 +6,7 @@ manager: pamgreen ms.topic: article ms.service: msteams ms.reviewer: vivek.mohan -ms.date: 12/11/2023 +ms.date: 11/12/2024 audience: admin ms.localizationpriority: medium f1.keywords: @@ -25,11 +25,11 @@ description: Learn how to configure the Teams meeting lobby to enhance security [!INCLUDE[Teams Premium ECM](includes/teams-premium-ecm.md)] -The meeting lobby is a tool that you can use to help ensure that inappropriate people aren't admitted to meetings. By holding different types of participants in the lobby, meeting organizers can vet them and make sure it's appropriate for them to attend the meeting. +The meeting lobby is a tool that you can use to help ensure that inappropriate people aren't admitted to meetings. Holding different types of participants in the lobby allows meeting organizers to make sure it's appropriate for them to attend the meeting. -By default, people in your organization and [guests](guest-access.md) are admitted to meetings directly and participants from [trusted organizations](/microsoftteams/trusted-organizations-external-meetings-chat?tabs=organization-settings#specify-trusted-microsoft-365-organizations) and [anonymous participants](anonymous-users-in-meetings.md) must wait in the lobby to be admitted by a meeting organizer. Meeting organizers can change this default setting for each meeting they create. +By default, people in your organization and [guests](guest-access.md) are admitted to meetings directly. Participants from [trusted organizations](/microsoftteams/trusted-organizations-external-meetings-chat?tabs=organization-settings#specify-trusted-microsoft-365-organizations) and [anonymous participants](anonymous-users-in-meetings.md) must wait in the lobby until a meeting organizer admits them. Meeting organizers can change this default setting for each meeting they create. -The lobby and other related settings can be controlled by the Teams Administrator by using meeting policies, meeting templates, and sensitivity labels to customize the experience for different users and different types of meetings. + Meeting policies in the Teams admin center, meeting templates, and sensitivity labels to customize the lobby experience for different users and different types of meetings. The following table lists features that you can use to help manage the lobby experience for your organization and where to configure them. @@ -49,33 +49,37 @@ For information about how to use templates and sensitivity labels to configure m ## Lobby settings for different types of meetings +### Who can admit from lobby + The following settings are available for **Who can admit from lobby**: -- Organizers and presenters +- Organizers, co-organizers, and presenters - Organizers and co-organizers -To manage who can bring participants from the lobby into the meeting or webinar, you should consider using this per-organizer policy for sensitive meetings. When set to it's default value of **Organizers and presenters**, only organizers and presenters can admit participants into the meeting from the lobby. This policy sets a default that your organizers can change through their **Meeting options**. +To manage who can bring participants from the lobby into the meeting or webinar, you should consider using this per-organizer policy for sensitive meetings. When set to the default value of **Organizers, co-organizers, and presenters**, only organizers, co-organizers, and presenters can admit participants into the meeting from the lobby. This policy sets a default that your organizers can change through their **Meeting options**. + +### Who can bypass the lobby The following settings are available for **Who can bypass the lobby**: - Everyone -- People in my org, trusted orgs, and guests - People in my org and guests +- People in my org, trusted orgs, and guests - People in my org -- People who were invited - Only organizers and co-organizers +- People who were invited -This per-organizer policy controls who can bring participants from the lobby into the meeting or webinar. When set to it's default value of **Organizers and presenters**, only organizers and presenters can admit participants into the meeting from the lobby. This policy sets a default that your organizers can change through their **Meeting options**. +This per-organizer policy controls who can bypass the lobby into the meeting or webinar. When set to the default value of **People in my org and guests**, only people in my org and guests can bypass lobby. This policy sets a default that your organizers can change through their **Meeting options**. -An additional setting, **People dialing in can bypass the lobby**, controls if people calling in by phone can bypass the lobby. +Another setting, **People dialing in can bypass the lobby**, controls if people calling in by phone can bypass the lobby. While the meeting organizer normally chooses which setting to use for each meeting, you can enforce a particular setting using either a meeting template or a sensitivity label. -If your organization requires that certain types of meetings not be attended by people outside the organization, consider a meeting template that only allows people in your organization to bypass the lobby. This ensures that people outside the organization who were accidentally invited or sent a meeting link can't join the meeting directly. +If your organization needs to restrict certain meetings to internal participants only, you could use a meeting template that allows only people in your organization to bypass the lobby. This option ensures that people outside the organization who were accidentally invited or sent a meeting link can't join the meeting directly. -If your organization has meetings where highly sensitive information is shared and you need to be sure that only certain people attend, consider using a meeting template or sensitivity label that only allows meeting organizers to bypass the lobby. This ensures that organizers can vet each incoming participant to make sure they should be in the meeting. This also prevents the meeting from starting until an organizer joins. +For meetings with highly sensitive information, you could use a meeting template or sensitivity label that allows only meeting organizers to bypass the lobby. This option allows organizers to vet participants and ensures the meeting doesn't start until an organizer joins. -For sensitive meetings in general, consider using the **People who were invited** option. This ensures that people who don't have either a direct or forwarded meeting invite go through the lobby. (The meeting organizer can also prevent forwarding when they create the meeting.) +For sensitive meetings in general, consider using the **People who were invited** option. This option ensures that people who don't have either a direct or forwarded meeting invite go through the lobby. (The meeting organizer can also prevent forwarding when they create the meeting.) For more information about the meeting lobby, see [Control who can bypass the meeting lobby in Microsoft Teams](who-can-bypass-meeting-lobby.md). @@ -85,7 +89,7 @@ For information about using meeting templates and sensitivity labels together, s By default, attendees who are dialing in by phone go through the lobby. Administrators can change this default with the **People dialing in can bypass the lobby** admin meeting policy. If you want to enforce this setting to be on or off, you must use a meeting template or sensitivity label. -If there are circumstances where you want to allow callers to bypass the lobby, meeting organizers can control this setting, or you can enforce it through a meeting template or sensitivity label. +If you want to allow callers to bypass the lobby, meeting organizers can control this setting, or you can enforce it through a meeting template or sensitivity label. #### Join and leave notifications @@ -95,7 +99,7 @@ Meeting organizers have the option of having attendees calling in by phone annou Unless you allow everyone to bypass the lobby, anonymous participants must go through the lobby to attend the meeting. Meeting organizers can then decide if these participants should be admitted. -If your organization doesn't allow anonymous participants to join meetings at all, you can turn off the **Anonymous users can join a meeting** policy in the Teams admin center. If you have certain groups in your organization - such as marketing - who need to organize meetings with anonymous participants and others - such as research - who shouldn't, you can use Teams meeting policies to configure anonymous meeting join for different groups. For more information, see [Manage anonymous participant access to Teams meetings, webinars, and town halls](anonymous-users-in-meetings.md). +If your organization doesn't allow anonymous participants in meetings, turn off the **Anonymous users can join a meeting** policy in the Teams admin center. For groups like marketing that need anonymous participants to join meetings, and others like research that don't, use Teams meeting policies to configure anonymous meeting join for different groups. For more information, see [Manage anonymous participant access to Teams meetings, webinars, and town halls](anonymous-users-in-meetings.md). ## Related topics diff --git a/Teams/configure-meetings-baseline-protection.md b/Teams/configure-meetings-baseline-protection.md index 3554e54f0a..bcf473d489 100644 --- a/Teams/configure-meetings-baseline-protection.md +++ b/Teams/configure-meetings-baseline-protection.md @@ -6,7 +6,7 @@ manager: pamgreen ms.topic: article ms.service: msteams ms.reviewer: vivek.mohan -ms.date: 12/11/2023 +ms.date: 11/14/2024 audience: admin ms.localizationpriority: medium f1.keywords: @@ -25,7 +25,7 @@ description: Learn how to configure Teams meetings for a baseline level of prote [!INCLUDE[Teams Premium ECM](includes/teams-premium-ecm.md)] -For the *baseline* level of protection, we restrict who can bypass the lobby by using a sensitivity label and set a default value for who can present with a Teams admin policy. You can restrict additional actions as well if your organization requires it. +For the *baseline* level of protection, we restrict **Who can bypass the lobby** by using a sensitivity label and set a default value for **Who can present** with a Teams admin policy. You can restrict other actions as well if your organization requires it. > [!NOTE] > Meeting options in sensitivity labels and custom meeting templates require Teams Premium. @@ -49,7 +49,7 @@ The following table describes which actions we restrict for baseline meetings an |Who can present|**People in my org and guests**|Teams admin center|No| |Who can record|**Organizers, co-organizers, and presenters**|Template|No| -Options that are listed as enforced are enforced by the sensitivity label or meeting template. Options that aren't enforced can be changed by the meeting organizer. +The sensitivity label or meeting template enforces options that are listed as enforced. The meeting organizer can change Options that aren't enforced. ## Default values for **Who can present** @@ -77,41 +77,19 @@ To configure who can admit from lobby: ## Watermarks and end-to-end encryption -In the *baseline* level of protection, we disable watermarks and end-to-end encryption by using a sensitivity label. This will prevent meeting organizers from using these features. Watermarks and end-to-end encryption are more applicable to sensitive meetings. +In the *baseline* level of protection, we turn off watermarks and end-to-end encryption by using a sensitivity label. This setting prevents meeting organizers from using these features. Watermarks and end-to-end encryption are more applicable to sensitive meetings. -End-to-end encryption and watermarks disable some other features such as PowerPoint Live. Turning them off for the *baseline* level of protection can avert instances where meeting organizers use these features without realizing the limits they impose. +End-to-end encryption and watermarks turn off some other features such as PowerPoint Live. Turning them off for the *baseline* level of protection can avert instances where meeting organizers use these features without realizing the limits they impose. -If you work in a highly regulated industry, you may want to keep these features available even in the *baseline* level of protection. +If you work in a highly regulated industry, you might want to keep these features available even in the *baseline* level of protection. ## Sensitivity labels For the *baseline* level of protection, we use a sensitivity label that you can use directly in a meeting or as part of a meeting template. Depending on the configuration you choose, this label can also be used to classify teams and individual files. -If you already have sensitivity labels deployed in your organization, consider how this label fits with your overall label strategy. You can change the name or settings shown below if needed to meet the needs of your organization. If you already have a label that you use for baseline or general protection, you can edit the label and add Teams meetings to it. +If you already have sensitivity labels deployed in your organization, consider how this label fits with your overall label strategy. You can change the name or settings if needed to meet the needs of your organization. If you already have a label that you use for baseline or general protection, you can edit the label and add Teams meetings to it. -To create a sensitivity label: - -1. Open the [Microsoft Purview compliance portal](https://compliance.microsoft.com). -1. Under **Solutions**, expand **Information protection** and then select **Labels**. -1. Select **Create a label**. -1. Give the label a name. We suggest **Sensitive**, but you can choose a different name if that one is already in use. -1. Add a display name and description, and then select **Next**. -1. On the **Define the scope for this label** page, make sure **Items**, **Files**, **Emails**, and **Meetings** are selected. (Note that you can select other options if you want to use this label for other purposes.) -1. Select **Next**. -1. On the **Choose protection settings for labeled items** page, select **Protect Teams meetings and chats** and then select **Next** -1. On the **Settings for Teams meetings and chats** page, choose the following values: - 1. Select **Control end-to-end encryption for meeting video and audio** and set **Apply end-to-end encryption** to **Don't apply end-to-end encryption**. - 1. Select **Control watermarks** and select **Don't apply watermark to shared content** and **Don't apply watermark to everyone's video feed**. - 1. Configure any other settings that you need for your organization. - - :::image type="content" alt-text="Screenshot of meeting sensitivity label settings showing configuration in this procedure." source="media/teams-meeting-sensitivity-label-baseline-small.png"::: - -1. Select **Next**. -1. Complete the wizard with any additional settings you want to use, select **Create label**, and then select **Done**. - -Once you've created the label, you need to publish it to the users who will use it. For baseline protection, we make the label available to all users. You publish the label in the Microsoft Purview compliance portal, on the **Label policies** page under **Information protection**. If you have an existing policy that applies to all users, add this label to that policy. If you need to create a new policy, see [Publish sensitivity labels by creating a label policy](/purview/create-sensitivity-labels#publish-sensitivity-labels-by-creating-a-label-policy). - -For additional information about using sensitivity labels with meetings, see [Use sensitivity labels to protect calendar items, Teams meetings and chat](/microsoft-365/compliance/sensitivity-labels-meetings). +To learn how to create and manage a sensitivity label, see [Use sensitivity labels to protect calendar items, Teams meetings and chat](/purview/sensitivity-labels-meetings#how-to-configure-a-sensitivity-label-to-protect-calendar-items-teams-meetings-and-chats). ## Meeting templates @@ -119,27 +97,25 @@ In the *baseline* level of protection, we use the template to set a default valu We also prevent people dialing in by phone from bypassing the lobby. You can omit this setting if your organization frequently holds meetings where dial-in participants should be able to join directly. If there are certain types of meetings where this is true, consider using a separate template for those meetings. -If you've chosen to disable watermarks and end-to-end encryption in the sensitivity label, you can also use the template to hide those options from the meeting organizer. +If you turned off watermarks and end-to-end encryption in the sensitivity label, you can also use the template to hide those options from the meeting organizer. To create a custom meeting template 1. In the Teams admin center, expand **Meetings** and select **Meeting templates**. 1. Select **Add** 1. Type a name and description for the template. -1. In the **Apply sensitivity label** section, choose the label you created above. +1. In the **Apply sensitivity label** section, choose the label you created. 1. Select **Apply sensitivity label**, and then select **Lock**. 1. In the **Lobby** dropdown, select **People in my org, trusted orgs, and guests**. 1. Make sure **People dialing in can bypass the lobby** is set to **Off**, then select it and select **Lock**. -1. If you've disabled watermarks and end-to-end encryption with the sensitivity label, consider selecting those options here and selecting **Hide** so meeting organizers won't see them. -1. Change any additional options if desired. +1. If you turned off watermarks and end-to-end encryption with the sensitivity label, consider selecting those options here and selecting **Hide** so meeting organizers doesn't see them. +1. Change any other options if desired. 1. To prevent the meeting organizer from changing an option, select the option and then select **lock**. 1. To prevent the meeting organizer from seeing an option, select the option and then select **Hide**. 1. Select **Save**. ## Related topics -[Configure Teams meetings with three tiers of protection](configure-meetings-three-tiers-protection.md) - -[Overview of custom meeting templates in Microsoft Teams](custom-meeting-templates-overview.md) - -[Use Teams meeting templates, sensitivity labels, and admin policies together for sensitive meetings](meeting-templates-sensitivity-labels-policies.md) +- [Configure Teams meetings with three tiers of protection](configure-meetings-three-tiers-protection.md) +- [Overview of custom meeting templates in Microsoft Teams](custom-meeting-templates-overview.md) +- [Use Teams meeting templates, sensitivity labels, and admin policies together for sensitive meetings](meeting-templates-sensitivity-labels-policies.md) diff --git a/Teams/configure-meetings-highly-sensitive-protection.md b/Teams/configure-meetings-highly-sensitive-protection.md index 71e1d2120b..f9225222e0 100644 --- a/Teams/configure-meetings-highly-sensitive-protection.md +++ b/Teams/configure-meetings-highly-sensitive-protection.md @@ -6,7 +6,7 @@ manager: pamgreen ms.topic: article ms.service: msteams ms.reviewer: vivek.mohan -ms.date: 12/11/2023 +ms.date: 11/14/2024 audience: admin ms.localizationpriority: medium f1.keywords: @@ -25,17 +25,17 @@ description: Learn how to configure Teams meetings for protection for highly sen [!INCLUDE[Teams Premium ECM](includes/teams-premium-ecm.md)] -For the *highly sensitive* level of protection, we'll look at two different scenarios: +For the *highly sensitive* level of protection, let's look at two different scenarios: -- Highly sensitive meetings where attendees participate and interact with the presenters -- Highly sensitive presentations where attendees don't interact and are just viewing the presentation +- Highly sensitive meetings where attendees participate and interact with the presenters. +- Highly sensitive presentations where attendees don't interact and are just viewing the presentation. > [!NOTE] > Meeting options in sensitivity labels and custom meeting templates require Teams Premium. ## Highly sensitive meetings -For highly sensitive meetings, we'll restrict who can bypass the lobby, who can present, when participants can chat, and we'll block copying from the meeting chat. We'll also enable end-to-end encryption and watermarking for shared video and content. +For highly sensitive meetings, we restrict **Who can bypass the lobby,** **Who can present**, when participants can chat, and we'll block copying from the meeting chat. We'll also enable end-to-end encryption and watermarking for shared video and content. The following table describes which actions we'll restrict for highly sensitive meetings and where those options are configured. diff --git a/Teams/configure-meetings-three-tiers-protection.md b/Teams/configure-meetings-three-tiers-protection.md index f3c8fe65b5..a038dd4497 100644 --- a/Teams/configure-meetings-three-tiers-protection.md +++ b/Teams/configure-meetings-three-tiers-protection.md @@ -6,7 +6,7 @@ manager: pamgreen ms.topic: solution-overview ms.service: msteams ms.reviewer: -ms.date: 12/11/2023 +ms.date: 11/14/2024 audience: admin ms.localizationpriority: medium f1.keywords: @@ -26,14 +26,14 @@ description: Learn how to configure Teams meetings for better security using thr [!INCLUDE[Teams Premium ECM](includes/teams-premium-ecm.md)] -The articles in this series provide options for using the compliance features available in Teams and Microsoft 365 to create a meeting environment that meets your compliance requirements. We'll look at the options available with sensitivity labels and templates and how you can use them together with other Teams admin settings. +The articles in this series offer various options for you, as an admin, to utilize the compliance features in Teams and Microsoft 365. These options allow ensure that your organization's meeting environment aligns with your compliance requirements. These articles explore the available options with sensitivity labels and templates, and how you can use them together with other Teams admin settings. -> [!Note] -> Meeting sensitivity labels and custom meeting templates require Teams Premium. +> [!NOTE] +> Meeting sensitivity labels and custom meeting templates require a Teams Premium license. -This article defines four different configurations, starting with a baseline configuration for meetings that don't have specific compliance requirements. Each additional configuration represents a meaningful step up in protection as meeting options become more restricted. The configurations in this article provide examples of how to configure protection for meetings with different levels of sensitivity. Use these examples to understand what's possible and modify the specific settings as needed for your organization. +This article defines four different configurations, starting with a baseline configuration for meetings that don't have specific compliance requirements. Each extra configuration represents up a meaningful step in protection as meeting options become more restricted. The configurations in this article provide examples of how to configure protection for meetings with different levels of sensitivity. Use these examples to understand what's possible and modify the specific settings as needed for your organization. -We'll discuss these three configurations: +There are three configurations: - Baseline protection @@ -41,11 +41,11 @@ We'll discuss these three configurations: - Highly sensitive protection -Additionally, we'll discuss a variation of the highly sensitive configuration that is designed for presentations that have minimal interaction from attendees. +This series also provides a variation of the highly sensitive configuration that is designed for presentations that have minimal interaction from attendees. ## Three tiers at a glance -The following table summarizes the configurations for each tier. Use these configurations as starting point recommendations and adjust the configurations to meet the needs of your organization. Depending on your compliance needs, you may not need every tier. +The following table summarizes the configurations for each tier. Use these configurations as starting point recommendations and adjust the configurations to meet the needs of your organization. Depending on your compliance needs, you might not need every tier. | |Baseline|Sensitive|Highly sensitive|Highly sensitive presentation| |:-----|:-----|:-----|:-----|:-----| @@ -91,28 +91,31 @@ Sensitivity labels and templates can be used together to help you meet your comp ## Meeting chat -Meeting chat can be an important part of collaboration during a meeting. However, you may want to restrict meeting chat in certain types of meetings to avoid sensitive information being shared there. +Meeting chat can be an important part of collaboration during a meeting. However, you might want to restrict meeting chat in certain types of meetings to avoid sensitive information being shared there. As an admin, you can control meeting chat in the following ways: -- **Teams admin meeting policy** (per user or group) can be used to allow chat, allow chat for everyone except anonymous participants, or turn chat off. Can also be used to prevent copying chat content to the clipboard. -- **Sensitivity label meeting option** (per meeting) can enforce chat to be on or off or allowed only during the meeting. Can also be used to prevent copying chat content to the clipboard These options can be left unconfigured to be controlled by a template or the meeting organizer. -- **Meeting template meeting option** (per meeting) can enforce chat to be on or off or allowed only during the meeting. Can also be used to prevent copying chat content to the clipboard. These options can be left unconfigured to be controlled by the meeting organizer. +- **Teams admin meeting policy** (per user or group) can be used to allow chat, allow chat for everyone except anonymous participants, or turn off chat. Can also be used to prevent copying chat content to the clipboard. +- **Sensitivity label meeting option** (per meeting) can enforce chat to be on or off or allowed only during the meeting. Can also be used to prevent copying chat content to the clipboard. These options can be left unconfigured for a meeting organizer or template to control. +- **Meeting template meeting option** (per meeting) can enforce chat to be on or off or allowed only during the meeting. Can also be used to prevent copying chat content to the clipboard. These options can be left unconfigured for a meeting organizer or template to control. For the three tiers of protection, we allow chat for baseline and sensitive meetings and restrict it in highly sensitive meetings to in-meeting only. We also prevent copying chat content to the clipboard in sensitive and highly sensitive meetings. For more information, see [Manage chat for sensitive Teams meetings](manage-chat-sensitive-meetings.md). -## Meeting recordings +## Meeting recordings and transcripts -As an admin, you can control meeting recordings in the following ways: +As an admin, you can control meeting recordings and transcripts in the following ways: - The **Meeting recording** admin meeting policy (per user or group) +- The **Transcription** admin meeting policy (per user or group) - The **Recordings automatically expire** (recording deletion) admin meeting policy (per user or group) - The **Who can record** option in sensitivity labels and meeting templates (per meeting) - The **Record automatically** option in sensitivity labels and meeting templates (per meeting) -If your organization or certain people or groups within it should never be able to record meetings, you can turn off the feature by using the **Meeting recording** admin meeting policy. +If your organization or certain people or groups within it should never be able to record meetings, you can turn off the feature by using the [**Meeting recording**](meeting-recording.md#allow-or-prevent-users-from-recording-meetings) admin meeting policy. + +If your organization or certain people or groups within it should never be able to transcribe meetings, you can turn off the feature by using the [**Transcription**](meeting-transcription-captions.md#transcription) admin meeting policy. If there are certain types of meetings that must always be recorded, you can enforce the **Record automatically** option using either a meeting template or a sensitivity label. @@ -132,15 +135,15 @@ There are three kinds of external participants who can join meetings: Participants from trusted organizations join meetings via the [external access](manage-external-access.md) feature. You can control what domains, if any, your organization wants to trust. (This setting also affects 1:1 and group chat with people in those domains.) -If [Teams guest access](guest-access.md) is enabled for your organization, then guests will be able to join meetings. Guest access settings can also be used to control guests' screen sharing mode, including disabling screen sharing. (Guest access is also used for inviting guests to teams.) +If [Teams guest access](guest-access.md) is enabled for your organization, then guests can join meetings. Guest access settings can also be used to control guests' screen sharing mode, including disabling screen sharing. (Guest access is also used for inviting guests to teams.) -If the [**Anonymous users can join a meeting** Teams admin setting](anonymous-users-in-meetings.md) is turned on, anonymous participants will be able to join meetings. +If the [**Anonymous users can join a meeting** Teams admin setting](anonymous-users-in-meetings.md) is turned on, anonymous participants can able to join meetings. While you can turn anonymous join off completely without affecting features other than meetings, both guest access and trusted organizations are used in scenarios other than meetings. If you want to restrict meeting access for these participants but need to leave the features turned on for other reasons, you must use the lobby to prevent these participants from joining a meeting. ## Lobby options -The meeting lobby allows meeting organizers to vet attendees before allowing them into the meeting. Depending on the type of meeting and your compliance requirements, you may want to allow all attendees to bypass the lobby and join the meeting directly, or hold certain types of attendees in the lobby until they're admitted by a meeting organizer. If you wish to prevent certain types of people - such as guests - from attending meetings, you can have them go through the lobby and then the meeting organizer can deny them admittance. +The meeting lobby allows meeting organizers to vet attendees before allowing them into the meeting. Depending on the meeting type and compliance requirements, you can allow all attendees to bypass the lobby or hold certain attendees in the lobby until the organizer admits them. If you wish to prevent certain types of people - such as guests - from attending meetings, you can have them go through the lobby and then the meeting organizer can deny them admittance. For the baseline tier, we allow everyone except anonymous attendees to bypass the lobby. For sensitive meetings, we allow only people with a meeting invitation to bypass the lobby. For highly sensitive meetings, we require organizers to admit each attendee. @@ -152,9 +155,9 @@ As an admin, you can control the lobby in the following ways: - The **Who can bypass the lobby?** option in sensitivity labels and meeting templates (per meeting) - The **People dialing in can bypass the lobby** admin meeting policy (per user or group) or in sensitivity labels and meeting templates (per meeting) -These options are also available to the meeting organizer unless they've been locked by a sensitivity label or template. +These options are also available to the meeting organizer unless a sensitivity label or template locks them. -If you're in a highly regulated industry and you need to manually admit each attendee to all meetings in your organization, you can configure the lobby by using admin meeting policies in the Teams admin center. If your organization has different types of meetings that have different lobby requirements, then we recommend using meeting templates or sensitivity labels to configure these options. +If you're in a highly regulated industry and need to manually admit attendees to all meetings, you can configure the lobby using admin meeting policies in the Teams admin center. If your organization has different types of meetings that have different lobby requirements, then we recommend using meeting templates or sensitivity labels to configure these options. While the admin policy sets a default, you need a template or label to enforce a lobby option. @@ -164,6 +167,5 @@ For more information, see [Configure the Microsoft Teams meeting lobby for sensi ## Related topics -[Microsoft cloud for enterprise architects illustrations](/microsoft-365/solutions/cloud-architecture-models) - -[Use sensitivity labels to protect calendar items, Teams meetings and chat](/microsoft-365/compliance/sensitivity-labels-meetings) +- [Microsoft cloud for enterprise architects illustrations](/microsoft-365/solutions/cloud-architecture-models) +- [Use sensitivity labels to protect calendar items, Teams meetings and chat](/microsoft-365/compliance/sensitivity-labels-meetings) diff --git a/Teams/create-a-phone-system-call-queue.md b/Teams/create-a-phone-system-call-queue.md index 6a98100956..94761ce433 100644 --- a/Teams/create-a-phone-system-call-queue.md +++ b/Teams/create-a-phone-system-call-queue.md @@ -595,33 +595,33 @@ Set-CsCallQueue -Identity -OverflowAction Forward -NoAgentActio ### Call queue feature compatibility -|Feature |Teams Desktop1 |Teams Web | Teams Mobile App2 |Teams Phone Mobile3 |Skype for Business |IP Phones | Standard Call Queues |Channel Based Call Queues | Comment | -|:--------------------------------|:------------------------:|:--------:|:----------------------------:|:-----------------------------:|:-----------------:|:--------:|:--------------------:|:------------------------:|:-------------| -|**Agent Routing Methods** | | | | | | | | | | -|Attendant Routing |Y |Y |Y |Y |Y |Y |Y |Y |*Default* | -|Longest Idle4 |Y |Y |Y |Y |N |Y |Y |Y |*Recommended* | -|Round Robin |Y |Y |Y |Y |Y |Y |Y |Y |*Recommended* | -|Serial |Y |Y |Y |Y |Y |Y |Y5 |Y5 | | -|**Agent Routing Options** | | | | | | | | | | -|Presence Based Routing4|Y |Y |Y |Y11 |N |Y |Y |Y |*Default* | -|Agents can opt out |Y |Y |Y |Y11 |Y8 |Y8|Y |Y |*Default* | -|**Transfer Modes** | | | | | | | | | | -|Conference Mode6 |Y |Y |Y |Y |Y |Y |Y |Y |*Default* | -|Transfer Mode |Y |Y |Y |Y |Y |Y |Y |Y | | -|**Collaborative Calling** | | | | | | | | | | -|Channel Based Queues |Y |N |N |N |N |N |N/A |Y9 |Agents on non-supported devices can still answer calls however they won't have the collaborative calling user interface | -|**Dynamic caller ID** | | | | | | | | | | -|Standard Call queue |Y |Y |Y |N |N |N |Y |N/A | | -|Channel based Call queue |Y |N/A |N/A |N/A |N/A |N/A |N/A |Y | | -|**PSTN Connectivity Methods** | | | | | | | | |See Note 10 | -|Calling Plans |Y |Y |Y |Y |Y |Y |Y |Y | | -|Direct Routing |Y |Y |Y |Y |N12 |Y |Y7 |Y | | -|Operator Connect |Y |Y |Y |Y |N |Y |Y7 |Y | | -|**Miscellaneous** | | | | | | | | | | -|Call toast shows Resource Account Name |Y |N |Y |N |Y | |Y |Y | | -|Click-to-call | Y |N |N |N |N |N |Y |Y | | -|[Compliance recording](teams-recording-policy.md) |N/A |N/A |N/A |N/A |N/A |N/A |N/A |N/A |Not supported | -|[Location based routing](location-based-routing-plan.md#inbound-calls-through-auto-attendants) |N/A |N/A |N/A |N/A |N/A |N/A |N/A |N/A |Not supported | +| Feature | Teams Desktop1 | Teams Web | Teams Mobile App2 | Teams Phone Mobile3 | Skype for Business | IP Phones | Standard Call Queues | Channel Based Call Queues | Comment | +|:-|:-:|:-:|:-:|:-:|:-:|:-:|:-:|:-:|:-| +| **Agent Routing Methods** | | | | | | | | | | +| Attendant Routing | Y | Y | Y | Y | Y | Y | Y | Y | *Default* | +| Longest Idle4 | Y | Y | Y | Y | N | Y | Y | Y | *Recommended* | +| Round Robin | Y | Y | Y | Y | Y | Y | Y | Y | *Recommended* | +| Serial | Y | Y | Y | Y | Y | Y | Y5 | Y5 | | +| **Agent Routing Options** | | | | | | | | | | +| Presence Based Routing4 | Y | Y | Y | Y11 | N | Y | Y | Y | *Default* | +| Agents can opt out | Y | Y | Y | Y11 | Y8 | Y8 | Y | Y | *Default* | +| **Transfer Modes** | | | | | | | | | | +| Conference Mode6 | Y | Y | Y | Y | Y | Y | Y | Y | *Default* | +| Transfer Mode | Y | Y | Y | Y | Y | Y | Y | Y | | +| **Collaborative Calling** | | | | | | | | | | +| Channel Based Queues | Y | N | N | N | N | N | N/A | Y9 | Agents on non-supported devices can still answer calls however they won't have the collaborative calling user interface | +| **Dynamic caller ID** | | | | | | | | | | +| Standard Call queue | Y | Y | Y | N | N | N | Y | N/A | | +| Channel based Call queue | Y | N/A | N/A | N/A | N/A | N/A | N/A | Y | | +| **PSTN Connectivity Methods** | | | | | | | | | See Note 10 | +| Calling Plans | Y | Y | Y | Y | Y | Y | Y | Y | | +| Direct Routing | Y | Y | Y | Y | N12 | Y | Y7 | Y | | +| Operator Connect | Y | Y | Y | Y | N | Y | Y7 | Y | | +| **Miscellaneous** | | | | | | | | | | +| Call toast shows Resource Account Name | Y | N | Y | N | Y | | Y | Y | | +| Click-to-call | Y | N | N | N | N | N | Y | Y | | +| [Compliance recording](teams-recording-policy.md) | | | | | | | | | Not fully supported | +| [Location based routing](location-based-routing-plan.md#inbound-calls-through-auto-attendants) | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | Not supported | #### Notes diff --git a/Teams/create-custom-meeting-template.md b/Teams/create-custom-meeting-template.md index fe5ab688a1..3a3f5f6db3 100644 --- a/Teams/create-custom-meeting-template.md +++ b/Teams/create-custom-meeting-template.md @@ -5,8 +5,8 @@ author: wlibebe manager: pamgreen ms.topic: article ms.service: msteams -ms.reviewer: janineco -ms.date: 01/08/2024 +ms.reviewer: idilates +ms.date: 11/19/2024 audience: admin ms.localizationpriority: medium f1.keywords: @@ -25,9 +25,9 @@ description: Learn how Microsoft Teams administrators can create a custom meetin [!INCLUDE[Teams Premium ECM](includes/teams-premium-ecm.md)] -Microsoft Teams custom meeting templates (a Teams Premium feature) allow you to specify values for many of the meeting options available to meeting organizers. Templates can be used to configure options that meeting organizers can change or can be used to lock options so that meeting organizers can't change them. For more information about custom meeting templates, see [Overview of custom meeting templates in Microsoft Teams](custom-meeting-templates-overview.md). +Microsoft Teams Premium's custom meeting templates allow you to specify values for many of the meeting options available to meeting organizers. Templates can be used to configure options that meeting organizers can change or can be used to lock options so that meeting organizers can't change them. For more information about custom meeting templates, see [Overview of custom meeting templates in Microsoft Teams](custom-meeting-templates-overview.md). -You can create up to 50 custom templates. See [Manage meeting templates in Microsoft Teams](manage-meeting-templates.md) for information on how to manage which templates are available to your users. +You can create up to 50 custom templates. For information on how to manage which templates are available to your user, see [Manage meeting templates in Microsoft Teams](manage-meeting-templates.md). For each option in the template, you can define the following: @@ -50,15 +50,15 @@ To create a custom meeting template 1. In the Teams admin center, expand **Meetings** and select **Meeting templates**. 1. Select **Add**. -1. Type a name and description for the template. Note that the name and description will truncate after 40 characters when viewed in Teams, but the full name and description are viewable on hover. +1. Enter a name and description for the template. The name and description truncates after 40 characters when viewed in Teams, but the full name and description are viewable on hover. 1. Choose the options that you want to use for this template. (See the sections below for descriptions of each option.) 1. To prevent the meeting organizer from changing an option, select the option and then select **lock**. 1. To prevent the meeting organizer from seeing an option, select the option and then select **Hide**. 1. Select **Save**. -Once the template has been created, it may take up to 24 hours to be available to your users. + Once you create the template, it may take up to 24 hours for your users to see it. -Note that if you change the options of an existing template, the changes affect new meetings scheduled using that template as well as any meetings that have already been scheduled with that template. + If you change the options of an existing template, the changes affect new meetings scheduled using that template, as well as any meetings that are already scheduled with that template. ### Security @@ -86,7 +86,7 @@ Note that if you change the options of an existing template, the changes affect |:------|:----------| |Record meetings automatically|When **On** meetings are recorded automatically.| |Who can record|Specifies whether meetings can be recorded by organizers and co-organizers only or by organizers, co-organizers, and presenters.| -|Copilot|Specifies if Copilot uses a meeting transcript.| +|Allow Copilot|Specifies when Copilot is available and how Copilot uses meeting transcripts.| ### Roles @@ -105,8 +105,7 @@ Note that if you change the options of an existing template, the changes affect ## Related topics -[Overview of custom meeting templates in Microsoft Teams](custom-meeting-templates-overview.md) - -[Use Teams meeting templates, sensitivity labels, and admin policies together](meeting-templates-sensitivity-labels-policies.md) - -[Configure Teams meetings with three tiers of protection](configure-meetings-three-tiers-protection.md) +- [Overview of custom meeting templates in Microsoft Teams](custom-meeting-templates-overview.md) +- [Use Teams meeting templates, sensitivity labels, and admin policies together](meeting-templates-sensitivity-labels-policies.md) +- [Configure Teams meetings with three tiers of protection](configure-meetings-three-tiers-protection.md) +- [Predefined meeting templates in Microsoft Teams](predefined-meeting-template-reference.md) diff --git a/Teams/facilitator-teams.md b/Teams/facilitator-teams.md new file mode 100644 index 0000000000..d7e46529ff --- /dev/null +++ b/Teams/facilitator-teams.md @@ -0,0 +1,134 @@ +--- +title: Set up Facilitator in Microsoft Teams for collaborative AI notes +author: DaniESmith +ms.author: danismith +manager: jtremper +ms.reviewer: solomon.alex, grace.culver +ms.date: 11/18/2024 +ms.topic: article +ms.tgt.pltfrm: cloud +ms.service: msteams +audience: Admin +ms.collection: + - M365-collaboration +ms.custom: + - admindeeplinkTEAMS +f1.keywords: +- NOCSH +appliesto: + - Microsoft Teams +ms.localizationpriority: high +search.appverid: MET150 +description: Learn about how Facilitator in Microsoft Teams can take collaborative AI-generated notes powered by Copilot. +--- + +# Set up Facilitator in Microsoft Teams for collaborative AI-generated notes + +> [!IMPORTANT] +> This feature is currently in Teams Public preview. +> +> Features in preview might not be complete and could undergo changes before becoming available in the public release. They're provided for evaluation and exploration purposes only. + +Facilitator is a collaborative communication agent available to your users in Teams conversations. It combines the power of large language models (LLMs) and Teams data to record notes and help users be productive during collaboration. Stay in the flow of conversation and receive powerful, AI-generated notes within a single workspace. No need for users to switch from reference to reference or app to app. + +Use Facilitator in peer-to-peer: + +- Chats +- Meetings + +Unlike an individual user's queries to Copilot in Teams, Facilitator displays Copilot's notes within the group's conversation. Users can focus on the conversation and let Facilitator take care of the note-taking for everyone. + +Facilitator also continuously updates as the conversation progresses. For example, the AI-generated notes display the options being considered by the team and then replaces those options with a single choice once the group decides. Now, that's intelligent collaboration right in Teams. + +> [!IMPORTANT] +> Facilitator's notes are communally shared between collaborators. +> +> However, when an individual user queries Copilot in Teams using the Copilot in Teams pane, their queries and responses from Copilot remain private to that user. +> +> Users are shown a notice when their queries are private or shared with others. + +For more information about how users can integrate AI-generated notes into their Teams chats, see [Keep track of chats with AI notes in Microsoft Teams](https://support.microsoft.com/office/keep-track-of-chats-with-AI-notes-in-Microsoft-Teams-0b7efbd0-fd3e-48e7-9a4b-4ea22cdc12c0). + +For more information about how users can integrate AI-generated notes into their Teams meetings, see [Automate notetaking in Microsoft Teams meetings](https://support.microsoft.com/office/automate-notetaking-in-Microsoft-Teams-meetings-37657f91-39b5-40eb-9421-45141e3ce9f6). + +## Security, Compliance, and Privacy + +Facilitator, Copilot, and Microsoft 365 are built on Microsoft's comprehensive approach to security, compliance, and privacy. + +When you use Microsoft Purview for your security and compliance management, AI-generated notes are supported by new auditing events that surface in [Data Security Posture Management for AI](/purview/ai-microsoft-purview#data-security-posture-management-for-ai-provides-insights-policies-and-controls-for-ai-apps) and can be used by [eDiscovery with a KQL query](/purview/edisc-keyword-query-language). + +To automatically retain or delete the notes, use a Microsoft Purview Data Lifecycle Management retention policy with the **Teams chat** location for AI-generated notes in chat, and a retention policy for **OneDrive accounts** for AI-generated notes in meetings. + +Other Microsoft Purview solutions either aren't applicable for AI-generated notes or aren't yet supported. + +For more information about security and privacy in Microsoft 365 Copilot, see the following articles: + +- [Data, Privacy, and Security for Microsoft 365 Copilot](/copilot/microsoft-365/microsoft-365-copilot-privacy) for Microsoft 365 Copilot in your organization (work or school). +- [Microsoft Purview data security and compliance protections for generative AI apps](/purview/ai-microsoft-purview). +- [Copilot Pro: Microsoft 365 apps and your privacy](https://support.microsoft.com/office/copilot-pro-microsoft-365-apps-and-your-privacy-6f0d8d80-f4bb-4c9f-989e-64a4adfd62e5) for Microsoft 365 Copilot apps at home. + +### Facilitator limitations + +#### General Facilitator limitations + +- Currently, AI-generated notes aren't supported in [external chats and meetings](trusted-organizations-external-meetings-chat.md). +- Retention labels aren't currently supported for AI-generated notes, which includes applying retention labels for cloud attachments. + +#### AI-generated notes for meetings limitations + +- AI-generated notes for meetings aren't automatically collected as cloud attachments in [Microsoft Preview eDiscovery](/purview/ediscovery-cloud-attachments) because it isn't currently supported. +- Meeting settings like [Prevent copy and paste](manage-chat-sensitive-meetings.md#prevent-copying-or-forwarding-of-chat) and [Watermarks](watermark-meeting-content-video.md) aren't applied to AI-generated notes in meetings. +- AI-generated notes for meetings don't inherit the meeting's sensitivity label; however, a sensitivity label can be applied to the notes' Loop component in the [Loop app or OneDrive](/purview/sensitivity-labels-loop). + +## Prerequisites and licensing + +The following list contains the prerequisites for users to be able to access Facilitator features in Teams chats and meetings: + +- An eligible *Microsoft 365* base license. + - For the list of eligible base licenses, see [Understand licensing requirements for Microsoft 365 Copilot](/copilot/microsoft-365/microsoft-365-copilot-licensing). +- A *Microsoft 365 Copilot* license. + - For information on how to acquire *Microsoft 365 Copilot* licenses, see [Where can I get Microsoft Copilot?](https://support.microsoft.com/topic/where-can-i-get-microsoft-copilot-40a622db-6d25-4266-b008-4bbcb55cf52f). +- Be a Microsoft Teams Public preview participant. + - For information on how to access Teams Public preview features, see [Microsoft Teams Public preview](/microsoftteams/public-preview-doc-updates). + +## Turn on Facilitator for chats and meetings + +As an admin, you control whether Facilitator is available to your entire organization or to a certain group of users. + +Facilitator is turned on by default. However, if all apps are blocked for your organization, Facilitator will also be blocked. + +To turn off or on Facilitator for users, complete the following steps: + +### 1. Turn on Facilitator in the Teams admin center + +1. Sign in to the [Teams admin center](https://admin.teams.microsoft.com/dashboard) with your Teams admin credentials. +1. In the left rail navigation, select **Teams apps** > **Manage apps**. +1. In the apps list's search box, search for **Facilitator**. +1. Select **Facilitator** from the app list. +1. In the actions menu, select **Allow** or **Block**. +1. In the pop-up, select the **Allow** or **Block** button. + 1. AI-generated notes are turned on when **Facilitator** is turned on. + +You can also use [app centric management](/microsoftteams/app-centric-management) to allow and block, create policies, and assign users. + +For more information about managing apps in Teams, see [Manage apps](manage-apps.md). + +### 2. Allow Facilitator for a group of users + +To allow Facilitator for users, a new app policy needs to be created and then assigned to users. + +Follow the instructions at [Use app permission policies to control user access to apps](teams-app-permission-policies.md) to create a new app policy for Facilitator. + +You can then assign the policy to your entire tenant or to a select group of users. Follow the instructions at [Add or modify app availability for users](/microsoftteams/app-centric-management#add-or-modify-app-availability-for-users) to assign the policy to users using app-centric management. + +### 3. Turn on Loop experiences in Teams for AI-generated notes in meetings + +Loop experiences in Teams need to be turned on in order for AI to generate notes in Teams meetings. + +To turn on Loop experiences in Teams, follow the instructions at [Settings management for Loop functionality in Teams](/microsoft-365/loop/loop-components-configuration#settings-management-for-loop-functionality-in-teams). + +## Related articles + +- [What is responsible AI?](https://support.microsoft.com/topic/what-is-responsible-ai-33fc14be-15ea-4c2c-903b-aa493f5b8d92) +- [Frequently asked questions: AI, Microsoft Copilot, and Microsoft Designer](https://support.microsoft.com/topic/frequently-asked-questions-ai-microsoft-copilot-and-microsoft-designer-987b275d-f6f2-4d5d-94c5-e927cffae705) +- [Providing feedback about Microsoft Copilot with Microsoft 365 apps](https://support.microsoft.com/topic/providing-feedback-about-microsoft-copilot-with-microsoft-365-apps-c481c26a-e01a-4be3-bdd0-aee0b0b2a423?ocid=CopilotLab_SMC_Privacy_Feedback) diff --git a/Teams/manage-meeting-templates.md b/Teams/manage-meeting-templates.md index 6edd1a41df..899ddf36e0 100644 --- a/Teams/manage-meeting-templates.md +++ b/Teams/manage-meeting-templates.md @@ -5,8 +5,8 @@ author: wlibebe manager: pamgreen ms.topic: article ms.service: msteams -ms.reviewer: janineco -ms.date: 12/11/2023 +ms.reviewer: idilates +ms.date: 11/19/2024 audience: admin ms.localizationpriority: medium f1.keywords: @@ -23,13 +23,13 @@ description: Learn how Microsoft Teams Administrators can specify which meeting [!INCLUDE[Teams Premium ECM](includes/teams-premium-ecm.md)] -You can use meeting template policies in Microsoft Teams to determine which meeting templates are available to users in your organization. +As an admin, you can use meeting template policies in Microsoft Teams to determine which meeting templates are available to users in your organization. ## Specify which meeting templates are available to users By default, the **Global (Org-wide default)** meeting template policy allows users to see all available templates, including default templates and any custom templates that you've created. If you want to limit which templates are available for different people or groups, you can create policies specifying this. -To create a meeting template policy +To create a meeting template policy, follow these steps: 1. In the Teams admin center, expand **Meetings** and select **Meeting template policies**. 1. Select **Add**. @@ -37,13 +37,13 @@ To create a meeting template policy 1. In the **Viewable templates** list, select any templates that you don't want users with this policy to see, and then select **Hide**. 1. Select **Save**. -Once you've created the policy, you need to assign it to users or groups. See [Assign policies to users and groups](assign-policies-users-and-groups.md) for more information. + Once you've created the policy, you need to assign it to users or groups. See [Assign policies to users and groups](assign-policies-users-and-groups.md) for more information. ## Change which meeting templates are visible to users You can update a meeting template policy if you want to change which templates are available to the users with that policy. -To edit a meeting template policy +To edit a meeting template policy, follow these steps: 1. In the Teams admin center, expand **Meetings** and select **Meeting template policies**. 1. Select the policy you want to change, and then select **Edit**. @@ -53,6 +53,6 @@ To edit a meeting template policy ## Related topics -[Overview of custom meeting templates in Microsoft Teams](custom-meeting-templates-overview.md) - -[Configure Teams meetings with three tiers of protection](configure-meetings-three-tiers-protection.md) +- [Overview of custom meeting templates in Microsoft Teams](custom-meeting-templates-overview.md) +- [Configure Teams meetings with three tiers of protection](configure-meetings-three-tiers-protection.md) +- [Predefined meeting templates in Microsoft Teams](predefined-meeting-template-reference.md) diff --git a/Teams/media/compliance-recorder-expandable.png b/Teams/media/compliance-recorder-expandable.png new file mode 100644 index 0000000000..2b868a5510 Binary files /dev/null and b/Teams/media/compliance-recorder-expandable.png differ diff --git a/Teams/media/compliance-recorder-small.png b/Teams/media/compliance-recorder-small.png new file mode 100644 index 0000000000..cd96556035 Binary files /dev/null and b/Teams/media/compliance-recorder-small.png differ diff --git a/Teams/meeting-recording.md b/Teams/meeting-recording.md index a8821cdbf2..67b7d9880c 100644 --- a/Teams/meeting-recording.md +++ b/Teams/meeting-recording.md @@ -30,7 +30,7 @@ description: Learn how to deploy features in Teams meetings to record audio, vid **APPLIES TO:** ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Meetings ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Webinars ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Town halls -In Microsoft Teams, your users can record their Teams meetings, webinars, and town halls to capture audio, video, and screen sharing activity. This type of recording is called [convenience recording](teams-recording-policy.md#compliance-vs-convenience-recording). The recording happens in Microsoft 365 and is saved to OneDrive or SharePoint, which must be enabled for the user. For details on OneDrive and SharePoint recording storage, see [Use OneDrive and SharePoint for meeting recordings](tmr-meeting-recording-change.md). +In Microsoft Teams, your users can record their Teams meetings, webinars, and town halls to capture audio, video, and screen sharing activity. This type of recording is called [convenience recording](teams-recording-policy.md). The recording happens in Microsoft 365 and is saved to OneDrive or SharePoint, which must be enabled for the user. For details on OneDrive and SharePoint recording storage, see [Use OneDrive and SharePoint for meeting recordings](tmr-meeting-recording-change.md). To learn about recording for live events, see [Live event recording policies in Teams](teams-live-events/live-events-recording-policies.md). diff --git a/Teams/predefined-meeting-template-reference.md b/Teams/predefined-meeting-template-reference.md index 1c6e790e2c..d9ed5d91a1 100644 --- a/Teams/predefined-meeting-template-reference.md +++ b/Teams/predefined-meeting-template-reference.md @@ -6,7 +6,7 @@ manager: pamgreen ms.topic: article ms.service: msteams ms.reviewer: janineco -ms.date: 12/08/2023 +ms.date: 11/19/2024 audience: admin ms.localizationpriority: medium f1.keywords: @@ -24,9 +24,9 @@ description: See a list of Microsoft Teams meeting templates and their settings. [!INCLUDE[Teams Premium ECM](includes/teams-premium-ecm.md)] -The following predefined meeting templates are available in Teams. You can determine which of these templates are available to your users by using [meeting template policies](manage-meeting-templates.md). +The following predefined meeting templates are available in Teams. You can determine which of these templates are available to your users by using [meeting template policies](manage-meeting-templates.md). -If your organization has Teams Premium, you can edit these templates (if noted below) or [create your own meeting templates](create-custom-meeting-template.md). You can also configure Teams Premium settings in editable templates and meeting organizers with a Teams Premium license can use those settings in their meetings. +If your organization has Teams Premium, you can edit these templates (indicated in the Lock status column) or [create your own meeting templates](create-custom-meeting-template.md). You can also configure Teams Premium settings in editable templates and meeting organizers with a Teams Premium license can use those settings in their meetings. ## Virtual appointment @@ -48,13 +48,13 @@ The Virtual appointment meeting template comes with the following options. You c |***Recording and transcription***|||| |Record meetings automatically|Off|Visible|Unlocked| |Who can record meetings|Only organizers and co-organizers|Visible|Unlocked| -|Copilot|On with transcript|Visible|Unlocked| +|Allow Copilot|During and after the meeting|Visible|Unlocked| |***Roles***|||| |Announce when people dialing in join and leave|Off|Visible|Unlocked| |***Meeting engagement***|||| |Allow meeting chat|On during the meeting only|Visible|Unlocked| |Allow reactions|Off|Visible|Unlocked| -|Enable Q&A|Off|Visible|Unlocked| +|Q&A|Off|Visible|Unlocked| |Manage what attendees see|Off|Visible|Unlocked| To learn more, see [Manage the Virtual appointment meeting template in Teams](virtual-appointment-meeting-template.md). @@ -79,19 +79,17 @@ The controlled-content meeting template comes with the following options. You ca |***Recording and transcription***|||| |Record meetings automatically|Off|Visible|Unlocked| |Who can record meetings|Only organizers and co-organizers|Visible|Unlocked| -|Copilot|On with transcript|Visible|Unlocked| +|Allow Copilot|During and after the meeting|Visible|Unlocked| |***Roles***|||| |Announce when people dialing in join and leave|Off|Visible|Unlocked| |***Meeting engagement***|||| |Allow meeting chat|On|Visible|Unlocked| |Allow reactions|Off|Visible|Unlocked| -|Enable Q&A|Off|Visible|Unlocked| +|Q&A|Off|Visible|Unlocked| |Manage what attendees see|Off|Visible|Unlocked| ## Related topics -[Overview of custom meeting templates in Microsoft Teams](custom-meeting-templates-overview.md) - -[Use Teams meeting templates, sensitivity labels, and admin policies together](meeting-templates-sensitivity-labels-policies.md) - -[Configure Teams meetings with three tiers of protection](configure-meetings-three-tiers-protection.md) +- [Overview of custom meeting templates in Microsoft Teams](custom-meeting-templates-overview.md) +- [Use Teams meeting templates, sensitivity labels, and admin policies together](meeting-templates-sensitivity-labels-policies.md) +- [Configure Teams meetings with three tiers of protection](configure-meetings-three-tiers-protection.md) diff --git a/Teams/teams-recording-compliance.md b/Teams/teams-recording-compliance.md new file mode 100644 index 0000000000..707f532bc1 --- /dev/null +++ b/Teams/teams-recording-compliance.md @@ -0,0 +1,229 @@ +--- +title: Introduction to Microsoft Teams third-party compliance recording +ms.author: scottfrancis +author: sfrancis206 +manager: pamgreen +ms.date: 11/11/2024 +audience: Admin +ms.topic: conceptual +ms.service: msteams +ms.reviewer: kiran.kodali +ms.localizationpriority: medium +search.appverid: MET150 +description: Learn about Teams third-party compliance recording for calling, meetings, town halls, webinars, and live events. +f1.keywords: +- CSH +ms.custom: + - Adopt + - seo-marvel-mar2020 +ms.collection: +- Teams_ITAdmin_Adopt +- M365-collaboration +- tier3 +- m365initiative-meetings +- m365initiative-voice +- purview-compliance +appliesto: +- Microsoft Teams +--- + +# Third-party compliance recording for Microsoft Teams calls and meetings + +**APPLIES TO:** ✔️Meetings ✔️Webinars ✔️Calls + +## Compliance recording overview + +Compliance recording is the process of recording and storing communications in a way that follows local, national, and global regulatory requirements. + +Microsoft Teams is enhanced to offer compliance recording of call and meeting communications by supporting integrations with certified, third-party, compliance recording solutions. + +Using a partner solution to record Teams calls, meetings, and events allows corporate compliance officers to securely collect necessary communications in the manner required to meet regulated compliance and legal obligations (such as MiFID II, Dodd-Frank, FDCPA, HIPAA, GDPR, etc.). + +Compliance recording partner solutions are integrated with Teams as shown in the following diagram: + +:::image type="content" source="media/compliance-recorder-small.png" alt-text="Diagram of the flow for when a Teams meeting or call is sent and received." lightbox="media/compliance-recorder-expandable.png"::: + +The Graph API supporting the third-party application’s recording status is available in the following national cloud deployments: + +|Global Service |US Government L4 |US Government L5 (DOD) |China operated by 21Vianet | +|----------------------|------------------|---------------|-----------------| +|Yes |Yes |Yes |No | + +This solution is designed specifically to turn on policy-based compliance recording with Teams. Any other use of this solution isn't supported. + +## Supported compliance recording capabilities + +As a Teams communications admin, with a third-party compliance recording solution, you can specify when to capture calls, meetings, and events for subsequent processing and retention, in accordance with relevant corporate or regulatory policies. +From the available APIs and third-party compliance recording solutions, the following capabilities are supported. + + + + + + + + + + + + + + + + + + + + + + +
PersonaCapabilities
Recorded users
    +

  • Be notified when recording is in progress.

    • +

  • Be informed when policy and/or recorder error is causing changes in calling behavior.

    • +
Communications admin
    +

  • Understand why and how to apply / enforce recording policies to Teams users / endpoints.

    • +

  • Configure and maintain Teams recording policies for the organization.

    • +

  • Monitor and troubleshoot recording-related issues with Teams calls and meetings.

    • +

  • Support internal compliance officer with operational analytics on usage, quality, and reliability.

    • +
Compliance officer
    +

  • Collect all Teams communications in the manner required to meet compliance obligations in appropriate regional boundaries.

    • +

  • Search for interactions based on communication-related metadata or interaction content. Common examples include:

    +
      +

    • Metadata - Participants, time, direction, dialed number, origin number, Custom business data.

      • +

    • Content – Transcription, sentiment, phonetics, related interactions.

      • +
    • +

  • Analyze and interact with collected communications, including the ability to monitor interactions as they're being collected.

    • +

  • Ensure security of collected communications and prevent tampering at all stages.

    • +
+ +For general Teams recording capabilities, see [Teams recordings](./teams-recording-policy.md) + +#### Considerations + +Compliance recording isn't supported for: + +- E911 emergency calling services +- Users operating in Survivable Branch Appliance mode +- PSTN Calls for India users + +**Large Meetings** + +The Compliance Recording platform supports meeting sizes up to 250 users in paired bot mode. +Larger meeting sizes might have performance implications and will be addressed with a future update. + +**Call queues** + +Inbound call queue calls are recorded where users have an assigned compliance recording policy. Some routing methods might involve usability concerns with multiple announcements. + +## Supported notification methods + +Users with an assigned compliance recording policy know that their digital interactions with Teams are being recorded. Depending on the third-party recording solution and how it's configured, users may not be able to disable the recording and may not have access to the recording. + +Compliance recording notifications are supported for the Teams client experiences. The experiences can be both visual and audio. + +### Teams clients - visual notice + +- Desktop/web +- Mobile (iOS/Android) +- Teams Phones +- Teams rooms + +### Other endpoints - audio notice + +- SIP phones +- Skype for Business +- Audio conferencing (audio notice in dial-in number's default or user-selected language) +- PSTN callers (audio notice in Teams user's default language) + +## Recorder development + +The solution for Teams compliance recording is achieved through Microsoft’s third-party partners who develop compliance recording bots, and pair the bot with their recording solution. Each partner solution varies, but each partner uses the same key Graph APIs, an application instance, and a compliance recording policy. + +For a sample of developing a compliance recording bot, see [deploying and testing a sample bot](https://github.com/microsoftgraph/microsoft-graph-comms-samples/tree/a3943bafd73ce0df780c0e1ac3428e3de13a101f/Samples/BetaSamples/LocalMediaSamples/ComplianceRecordingBot#bot-registration). + +## Third-party compliance recording partners + +Microsoft created a compliance recording for Microsoft Teams certification program while making Teams APIs available for partners to develop and integrate compliance recording solutions. This program provides customers with the assurance that each participating partner's solution is tested and verified to provide the quality, compatibility, and reliability expected from a Microsoft solution. + +The following site lists current partners with certified their compliance recording solution for Microsoft Teams: +[Modern Work for Partners - Compliance Recording Solutions](https://cloudpartners.transform.microsoft.com/compliance-recording-solutions) + +Microsoft only supports compliance recording solutions from the listed certified partners. If there are enablement or operational issues, you must contact your compliance recording partner first. If the partner determines the issue is with Microsoft, they might ask you to raise a case with Microsoft, providing context of the investigation completed by the partner. If needed, the partner can bring the issue to Microsoft through their Microsoft support channel. Microsoft might reject support cases where a non-certified Compliance Recording solution is used, or if investigation shows that the issue is one the partner can address. + +If you're a vendor seeking to join the certification program, fill out the calling platform intake as the next step. +[Calling Platform Intake](https://aka.ms/CallingPlatformIntake) + +## Create and manage your compliance recording policy + +Once a compliance recording solution is in place, a Teams admin can create and assign recording policies to control which users are recorded and which recorder is used for each user. Recorders are automatically invited to participate in conversations based on the configuration of these policies when a communication interaction takes place. +Compliance +recording policies are managed using [Microsoft +PowerShell](./teams-powershell-overview.md) +and can be applied at the tenant, per-user, and security group level for each +organization. You can find more information on Microsoft Learn for +[Meeting +policies](./meeting-policies-overview.md), + [calling +policies](./teams-calling-policy.md) and [group +policies](./assign-policies-users-and-groups.md#assign-a-policy-to-a-group). + +1. Create an application instance in your tenant. + + ```powershell + New-CsOnlineApplicationInstance -UserPrincipalName cr.instance@contoso.onmicrosoft.com -DisplayName ComplianceRecordingBotInstance -ApplicationId fcc88ff5-a42d-49cf-b3d8-f2e1f609d511 + ``` + + Example results + - RunspaceId : 4c13efa6-77bc-42db-b5bf-bdd62cdfc5df + - ObjectId : 5069aae5-c451-4983-9e57-9455ced220b7 + - TenantId : 5b943d7c-5e14-474b-8237-5022eb8e0dc9 + - UserPrincipalName : cr.instance@contoso.onmicrosoft.com + - ApplicationId : fcc88ff5-a42d-49cf-b3d8-f2e1f609d511 + - DisplayName : ComplianceRecordingBotInstance + - PhoneNumber : + + ```powershell + Sync-CsOnlineApplicationInstance -ObjectId 5069aae5-c451-4983-9e57-9455ced220b7 + ``` + +2. Create a Compliance Recording policy. + + ```powershell + New-CsTeamsComplianceRecordingPolicy -Identity TestComplianceRecordingPolicy -Enabled $true -Description "Test policy created by tenant admin" + ``` + + Example results + - Identity : Global + - ComplianceRecordingApplications : {} + - Enabled : True + - WarnUserOnRemoval : True + - Description : Test policy created by tenant admin + + ```powershell + Set-CsTeamsComplianceRecordingPolicy -Identity TestComplianceRecordingPolicy ` + -ComplianceRecordingApplications @(New-CsTeamsComplianceRecordingApplication -Id 5069aae5-c451-4983-9e57-9455ced220b7 -Parent TestComplianceRecordingPolicy) + ``` + + See [Set-CsTeamsComplianceRecordingPolicy](/powershell/module/teams/set-csteamscompliancerecordingpolicy). + +3. Assign the Compliance Recording policy to a user. + + ```powershell + Grant-CsTeamsComplianceRecordingPolicy -Identity testuser@contoso.onmicrosoft.com -PolicyName TestComplianceRecordingPolicy + ``` + + See [Grant-CsTeamsComplianceRecordingPolicy](/powershell/module/teams/grant-csteamscompliancerecordingpolicy). + + ```powershell + Get-CsOnlineUser testuser@contoso.onmicrosoft.com | select SipAddress, TenantId, TeamsComplianceRecordingPolicy | fl + ``` + + Example + - UserPrincipalName : testuser@contoso.onmicrosoft.com + - TenantId : 5b943d7c-5e14-474b-8237-5022eb8e0dc9 + - TeamsComplianceRecordingPolicy : TestComplianceRecordingPolicy + +### Related topics  + +- [Teams Recordings - Microsoft Teams | Microsoft Learn](./teams-recording-policy.md) +- diff --git a/Teams/teams-recording-policy.md b/Teams/teams-recording-policy.md index e3e0a04d30..ae9c43faef 100644 --- a/Teams/teams-recording-policy.md +++ b/Teams/teams-recording-policy.md @@ -1,16 +1,16 @@ --- -title: Introduction to Microsoft Teams third party compliance recording -ms.author: wlibebe -author: wlibebe +title: Introduction to recording Microsoft Teams calls and meetings +ms.author: scottfrancis +author: sfrancis206 manager: pamgreen -ms.date: 06/27/2024 +ms.date: 11/11/2024 audience: Admin ms.topic: conceptual ms.service: msteams -ms.reviewer: ritikag,lisma +ms.reviewer: ritikag ms.localizationpriority: medium search.appverid: MET150 -description: Learn about Teams third party compliance recording for calling, meetings, town halls, webinars, and live events. +description: Learn about Teams recordings for calling, meetings, town halls, webinars, and live events. f1.keywords: - CSH ms.custom: @@ -20,295 +20,69 @@ ms.collection: - Teams_ITAdmin_Adopt - M365-collaboration - tier3 +- m365initiative-meetings +- m365initiative-voice - purview-compliance appliesto: - Microsoft Teams --- -# Introduction to Microsoft Teams third party compliance recording +# Introduction to Teams recording **APPLIES TO:** ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Meetings ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Webinars ![Image of a checkmark for yes](/office/media/icons/success-teams.png)Town halls ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Calls ![Image of a checkmark for yes](/office/media/icons/success-teams.png) Live events ## Overview -Third-party compliance recording allows orgs using Microsoft Teams for calls, meetings, and events to implement an admin policy for automatic recording. For your users to make calls, they must have an assigned Teams Phone license. As an admin, you can also choose when to capture calls, meetings, and events for subsequent processing and retention, in accordance with relevant corporate or regulatory policies. +In Microsoft Teams, your users can record calls and meetings to reference later and share with others. Communications can also be automatically preserved for industry compliance reasons. Call and meeting recordings capture media shared during the session (audio, video, and screen sharing activity), and are stored according to your policies. -Teams is enhanced to support the integration of partner recording solutions. These enhancements provide a complete solution for configuring, managing, recording, storing, and analyzing Teams communications. The enhancements include communications platform APIs and events for recording, which provide: +There are two recording features that can be enabled with policy: -- Seamless, high-quality media capture across devices. Compliance recording captures the same screenshare activity as convenience recording. To learn which screenshare activities are captured, see [Record a meeting in Microsoft Teams](https://support.microsoft.com/office/record-a-meeting-in-microsoft-teams-34dfbe7f-b07d-4a27-b4c6-de62f1348c24). +- **Convenience recording**- an ad-hoc recording of a call or meeting that a user starts and manages. -- Support for interaction capture between Teams users and supported calling, meeting, and endpoints (Teams, Teams Mobile, Skype for Business, PSTN). +- **Compliance recording**-calls and meetings that are automatically recorded without user intervention and owned by the company, using a third-party solution. -Compliance recording can be enabled on Microsoft 365 A3/A5/E3/E5/Business Premium, Office 365 A3/A5/E3/E5 users, Teams Rooms license, or Microsoft Teams Shared Devices license. +The following table compares convenience and compliance recording. -> [!NOTE] -> Compliance recording isn't currently supported for E911 emergency calling services. +| Property | Convenience Recording | Compliance Recording | +| ---------------------- | :------------------: | :---------------: | +| Recording initiator | Licensed Teams user, enabled with meeting / calling policy | Admin (system) | +| Storage and access owner | [Meeting storage and permissions](tmr-meeting-recording-change.md) | Admin / compliance officer | +| Participant notification enforced | Yes | Yes | +| Participant consent supported | Yes | No | +| Media recorded | Voice, video, screen share, PPT Live | Voice, video, screen share | +| Retention policy | [Meeting storage and permissions](tmr-meeting-recording-change.md) | Configurable with partner solution | +| Recording policy | Configurable with Teams Admin Center (Meeting policy + Calling policy) | Configurable with user policy | -The compliance recording solution integration capabilities were also -reviewed at Ignite 2019 in the [Compliance -Recording and Microsoft Teams -session](https://myignite.microsoft.com/archives/IG19-VCE40). +- Guests can't initiate convenience recordings. -### Compliance vs convenience recording +- Users in trusted organizations can’t initiate convenience recordings when they join meetings in your organization. -In Microsoft Teams, there are two types of recordings: +- Users in trusted organizations can initiate convenience recordings of unscheduled, 1:1 calls originated by either party. If they initiate, the recording adheres to the calling policy defined in the trusted organization's tenant. -- **Convenience recording-** an ad-hoc recording of a call or meeting that a user starts. To learn more about convenience recording, see [Teams meeting recording](meeting-recording.md). -- **Compliance recording-** using an admin policy to automatically record calls and meetings. +- Users assigned with Edu A1 license only, can record manually but can't use meeting options to auto-record. -The following table details differences between convenience and compliance recording. +Meeting recordings don't capture: -| Type | Convenience Recording | Compliance Recording | -| ---------------------- | ------------------ | --------------- | -| Initiator | User | Admin (system) | -| Target | Per-call / meeting / event | Per-user | -| Storage owner | Organizer | Admin or compliance officer | -| Participant notification required? | Yes | Yes | -| Retention Policy | Organizer's SharePoint Online policy enforced | Yes | +- More than four peoples' video streams at once +- Whiteboards and annotations +- Shared notes +- Content shared by apps +- Videos or animations embedded in PowerPoint Live presentations +- Multi-screen share -Users with an assigned compliance recording policy know that their digital -interactions with Teams are being recorded. They also know that they can't -disable the recording and don't have access to the recording once the interaction is complete. The recording becomes part of the organizational archive. This archive is available to compliance and legal personnel for eDiscovery, legal hold, and other corporate retention uses. +Calls in Teams are unscheduled, peer-to-peer Teams client sessions (encompassing internal and external Teams users). In convenience and compliance recording, policy scope for calls includes Teams PSTN calls, if the user has one of the following licenses: Microsoft 365 E5, Office 365 E5, or Microsoft/Office 365 E3 with Teams Phone Add-on license. -## Solution architecture overview +> [!TIP] +> To learn and share more about recording options that you may allow your users to control, refer to [Record a meeting in Microsoft Teams](https://support.microsoft.com/office/record-a-meeting-in-microsoft-teams-34dfbe7f-b07d-4a27-b4c6-de62f1348c24).  -Compliance recording solutions are integrated with Teams as -shown in the following diagram: +## Managing recording policies -:::image type="content" source="media/compliance-recording-diagram-small.png" alt-text="Diagram of the flow for when a Teams meeting or call is sent and received." lightbox="media/compliance-recording-diagram-expand.png"::: +Navigate to these sections for more specific details on convenience and compliance recording: -> [!NOTE] -> This solution is designed specifically to enable policy-based compliance recording with Teams. Any other use of this solution isn't supported. +| Meeting convenience recording | Call convenience recording | Meeting and call compliance recording | +| :------------------: | :---------------: | :---------------: | +| [Manage Teams recording policies for meetings](./meeting-recording.md)| [Manage Teams recording policies for calls](./call-recording-transcription-captions.md) | [Teams compliance recording for meetings and calls](./teams-recording-compliance.md) | -## Example user needs +### Related topics - - - - - - - - - - - - - - - - - - - - - -
PersonaNeeds
Recorded users
    -

  • Be notified when recording is in progress.

    • -

  • Be informed when policy and/or recorder error is causing changes in calling behavior.

    • -
Communications admin
    -

  • Understand why and how to apply / enforce recording policies to Teams users / endpoints.

    • -

  • Configure and maintain Teams recording policies for the organization.

    • -

  • Monitor and troubleshoot recording-related issues with Teams calls and meetings.

    • -

  • Support internal compliance officer with operational analytics on usage, quality, and reliability.

    • -
Compliance officer
    -

  • Collect all Teams communications in the manner required to meet compliance obligations in appropriate regional boundaries.

    • -

  • Search for interactions based on communication-related metadata or interaction content. Common examples include:

    -
      -

    • Metadata - Participants, time, direction, dialed number, origin number, Custom business data.

      • -

    • Content – Transcription, sentiment, phonetics, related interactions.

      • -
    • -

  • Analyze and interact with collected communications, including the ability to monitor interactions as they're being collected.

    • -

  • Ensure security of collected communications and prevent tampering at all stages.

    • -
- -## Recorders - -The core component of the compliance recording solution is the recorder. -Recorders are built as scalable Azure-based services (bots) that -[use Microsoft's communications -platform](/graph/cloud-communications-concept-overview) -and register as applications with Microsoft Graph. The recorder provides -the direct interaction with the Teams calls and meetings -[communications platform -APIs](/graph/api/resources/communications-api-overview) -and provides the endpoint for media ingestion. - -A [sample compliance recorder application is -available](https://github.com/microsoftgraph/microsoft-graph-comms-samples/tree/a3943bafd73ce0df780c0e1ac3428e3de13a101f/Samples/BetaSamples/LocalMediaSamples/ComplianceRecordingBot) -that shows how to configure the bot, create the app instance and assign -the compliance policies. The sample also has examples on API usage for -recording specific interactions such as handling -[incoming -call](https://github.com/microsoftgraph/microsoft-graph-comms-samples/blob/a3943bafd73ce0df780c0e1ac3428e3de13a101f/Samples/BetaSamples/LocalMediaSamples/ComplianceRecordingBot/FrontEnd/Http/Controllers/PlatformCallController.cs#L199-L244) routing, -[changing recording -states](https://github.com/microsoftgraph/microsoft-graph-comms-samples/blob/a3943bafd73ce0df780c0e1ac3428e3de13a101f/Samples/BetaSamples/LocalMediaSamples/ComplianceRecordingBot/FrontEnd/Bot/CallHandler.cs#L135-L138), -and [removing the user who is being -recorded](https://github.com/microsoftgraph/microsoft-graph-comms-samples/blob/a3943bafd73ce0df780c0e1ac3428e3de13a101f/Samples/BetaSamples/LocalMediaSamples/ComplianceRecordingBot/FrontEnd/Bot/CallHandler.cs#L121-L126). -Graph documentation on the specific APIs can be found here for -[updateRecordingStatus](/graph/api/call-updaterecordingstatus?tabs=http) -and -[incomingContext](/graph/api/resources/incomingcontext). - -The exact implementation of the recorder service varies by partner, but must be designed to support multiple recorders. This requirement ensures high availability and geographical distribution, reducing latency between Teams and the recorder. Recorders should be designed with resiliency and redundancy in mind. - -Partners must confirm the minimum required release version of the -Microsoft Graph communications APIs and SDKs with Microsoft before -submitting their solution for certification. This requirement ensures that all -requirements of compliance recording integration are supported. - -Requirements that are fundamental for compliance recording -scenario: - -- Recorder bot must be deployed in Azure. - -- Recorder bot must run on a Windows VM in Azure. - -- Recorder bot outbound firewall destination IP address must be open to the Azure public IP range. - -- Recorder bot inbound firewall source IP address must be open to the [Teams IP range](/microsoft-365/enterprise/urls-and-ip-address-ranges#microsoft-teams). - -The Azure and Windows VM requirements only apply to the Teams Bot -component, which means that a partner might implement the rest of the -platform of their choice provided they can meet the relevant performance -and functional requirements for compliance recording. - -## Create and manage your compliance recording policy - -Through creating and assigning compliance recording policies, as an admin, you can determine which users are to be recorded and which recorder is used for each user. Recorders are automatically invited to participate in conversations based on the configuration of these policies when a communication interaction takes place. -Compliance -recording policies are managed using [Microsoft -PowerShell](./teams-powershell-overview.md) -and can be applied at the tenant, per-user, and security group level for each -organization. You can find more information on Microsoft Learn for -[Meeting -policies](./meeting-policies-overview.md), - [calling -policies](./teams-calling-policy.md) and [group -policies](./assign-policies-users-and-groups.md#assign-a-policy-to-a-group). - -1. Create an application instance in your tenant. - - ```powershell - PS C:\> New-CsOnlineApplicationInstance -UserPrincipalName cr.instance@contoso.onmicrosoft.com -DisplayName ComplianceRecordingBotInstance -ApplicationId fcc88ff5-a42d-49cf-b3d8-f2e1f609d511 - - RunspaceId : 4c13efa6-77bc-42db-b5bf-bdd62cdfc5df - ObjectId : 5069aae5-c451-4983-9e57-9455ced220b7 - TenantId : 5b943d7c-5e14-474b-8237-5022eb8e0dc9 - UserPrincipalName : cr.instance@contoso.onmicrosoft.com - ApplicationId : fcc88ff5-a42d-49cf-b3d8-f2e1f609d511 - DisplayName : ComplianceRecordingBotInstance - PhoneNumber : - ``` - - ```powershell - PS C:\> Sync-CsOnlineApplicationInstance -ObjectId 5069aae5-c451-4983-9e57-9455ced220b7 - ``` - -2. Create a Compliance Recording policy. - - ```powershell - PS C:\> New-CsTeamsComplianceRecordingPolicy -Identity TestComplianceRecordingPolicy -Enabled $true -Description "Test policy created by tenant admin" - - Identity : Global - ComplianceRecordingApplications : {} - Enabled : True - WarnUserOnRemoval : True - Description : Test policy created by tenant admin - ``` - - ```powershell - PS C:\> Set-CsTeamsComplianceRecordingPolicy -Identity TestComplianceRecordingPolicy ` - -ComplianceRecordingApplications @(New-CsTeamsComplianceRecordingApplication -Id 5069aae5-c451-4983-9e57-9455ced220b7 -Parent TestComplianceRecordingPolicy) - ``` - - See [Set-CsTeamsComplianceRecordingPolicy](/powershell/module/teams/set-csteamscompliancerecordingpolicy). - -3. Assign the Compliance Recording policy to a user. - - ```powershell - PS C:\> Grant-CsTeamsComplianceRecordingPolicy -Identity testuser@contoso.onmicrosoft.com -PolicyName TestComplianceRecordingPolicy - ``` - - See [Grant-CsTeamsComplianceRecordingPolicy](/powershell/module/teams/grant-csteamscompliancerecordingpolicy). - - ```powershell - PS C:\> Get-CsOnlineUser testuser@contoso.onmicrosoft.com | select SipAddress, TenantId, TeamsComplianceRecordingPolicy | fl - - UserPrincipalName : testuser@contoso.onmicrosoft.com - TenantId : 5b943d7c-5e14-474b-8237-5022eb8e0dc9 - TeamsComplianceRecordingPolicy : TestComplianceRecordingPolicy - ``` - -## User experiences - -### PSTN calls - -Inbound call queue (CQ) calls are recorded for users who have an assigned compliance recording (CR) policy. Some routing methods might involve usability concerns with multiple announcements. We recommend appropriately configuring your call queues to align with your organization's intended user experience. - -Compliance recording doesn't work if users have an Internet outage, and make or receive PSTN calls using an SBA. - -### Notifications - -Support for notifications is enabled using the Teams client experiences. The experiences can be either visual or audio. - -#### Teams clients - visual notice - -- Desktop/web -- Mobile (iOS/Android) -- Teams Phones -- Teams rooms - -#### Other endpoints - audio notice - -- SIP phones -- Skype for Business -- Audio conferencing (audio notice in dial-in number's default or user-selected language) -- PSTN callers (audio notice in Teams user's default language) - -## Compliance recording for Teams certification programs - -In addition to publishing publicly available APIs allowing partners to develop and integrate CCaaS solutions with Teams, we developed the compliance recording for Microsoft Teams certification program. This program provides customers with the assurance that each participating partner's solution is tested and verified. Customers can be assured that partners provide the quality, compatibility, and reliability they expect from Microsoft solutions. - -The following partners certify their solution for Microsoft Teams.

- -|Partner|Solution website | -|:--|:--| -|ASC Technologies |[https://www.asctechnologies.com/english/ASC_Recording_Insights_Compliance_Recording_for_Microsoft_Teams.html](https://www.asctechnologies.com/english/ASC_Recording_Insights_Compliance_Recording_for_Microsoft_Teams.html) | -|AudioCodes |[https://online.audiocodes.com/smarttap-360-live-for-microsoft-teams](https://online.audiocodes.com/smarttap-360-live-for-microsoft-teams) | -|CallCabinet |[https://www.callcabinet.com/compliance-microsoft-teams-call-recording](https://www.callcabinet.com/compliance-microsoft-teams-call-recording ) | -|Dubber |[https://www.dubber.net/call-recording/](https://www.dubber.net/call-recording/) | -|Imagicle |[https://www.imagicle.com/en/products/call-recording/](https://www.imagicle.com/en/products/call-recording/) | -|Insightful Technology |[https://insightfultechnology.com/teams/](https://insightfultechnology.com/teams/) | -|Luware |[https://luware.com/en/solution/microsoft-teams-recording/](https://luware.com/en/solution/microsoft-teams-recording/) | -|Mida Solutions |[https://www.midasolutions.com/recorder-for-teams/](https://www.midasolutions.com/recorder-for-teams/) | -|NICE Engage |[https://www.nice.com/products/workforce-engagement/call-recording/air-and-engage](https://www.nice.com/products/workforce-engagement/call-recording/air-and-engage) | -|NICE NTR-X |[https://www.niceactimize.com/compliance/ms-teams-recording.html](https://www.niceactimize.com/compliance/ms-teams-recording.html) | -|Numonix |[https://numonix.cloud](https://numonix.cloud) | -|Oak Innovation |[https://www.oakinnovate.com/clarify](https://www.oakinnovate.com/clarify) | -|Red Box |[https://www.redboxvoice.com/compliance-recording-for-microsoft-teams](https://www.redboxvoice.com/red-box-partners/microsoft-integration/compliance-recording-for-microsoft-teams) | -|Theta Lake |[https://thetalake.com/integrations/microsoft/](https://thetalake.com/integrations/microsoft/) | -|Touch Call Recording (GuardRec Compliance 2022.10.3) |[https://touchcallrecording.com/teams-policy-based-recording-for-callings-and-meetings](https://touchcallrecording.com/teams-policy-based-recording-for-callings-and-meetings) | -|Verint |[https://www.verba.com/solutions/microsoft-teams-recording](https://www.verba.com/solutions/microsoft-teams-recording) | - -
-The following partners are in the process of certifying their solution for Microsoft Teams.

- -|Partner|Solution website | -|:--|:--| -|Cloud World Wide Services |[https://recordia.net/microsoft-teams-call-recording/](https://recordia.net/microsoft-teams-call-recording/) | -|CreaLog |[https://www.crealog.com/en/products-solutions/recording/](https://www.crealog.com/en/products-solutions/recording/) | -|Landis Technologies |[https://landistechnologies.com/](https://landistechnologies.com/) | -|Redwood Technologies |[https://www.contentguru.com/en-us/solutions/needs/compliance-recording-ms-teams/](https://www.contentguru.com/en-us/solutions/needs/compliance-recording-ms-teams/) | - -This list gets updated as more partners join and meet the certification criteria. - -## Support boundaries - -Microsoft only supports compliance recording solutions from the listed certified partners. If there are issues, you must contact your compliance recording partner first. If needed, the partner can bring the issue to Microsoft through internal channels. Microsoft might reject support cases where a non-certified Compliance Recording solution is used, or if investigation shows the issue is one that the partner can address. - -## Next steps - -If you're a vendor seeking to join the certification program, fill out the calling platform intake as the next step. -> [!div class="nextstepaction"] -> [Calling Platform Intake](https://aka.ms/CallingPlatformIntake) +- [Teams settings and policies reference - Microsoft Teams | Microsoft Learn](settings-policies-reference.md) diff --git a/Teams/toc.yml b/Teams/toc.yml index ed3109bb6a..845ccb1b38 100644 --- a/Teams/toc.yml +++ b/Teams/toc.yml @@ -3,6 +3,8 @@ items: href: teams-overview.md - name: Teams Premium overview href: enhanced-teams-experience.md +- name: Set up Facilitator for AI notes + href: facilitator-teams.md - name: Get started items: - name: Deployment overview @@ -335,8 +337,12 @@ items: href: /microsoft-365/compliance/information-barriers-teams-shared-channels?bc=%2fmicrosoftteams%2fbreadcrumb%2ftoc.json&toc=%2fmicrosoftteams%2ftoc.json - name: Legal hold href: /microsoft-365/compliance/ediscovery-teams-legal-hold?bc=%2fmicrosoftteams%2fbreadcrumb%2ftoc.json&toc=%2fmicrosoftteams%2ftoc.json - - name: Third party compliance recording - href: teams-recording-policy.md + - name: Recording + items: + - name: Introduction to Teams recording + href: teams-recording-policy.md + - name: Third party compliance recording + href: teams-recording-compliance.md - name: Retention policies href: retention-policies.md - name: Sensitivity labels