Skip to main content
🦉
Message CenterMicrosoft 365 Updates
HomePermissionsTenant FinderPortfolio
🦉
M365 Message Centerby Cengiz YILMAZ

Track the latest updates, features, and announcements for Microsoft 365 services. Comprehensive archive of service updates and important changes.

Quick Links

HomePermissionsTenant FinderPortfolio

Connect

© 2026 M365 Message Center. Created with ❤️ by Cengiz YILMAZ

Data sourced from Microsoft 365 Message Center • Not affiliated with Microsoft

  1. Home
  2. /
  3. MC1143996

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

Plan for Change

Message ID

MC1143996
View in Admin Center

Services

Microsoft Purview

Summary

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.

Details

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:
    • Set-ProtectionAlert
    • Set-DlpComplianceRule

    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.

    Timeline

    📅
    Published
    Aug 29, 2025
    Message published to Message Center
    ✏️
    Updated
    Aug 29, 2025
    Message content updated
    🏁
    End Date
    Nov 14, 2025
    Message timeline ends

    Tags

    #Admin impact#Retirement

    Category

    📋Plan for Change

    Related Messages

    Similar updates

    MC1129711●

    Microsoft Purview | ​Retirement of the classic eDiscovery (Premium) experience

    Aug 5, 2025
    MC1217649●

    Endpoint DLP-sensitive data alerting retiring in Defender; use Purview DLP

    Jan 14, 2026
    MC1151234

    Microsoft Purview DLP and Edge for Business: Automated blocking of unmanaged GenAI apps in unprotected browsers

    Sep 10, 2025
    MC1148528●

    Microsoft Purview compliance portal: Data Loss Prevention: User based alert aggregation

    Sep 5, 2025
    MC1143302

    Insider Risk Management- Multi selectable DLP policies as an IRM triggering event

    Aug 27, 2025