MC1387575 - Microsoft Purview | Endpoint Data Loss Prevention: Scope Just-in-time audit by user or group

Message Center

Summary

Microsoft Purview Endpoint Data Loss Prevention now requires admins to explicitly configure which users or groups are audited under Just-in-time protection, enhancing control and reducing unnecessary audit noise. The rollout begins mid-September 2026, with updated settings to manage audit scope and activity logging in Activity explorer.

Last Updated

Jul 7, 2026

Published Jun 11, 2026

View version history

Service

Microsoft Purview

Tag

Updated message
New feature
Admin impact

Platforms

Web

More information

Updated July 7, 2026: We have updated the timeline. Thank you for your patience. 

What and Why:

Admins can now scope which users and groups have their activities audited when Just-in-time protection is enabled in Microsoft Purview Endpoint Data Loss Prevention.

Previously, when Just-in-time protection was turned on, user activities were logged automatically for users who were not targeted by policies. With this update, audit logging must be explicitly configured so that only users or groups included in the audit scope have their activities logged. This change gives organizations greater control over audit signal collection and helps reduce unnecessary audit noise.

This message is associated with Microsoft 365 Roadmap ID 562991.

Rollout Schedule:

Global: We will begin rolling out in mid-September 2026 (previously early July) and expect to complete by end of September 2026 (previously early July).

Impact on Your Organization:

Who is affected: Admins managing Microsoft Purview Endpoint Data Loss Prevention and Just-in-time protection settings.

Platforms/Services:

  • Microsoft Purview
  • Endpoint Data Loss Prevention
  • Activity explorer.

What will happen:

  • Just-in-time audit behavior is now managed through the Audit covered user activities setting under Settings > Data loss prevention > Just-in-time protection. Under the Devices tab, turn on Audit covered user activities.
  • Screenshot: Just-in-time protection settings with Audit covered user activities turned on:

    user settings

  • Users included in audit scope will not see enforcement actions, and their activities will be recorded in Activity explorer.
  • Users included in block scope will be prevented from completing actions while files are evaluated for sensitive information. Their activities are recorded in Activity explorer.
  • Users not included in audit or block scope will not have activities covered by Just-in-time protection recorded.
  • Audited activities include printing, transfers to removable media or network shares, copying or moving files using Remote Desktop Protocol or an unapproved Bluetooth app, and uploading files to a restricted cloud service domain.

Action Required / Recommendations:

  • Deploy anti-malware client version 4.18.26060 or later before enabling this feature.
  • Review your existing Just-in-time configuration to identify users currently generating audit events.
  • Explicitly add all users or groups that should continue generating Just-in-time audit events to the audit scope.
  • Validate your configuration to ensure expected activities appear in Activity explorer.

Learn more: Get started with Microsoft Purview Data Loss Prevention just-in-time protection | Microsoft Learn

Compliance considerations:

Compliance area Impact
Audit logging capabilities Audit logging behavior changes from automatic to explicitly scoped, affecting which user activities are recorded for Just-in-time protection.
Admin compliance monitoring and reporting Admins must configure audit scope to maintain expected visibility of user activity in Activity explorer.
Purview reporting and compliance workflows The change alters how Just-in-time audit data is collected and reviewed for compliance and investigation workflows.
Admin controls and group-based configuration The feature introduces additional admin configuration controls for scoping audit behavior, which may be applied using user or group selection.

Version history

2 versions tracked

Updated 1 time since Jun 11, 2026. Microsoft Message Center only ever shows the current version; this archive preserves the history.

Compare any two versions

From
To
  1. Jul 7, 2026 · 06:00 PMLatest · v2

    Changed: Body, Tags, End date

  2. Jun 11, 2026 · 05:25 PMOriginal · v1

    Changed: Initial version