Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Microsoft Purview compliance portal: Blanket custom retention policies which apply to all Audit recordTypes

From Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.

Rollout

Roadmap
395215

Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".

Schedule dates changed in the text

Date phrases in schedule sentences differ between the versions we saw
  • Seen 23 Jul 2024 early June 2024, mid-June 2024, early August 2024, mid-August 2024 → mid-September 2024, late October 2024
  • Seen 28 Jun 2024 late June 2024, mid-July 2024, late July 2024 → early June 2024, early August 2024, mid-August 2024, late August 2024

Read from date phrases in Microsoft's text, not from notice metadata. A changed phrase can be a moved rollout, a new milestone or just rewording; "What changed" below shows which.

What the notice says

Microsoft’s text, safely structured

Updated July 23, 2024: We have updated the rollout timeline below. Thank you for your patience.

Microsoft Purview is enhancing the Audit custom retention policy experience to make it easier for customers to change the default retention policy across all their Audit logs. With this change, customers can now create blanket custom retention policies that apply to all Audit recordTypes. This capability will become available in addition to the existing support of manually selecting specific recordTypes in a custom policy.

This message is associated with Microsoft 365 Roadmap ID 395215

When this will happen

Public Preview: We will begin rolling out late August 2024 (previously mid-July) and expect to complete by mid-September 2024 (previously late July).

General Availability: We will begin rolling out late September2024 (previously mid-August) and expect to complete by late October 2024 (previously late August).

How this will affect your organization

This change now allows security admins in your organization to apply a default retention policy to all of the Audit recordTypes. Previously, an admin had to manually select every single recordType in the dropdown menu of a custom retention policy. Moreover, it did not automatically include any new recordTypes added to the Audit log at a future time.

With this change, an admin can simply select All under the recordTypes field to apply the custom retention policy to all existing and future recordTypes.

What you need to do to prepare

To apply a custom retention policy to all recordType logs, an admin can simply select All under the recordTypes field to apply the custom retention policy to all existing and future recordTypes.

More information is available here: Manage audit log retention policies | Microsoft Learn

What changed

