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

Service

Microsoft Purview

Published

Apr 24, 2025

Tag

New feature
Admin impact

Platforms

Web

Summary

Microsoft Purview will soon allow DLP admins to rename existing policies and rules without recreating them. The feature will roll out in stages from July to October 2025 and will be supported across major workloads. A new editable field, DisplayName, will be introduced. No admin action is required before the rollout.

More information

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:

admin controls

Editing a rule to rename it:

admin controls

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