(Updated) Microsoft Purview | Endpoint Data Loss Prevention: Policy sync and device health AI skill
Versions captured by this deployment. Earlier versions and notices may be missing; first observed is not first published.
Rollout
- Ends
- 31 Dec 2026
- Roadmap
- 562016
- Platforms
- Web
Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".
- Microsoft's start date
- 5 Jun 2026
- Last changed by Microsoft
- 13 Oct 2026
- First seen here
- 19 Oct 2026
- Versions seen
- 1
What the notice says
Microsoft's text, with its sections, lists and tables; source markup removedUpdated October 13, 2026: We have decided not to move forward with this change at this time. We will communicate via Message center when we are ready to proceed. We apologize for any inconvenience.
What and Why
We are introducing Policy Sync and Device Health AI skills for Microsoft Purview Endpoint Data Loss Prevention. These AI-powered capabilities provide real-time visibility into policy deployment across devices and help admins quickly identify and resolve sync issues. By using AI to surface root causes and recommend actions, this feature improves troubleshooting efficiency and increases confidence that policies are enforced consistently across devices. This aligns with our enterprise-ready AI approach by delivering intelligent insights within Microsoft Purview.
This message is associated with Microsoft 365 Roadmap ID 562016.
Rollout Schedule
- Public Preview: We will communicate via Message center when we are ready to proceed.
- General Availability (Worldwide): We will communicate via Message center when we are ready to proceed.
Impact on Your Organization
Who is affected
- Admins managing Endpoint Data Loss Prevention policies in Microsoft Purview
Platforms/Services
- Microsoft Purview compliance portal
- Endpoint DLP
- Security Copilot
What will happen
- Admins will see new AI-powered insights for policy sync status and device health:
- Real-time visibility into DLP policy deployment across endpoints will be available:
- Impacted devices and sync failures will be identified automatically:
- Root cause explanations and recommended remediation actions will be provided:
- The experience will be available within DLP policy and device views in Microsoft Purview.
- The feature requires Security Copilot capabilities to be available in the tenant.
Action Required/Recommendations
No immediate action is required.
To prepare for this feature:
- Ensure that Security Copilot is enabled in your organization.
- Confirm that Security Compute Units are provisioned to support AI experiences.
- Verify that admins have appropriate permissions to access DLP policies and device views in Microsoft Purview.
- Review the DLP portal to familiarize your team with where the feature will appear.
- Communicate this update to your security and compliance administrators.
Compliance considerations
| Question | Answer |
|---|---|
| Does the change introduce or significantly modify AI or machine learning capabilities that interact with or provide access to customer data? | Yes. The change introduces AI-powered skills that analyze DLP policy sync status and device health, identify impacted devices, and provide root cause insights along with recommended remediation actions. |
| Does the change alter how admins can monitor, report on, or demonstrate compliance activities? | Yes. The change adds new AI-driven insights and visibility into DLP policy deployment and device readiness within Microsoft Purview, enhancing how admins monitor and assess compliance activities. |
What changed
Between the versions this installation saw, newest firstThis installation has seen one version of this notice, first on 19 Oct 2026. Later changes will show here.
Linked documentation
Microsoft pages the notice links toThe notice links to no Microsoft Learn or Support page that this installation reads.
Not confirmed here
What this page cannot tell you- Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
- Versions before 19 Oct 2026: this installation first saw the notice after Microsoft posted it.