Between archive captures, newest first
  1. Updated June 28,July 23, 2024: We have updated the rollout timeline below. Thank you for your patience. Today, users can share content to a Microsoft Teams meeting directly from a standalone webapp (in Purview is enhancing the browser) if developers have embedded a Share-in-Meeting control in their webapps. Today, this control allows users Audit custom retention policy experience to make it easier for customers to share content only to an ongoing Teams meeting (or a new ad-hoc meeting) on the same device. In change the default retention policy across all their Audit logs. With this rollout, we will retain the control's existing capabilities, and we will enhance the control change, customers can now create blanket custom retention policies that apply to enable users to share content to a meeting scheduled for the future. We all Audit recordTypes. This capability will combine the Share-in-Meeting controls withbecome available in addition to the existing Share to Teams dialog box, so users can use one dialog box to share from a Teams app to Teams chats, channels, or meetings. We are also introducing the ability for users to choose Present Now from the dialog to present content support of manually selecting specific recordTypes in a Teams meeting. Developers can choose to opt into the features in this rollout. custom policy. This rollout applies to Teams for Windows, the web, and Mac. This message is associated with Microsoft 365 Roadmap ID 394670.395215 When this will happen: Public Developer Preview: We will begin rolling out early June 2024 and expect to complete by mid-June 2024. Targeted Release: We will begin rolling out early late August 2024 (previously early July) mid-July) and expect to complete by mid-Augustmid-September 2024 (previously mid-July).late July). General Availability (Worldwide, GCC): Availability: We will begin rolling out mid-August 2024late September2024 (previously early July) mid-August) and expect to complete by late AugustOctober 2024 (previously mid-July).late August). How this will affect your organization: Additional enhancements for developers in this this rollout: When a meeting begins, the app side panel is opened automatically for the user who shared the content This change now allows security admins in your organization to the meeting. Exposes shared content information for the app apply a default retention policy to get the list all of content shared, display the content, and have it readily available in the side panel. Notifies the meeting participants through an experience Audit recordTypes. Previously, an admin had to manually select every single recordType in the meeting chat thatdropdown menu of a user has shared content in the meeting. App developers can embed the Sharecustom retention policy. Moreover, it did not automatically include any new recordTypes added to Teams control on their external webapp: Using the Share to Teams control, users canthe Audit log at a future time. With this change, an admin can simply select a chat, channel, or meeting All under the recordTypes field to share their content to. Users can also choose apply the custom retention policy to present the content onto in a Teams meeting with the Present Now feature. all existing and future recordTypes. What you need to do to prepare: This rollout will happen by the specified date with noTo apply a custom retention policy to all recordType logs, an admin action required beforecan simply select All under the rollout. Please notify your app developers about this change and update any relevant documentation as appropriate. Before rollout, we will update this post with revised documentation.recordTypes field to apply the custom retention policy to all existing and future recordTypes. More information is available here: Manage audit log retention policies | Microsoft Learn

    • Tags New feature, Admin impact → Updated message, New feature, Admin impact

    Microsoft Purview is enhancingUpdated June 28, 2024: We have updated the Audit custom retention policy experiencerollout timeline below. Thank you for your patience. Today, users can share content to make it easier for customers to changea Microsoft Teams meeting directly from a standalone webapp (in the default retention policy across allbrowser) if developers have embedded a Share-in-Meeting control in their Audit logs. Withwebapps. Today, this control allows users to share content only to an ongoing Teams meeting (or a new ad-hoc meeting) on the same device. In this change, customers can now create blanket custom retention policies that applyrollout, we will retain the control's existing capabilities, and we will enhance the control to enable users to share content to all Audit recordTypes. This capabilitya meeting scheduled for the future. We will become available in additioncombine the Share-in-Meeting controls with the existing Share to Teams dialog box, so users can use one dialog box to share from a Teams app to Teams chats, channels, or meetings. We are also introducing the existing support of manually selecting specific recordTypes ability for users to choose Present Now from the dialog to present content in a custom policy.Teams meeting. Developers can choose to opt into the features in this rollout. This rollout applies to Teams for Windows, the web, and Mac. This message is associated with Microsoft 365 Roadmap ID 395215394670. When this will happen: Public Developer Preview: We will begin rolling out early June 2024 and expect to complete by mid-June 2024. Targeted Release: We will begin rolling out early August 2024 (previously early July) and expect to complete by late June 2024.mid-August 2024 (previously mid-July). General Availability:Availability (Worldwide, GCC): We will begin rolling out mid-Julymid-August 2024 (previously early July) and expect to complete by late July 2024.August 2024 (previously mid-July). How this will affect your organization: This change now allows security admins in your organizationAdditional enhancements for developers in this this rollout: When a meeting begins, the app side panel is opened automatically for the user who shared the content to apply a default retention policythe meeting. Exposes shared content information for the app to allget the list of content shared, display the Audit recordTypes. Previously, an admin had to manually select every single recordTypecontent, and have it readily available in the side panel. Notifies the meeting participants through an experience in the dropdown menu ofmeeting chat that a custom retention policy. Moreover, it did not automatically include any new recordTypes addeduser has shared content in the meeting. App developers can embed the Share to Teams control on their external webapp: Using the Audit log atShare to Teams control, users can select a future time. With this change, an admin can simply select All under the recordTypes field chat, channel, or meeting to share their content to. Users can also choose to applypresent the custom retention policy to all existing and future recordTypes.content onto in a Teams meeting with the Present Now feature. What you need to do to prepare: To apply a custom retention policy to all recordType logs, an This rollout will happen by the specified date with no admin can simply select All under action required before the recordTypes field to apply the custom retention policy to all existing and future recordTypes. More information is available here: Manage audit log retention policies | Microsoft Learnrollout. Please notify your app developers about this change and update any relevant documentation as appropriate. Before rollout, we will update this post with revised documentation.

  2. · first version seen

Learn more

Links from the notice and their documentation checks

No related announcements were found in the saved public history. Check the source for newer announcements.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
  • 1 linked page has not been read yet.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 00:16 UTC · 274 of 275 readable · 251 fully read · 18 waiting for GitHub's hourly limit · documentation 469/469 current