Microsoft Purview Data Loss Prevention | Enforcement plane rename from Entra to Application

Originally posted by Microsoft Jan 18, 2026 Uncategorized 0 Comments

Microsoft Purview DLP is renaming the Enforcement plane from “Entra” to “Application” starting mid-January 2026, with no functional or user impact. Admins should update scripts and documentation accordingly. New audit logs will reflect “Application,” while existing logs keep “Entra.” No compliance issues identified.

We are updating the Enforcement plane terminology in Microsoft Purview Data Loss Prevention (DLP) and Collection Policies. The Enforcement plane identifies the application or environment where a DLP policy is evaluated and enforced, indicating where user actions are inspected and where policy outcomes—such as blocking, replacing, or auditing—are applied. Because policy enforcement happens on the application where activity occurs, we are renaming the Enforcement plane from Entra to Application. This update aligns terminology with how policies function and clarifies that enforcement applies across both AI and non‑AI applications.

When this will happen:

General Availability (Worldwide): Rollout begins mid-January 2026 and is expected to complete by mid-February 2026.

How this affects your organization:

Who is affected:

• Admins who manage Microsoft Purview DLP or Collection Policies
• Organizations using Purview audit logs or DLP cmdlets

What will happen:

• The Enforcement plane value will change from Entra to Application across product experiences.
• New audit logs will show the updated Application value; existing logs will retain the prior Entra value.


View image in new tab

• There are no functional changes to DLP policy behavior.
• There is no user impact.

What you can do to prepare:

• No action is required for user experience or policy behavior.
• If you use cmdlets, update scripts to reference Application instead of Entra.
• Update internal documentation or training materials that reference the previous terminology.

Compliance considerations:

No compliance considerations identified, review as appropriate for your organization.

Message ID: MC1218710