Back to latest version
You're viewing a historical snapshot from Aug 29, 2025. This is not the latest version.

Metadata at Aug 29, 2025

Published

Aug 29, 2025

Service

Microsoft Purview

Tag

Admin impact
Retirement

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

Message Center

What changed since this version

removed textadded text

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

Introduction

To improve consistency between portal and PowerShell configurations,We have identified that some tenants are using DLP rules in which alert generation has been enabled using the Microsoft Purview will update howportal policy configuration page but the corresponding Alert Policy (Protection Alert) was disabled or deleted using "Set-ProtectionAlert" PowerShell cmdlet (Learn more). Due to this the alert generation is handledgets turned off for Data Loss Prevention (DLP) rules. This change ensures thatthe associated DLP rule – even though the alert settingsit 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 rule in the portal accurately reflect rule configurations made via PowerShell.

    Purview portal, make any update, and save the configuration.
  • Use the PowerShell cmdlets to re-enable alert generation for the rule. (Learn more)

When this will happen

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

How this affects your organization

We’ve identified that a few tenants have one or moreTo ensure consistency we will update the DLP rule to remove Generate Alert as an action. Since alerts were disabled using Protection Alert PowerShell cmdlets there will be no change in alert generation behavior for corresponding DLP rule and policy. We are only ensuring there is consistency between DLP rules with alert generation enabled in the Microsoft Purview portal, but the(with Generate Alert as an action) and their 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 these rules. The rules will remain active and continue to enforce DLP actions, but alerts will no longer be generated unless reconfigured.

This change does not impact the enforcement of DLP policies—only the alert generation behavior.Alert policies (protection alert)

What you can do to prepareprepare:

No admin action is required unlessIf you wantwish to continue receivingreceive alerts for affected rules. To re-enable alert generation:these rules, please take one of the following actions:

  • 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 Alert for affected DLP rule actions will no longer be generated unless explicitly re-enabled.No affect.
    Modifies Purview capabilities Alert generation for DLP rules will be disabled in the portal if previously removed via PowerShell.No affect.
    Alters how admins can monitor, report on, or demonstrate compliance activities Admins may see fewer alerts in Purview reporting unless rules are reconfigured.No affect.
    Includes an admin control Admins can re-enable alert generation if they wish to via portal or PowerShell.Set-"DlpComplianceRule" PowerShell cmdlet.
    Allows user to enable/disable the feature Admins can togglere-enable alert generation per rule.if they wish to via portal or Set-"DlpComplianceRule" PowerShell cmdlet.

    Snapshot from Aug 29, 2025

    Introduction

    To improve consistency between portal and PowerShell configurations, Microsoft Purview will update how alert generation is handled for Data Loss Prevention (DLP) rules. This change ensures that alert settings in the 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

    We’ve identified that a few tenants have one or more DLP rules 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 these rules. The rules will remain active and continue to enforce DLP actions, but alerts will no longer be generated unless reconfigured.

    This change does not impact the enforcement of DLP policies—only the alert generation behavior.

    What you can do to prepare

    No admin action is required unless you want to continue receiving alerts for affected rules. To re-enable alert generation:

    • Open the rule in the Purview portal, make any update, and save the configuration.
    • Use PowerShell 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 Alert for affected DLP rule actions will no longer be generated unless explicitly re-enabled.
      Modifies Purview capabilities 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 Admins may see fewer alerts in Purview reporting unless rules are reconfigured.
      Includes an admin control Admins can re-enable alert generation via portal or PowerShell.
      Allows user to enable/disable the feature Admins can toggle alert generation per rule.