Posted by Data loss prevention moves to the network layer
Status: Preview – documented July 2026
Purview now integrates with Microsoft Entra Global Secure Access so that organizations can intercept and inspect text and AI interactions at the network layer, enforce restrictive actions based on DLP policy, and detect risky user activity through Insider Risk Management.
The business significance is that enforcement no longer depends on the destination being a managed Microsoft application. For organizations whose principal exposure is employees pasting confidential material into unsanctioned AI services, this is the first control point that sits in the path of the traffic rather than on the endpoint alone.
Data loss prevention policies and sensitivity labeling extend to non-Microsoft connected applications
Status: Preview – documented August 2026
Organizations can create DLP policies that protect sensitive data at rest in non-Microsoft connected applications such as Box and Google Workspace. As you might know, this type of functionality is provided using Microsoft Defender for Cloud Apps connectors and the Microsoft 365 classification engine. A single classification model and a single policy authority can now cover both Microsoft and (selected) non-Microsoft.
Status: Preview – documented August 2026
Alongside the DLP change, auto-labeling policies can now protect sensitive data at rest in non-Microsoft connected apps including Box and Google Workspace, again using Defender for Cloud Apps and the Microsoft 365 classification engine. This matters more than it first appears. Sensitivity labels offer encryption, work in DLP conditions and determine access decisions that AI tools inherit.
Auto-labeling capacity to 500.000 files per day
Status: Capacity increase announced in the Microsoft Security Blog, 27 August 2026
Auto-labeling (E5 or E7) is one of the best ways (when done correctly) to ensure that documents get sensitivity labels applied, which in turn make Microsoft 365 Copilot more secure. The initial limit for auto-labeling (SharePoint and OneDrive) is set to 100.000 files per day. But this will increase to 500.000 files per day. As we all know, most tenants hold many, many files (tens of millions is no exception) so this increase is significant.
Simulation mode and policy insights
Status: New – documented August 2026
Simulation mode is crucial for any activity that will influence the workings with information. DLP and auto labeling both have simulation modes, and I highly recommend using these. As of August 2026, a new Insights tab in the policy details panel gives an at-a-glance view of policy performance, with content that differs depending on whether the policy is in simulation or enforcement mode. This tab only appears for Microsoft 365 content.
Exchange Online DLP classification failures
Status: Preview – documented July 2026
Exchange Online DLP policies now detect classification failures caused by timeouts, throttling and other scanning errors. Classification is an integral part of many of Purview functions/solutions and it needs to work correctly. We don’t want to get overburdened by false positives, for instance when the message could not be scanned and is flagged as an issue. So now, administrators can enable classification-failure detection and use the DocumentScanFailures condition to apply different protection actions.