Back to latest version

MC1143996 - Microsoft Purview compliance portal: Data Loss Prevention - Upcoming Change to DLP Alert Settings

Message Center

Metadata at Aug 29, 2025

Published

Aug 29, 2025

Service

Microsoft Purview

Tag

Admin impact
Retirement

Metadata changes

Tags
Admin impact, Retirement, Updated messageAdmin impact, Retirement

Body changes

removed textadded text

Updated September 24, 2025: We have updated the content. Thank you for your patience.

Introduction

We have identified that some tenants are using DLP rules in whichTo improve consistency between portal and PowerShell configurations, Microsoft Purview will update how alert generation has been enabled using the Microsoft Purview portal policy configuration page but the corresponding Alert Policy (Protection Alert) was disabled or deleted using "Set-ProtectionAlert" PowerShell cmdlet (Learn more). Due to this theis handled for Data Loss Prevention (DLP) rules. This change ensures that alert generation gets turned off for the associated DLP rule – even though the alert it appears active on Purview portal policy configuration UX.

If you wish to continue receive alerts for these rules, please take one of the following actions:

  • Open the rulesettings in the Purview portal, make any update, and save the configuration.
  • Use the PowerShell cmdlets to re-enable alert generation for the rule. (Learn more)
portal accurately reflect rule configurations made via PowerShell.

When this will happen

This change will begin rolling out on September 26, 2025.

How this affects your organization

To ensure consistency we will update theWe’ve identified that a few tenants have one or more DLP rule to remove Generate Alert as an action. Since alerts were disabled using Protection Alert PowerShell cmdlets there will be no change inrules with alert generation enabled in the Microsoft Purview portal, but the corresponding alert action was disabled or removed using PowerShell cmdlets.

To align portal behavior with PowerShell configurations, Microsoft will automatically disable the alert generation toggle in the Purview portal for correspondingthese rules. The rules will remain active and continue to enforce DLP rule and policy. We are actions, but alerts will no longer be generated unless reconfigured.

This change does not impact the enforcement of DLP policies—only ensuring there is consistency between DLP rules (with Generate Alert as an action) and their corresponding Alert policies (protection alert)the alert generation behavior.

What you can do to prepare:prepare

IfNo admin action is required unless you wishwant to receivecontinue receiving alerts for these rules, please take one of the following actions:affected rules. To re-enable alert generation:

  • Open the rule in the Purview portal, make any update, and save the configuration.
  • Use the PowerShell cmdlet “Set-DlpComplianceRule” to re-enable alert generation for the rule. (You can refer to the following cmdlet documentation for guidance:

    Compliance considerations

    Compliance Area Impact
    Alters how existing customer data is processed, stored, or accessed No affect.Alert for affected DLP rule actions will no longer be generated unless explicitly re-enabled.
    Modifies Purview capabilities No affect.Alert generation for DLP rules will be disabled in the portal if previously removed via PowerShell.
    Alters how admins can monitor, report on, or demonstrate compliance activities No affect.Admins may see fewer alerts in Purview reporting unless rules are reconfigured.
    Includes an admin control Admins can re-enable alert generation if they wish to via portal or Set-"DlpComplianceRule" PowerShell cmdlet.PowerShell.
    Allows user to enable/disable the feature Admins can re-enabletoggle alert generation if they wish to via portal or Set-"DlpComplianceRule" PowerShell cmdlet.per rule.