Summary
Starting September 26, 2025, Microsoft Purview will update DLP alert settings to remove "Generate Alert" from rules where corresponding Protection Alerts were disabled via PowerShell. To keep receiving alerts, admins must update and save rules in the portal or re-enable alerts using the Set-DlpComplianceRule cmdlet.
Details
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 which 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 the 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 rule 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)
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 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 Generate Alert as an action) and their corresponding Alert policies (protection alert)
What you can do to prepare:
If you wish to receive alerts for 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. (Learn more).
Compliance considerations
| Compliance Area | Impact |
|---|---|
| Alters how existing customer data is processed, stored, or accessed | No affect. |
| Modifies Purview capabilities | No affect. |
| Alters how admins can monitor, report on, or demonstrate compliance activities | No affect. |
| Includes an admin control | Admins can re-enable alert generation if they wish to via portal or Set-"DlpComplianceRule" PowerShell cmdlet. |
| Allows user to enable/disable the feature | Admins can re-enable alert generation if they wish to via portal or Set-"DlpComplianceRule" PowerShell cmdlet. |
Change History
September 24, 2025 at 10:30 PM
Updated
Title
Previous
Microsoft Purview compliance portal: Data Loss Prevention - Upcoming Change to DLP Alert Settings
New
(Updated) Microsoft Purview compliance portal: Data Loss Prevention - Upcoming Change to DLP Alert Settings
Summary
Previous
Starting September 26, 2025, Microsoft Purview will align DLP alert settings between the portal and PowerShell by disabling alert generation in the portal for rules where PowerShell disabled it. DLP enforcement continues unaffected. Admins must re-enable alerts via portal or PowerShell to keep receiving them.
New
Starting September 26, 2025, Microsoft Purview will update DLP alert settings to remove "Generate Alert" from rules where corresponding Protection Alerts were disabled via PowerShell. To keep receiving alerts, admins must update and save rules in the portal or re-enable alerts using the Set-DlpComplianceRule cmdlet.
Last Updated Date
Previous
2025-08-29T00:31:08.690Z
New
2025-09-24T20:32:25.427Z
Tags
Previous
Admin impact,Retirement
New
Updated message,Admin impact,Retirement
Body Content
Previous
<p><b>Introduction</b></p><p>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.</p><p><b>When this will happen</b></p><p>This change will begin rolling out on September 26, 2025.</p><p><b>How this affects your organization</b></p><p>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.</p><p>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 <b>alerts will no longer be generated unless reconfigured</b>.</p><p>This change does <b>not </b>impact the enforcement of DLP policies—only the alert generation behavior.</p><p><b>What you can do to prepare</b></p><p>No admin action is required unless you want to continue receiving alerts for affected rules. To re-enable alert generation:</p><ul><li>Open the rule in the Purview portal, make any update, and save the configuration.</li><li>Use PowerShell to re-enable alert generation for the rule. You can refer to the following cmdlet documentation for guidance:<ul><li><a href="https://learn.microsoft.com/powershell/module/exchangepowershell/set-protectionalert?view=exchange-ps" target="_blank">Set-ProtectionAlert</a>
</li><li><a href="https://learn.microsoft.com/powershell/module/exchangepowershell/set-dlpcompliancerule?view=exchange-ps" target="_blank">Set-DlpComplianceRule</a></li></ul></li></ul><p></p><ul></ul><p></p><p><b>Compliance considerations</b></p><table border="1" cellpadding="6" cellspacing="0">
<tbody><tr>
<th>Compliance Area</th>
<th>Impact</th>
</tr>
<tr>
<td>Alters how existing customer data is processed, stored, or accessed</td>
<td>Alert for affected DLP rule actions will no longer be generated unless explicitly re-enabled.</td>
</tr>
<tr>
<td>Modifies Purview capabilities</td>
<td>Alert generation for DLP rules will be disabled in the portal if previously removed via PowerShell.</td>
</tr>
<tr>
<td>Alters how admins can monitor, report on, or demonstrate compliance activities</td>
<td>Admins may see fewer alerts in Purview reporting unless rules are reconfigured.</td>
</tr>
<tr>
<td>Includes an admin control</td>
<td>Admins can re-enable alert generation via portal or PowerShell.</td>
</tr>
<tr>
<td>Allows user to enable/disable the feature</td>
<td>Admins can toggle alert generation per rule.</td>
</tr>
</tbody></table>
New
<p>Updated September 24, 2025: We have updated the content. Thank you for your patience.</p><p><b>Introduction</b></p><p>We have identified that some tenants are using DLP rules in which 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 <b>"Set-ProtectionAlert"</b> PowerShell cmdlet (<a href="https://learn.microsoft.com/powershell/module/exchangepowershell/set-protectionalert?view=exchange-ps" target="_blank">Learn more</a>). Due to this the alert generation gets turned off for the associated DLP rule – even though the alert it appears active on Purview portal policy configuration UX.</p><p>If you wish to continue receive alerts for these rules, please take one of the following actions:
</p><ul><li>Open the rule in the Purview portal, make any update, and save the configuration.
</li><li>Use the PowerShell cmdlets to re-enable alert generation for the rule. (<a href="https://learn.microsoft.com/powershell/module/exchangepowershell/set-dlpcompliancerule?view=exchange-ps" target="_blank">Learn more</a>)</li></ul><p><b>When this will happen</b></p><p>This change will begin rolling out on September 26, 2025.</p><p><b>How this affects your organization</b></p><p>To 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 Generate Alert as an action) and their corresponding Alert policies (protection alert)</p><p><b>What you can do to prepare:</b></p><p>If you wish to receive alerts for these rules, please take one of the following actions:</p><ul><li> Open the rule in the Purview portal, make any update, and save the configuration.</li><li>Use the PowerShell cmdlet “Set-DlpComplianceRule” to re-enable alert generation for the rule. (<a href="https://learn.microsoft.com/powershell/module/exchangepowershell/set-dlpcompliancerule?view=exchange-ps" target="_blank">Learn more</a>).</li></ul><p></p><ul></ul><p></p><p><b>Compliance considerations</b></p><table border="1" cellpadding="6" cellspacing="0">
<tbody><tr>
<th>Compliance Area</th>
<th>Impact</th>
</tr>
<tr>
<td>Alters how existing customer data is processed, stored, or accessed</td>
<td>No affect.</td></tr><tr><td>Modifies Purview capabilities</td>
<td>No affect.</td>
</tr>
<tr>
<td>Alters how admins can monitor, report on, or demonstrate compliance activities</td>
<td>No affect.</td>
</tr>
<tr>
<td>Includes an admin control</td>
<td>Admins can re-enable alert generation if they wish to via portal or Set-"DlpComplianceRule" PowerShell cmdlet.</td>
</tr>
<tr>
<td>Allows user to enable/disable the feature</td>
<td>Admins can re-enable alert generation if they wish to via portal or Set-"DlpComplianceRule" PowerShell cmdlet.</td>
</tr>
</tbody></table>
Never Miss a Microsoft 365 Update
Join thousands of IT professionals who rely on DeltaPulse for real-time Microsoft 365 change intelligence, automated notifications, and community insights.