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

1. 24 Sep 2025
   • Tags Admin impact, Retirement → Updated message, Admin impact, Retirement

   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 how alert generation is handled for Data Loss Prevention (DLP) rules. This change ensures that alert settings inportal 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 portal accurately reflect rule configurations made via PowerShell. When this will happen This change will begin rolling outalert generation gets turned off for the associated DLP rule – even though the alert it appears active on September 26, 2025. How this affects your organization We’ve identified that a few tenants havePurview portal policy configuration UX. If you wish to continue receive alerts for these rules, please take one or more DLP rules with alert generation enabled of the following actions: Open the rule in the Microsoft Purview portal, butmake any update, and save the corresponding alert action was disabled or removed using PowerShell cmdlets. To align portal behavior with PowerShell configurations, Microsoftconfiguration. Use the PowerShell cmdlets to re-enable alert generation for the rule. (Learn more) When this will happen This change will automatically disable the alert generation toggle in the Purview portal for these rules. The rulesbegin rolling out on September 26, 2025. How this affects your organization To ensure consistency we will remain active and continueupdate the DLP rule to enforce DLP actions, butremove Generate Alert as an action. Since alerts were disabled using Protection Alert PowerShell cmdlets there will be no longer be generated unless reconfigured. This change does not impact the enforcement ofchange in alert generation behavior for corresponding DLP rule and policy. We are only ensuring there is consistency between DLP policies—only the alert generation behavior.rules (with Generate Alert as an action) and their corresponding Alert policies (protection alert) What you can do to prepare No admin action is required unless prepare: If you wantwish to continue receiving receive 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:Set-ProtectionAlert Set-DlpComplianceRule (Learn more). 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.

2. 29 Aug 2025 · first version seen

• Learn moreNot read yet
• Learn moreNot read yet

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

• Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
• 2 linked pages have not been read yet.