Public mode

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

Some sources, documents or advisories need attention: 272/272 feeds/APIs · 469/469 docs · 8/9 advisories · checked 07:24 UTC Customize Public modeDiscuss ChangeIntel on Discord

Microsoft Purview | Data Loss Prevention: Ability to rename policy and rules

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

Rollout

Roadmap
370535

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

What the notice says

Microsoft’s text, with source markup removed
Coming soon for This feature gives the ability for the DLP admin to rename the existing policy/rule without having to create the entire the rule or policy again This message is associated with Microsoft 365 Roadmap ID 370535. When this will happen: Public Preview: We will begin rolling out mid-July 2025 and expect to complete by late July 2025. General Availability (Worldwide): We will begin rolling out late August 2025 and expect to complete by mid-September 2025. General Availability (GCC, GCC High, DOD): We will begin rolling out mid-October 2025 and expect to complete by late October 2025. How this will affect your organization: This feature is currently supported for major workloads: Microsoft Exchange Online, Microsoft Teams, Microsoft SharePoint, Microsoft OneDrive, and Microsoft Endpoint. With this rollout, we will also introduce a new field called DisplayName that you can edit in DLP and in Microsoft PowerShell. For all practical purposes the display name can be used as the name for all the operations. Renaming an existing policy: Editing a rule to rename it: All DLP experiences (such as Incident Reports, User Notifications, Email Alerts, DLP Alerts, MTP Alerts, and Activity Explorer) will start showing the policy/rule names at the point of record generation. For example: If a policy is named P1 at T0 and updated to P2 at T1, all records generated between T0 and T1 will have the name as P1 and all the records from T1 will have the name as P2. This feature will be available by default for admins to configure. What you need to do to prepare: This is a non-invasive feature. The tenant admin will not see any changes unless the admin uses the feature. This rollout will happen automatically by the specified dates with no admin action required before the rollout. Review your current configuration to assess the impact on your organization. You may want to notify your users about this change and update any relevant documentation. Learn more: Create and deploy a data loss prevention policy | Microsoft Learn

What changed

Between archive captures, newest first

The archive supplies one version of this notice.

Linked documentation

Microsoft pages the notice links to

The notice links to no Microsoft Learn or Support page that this installation reads.

No related evidence found in this installation's recent collection. This does not establish that no announcement exists.

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.
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 26 Oct 07:24 UTC · 272 of 272 readable · 270 fully read · documentation 469/469 current