Tenant announcements

(Updated) Microsoft Purview: permissions audit log improvements

MC1473155

All Microsoft 365 Message Center posts · Daily summary

About this page These posts come from a tenant in West Europe and are shown as a reference. Day-by-day digest: MC Summary. Linked to the roadmap via Roadmap ID when Microsoft names one. Items are kept for 12 months. Always check Message Center in your own environment for what applies to you.
MC1473155
Show roadmap information (1)
#569363Rolling out
Microsoft Purview: Permissions audit log improvements
Rollout startSeptember 2026

Added to roadmap: 17 aug 2026 | Last modified: 28 sep 2026

Improving permission checks when users access the Microsoft Purview portal. Enhanced audit logs will provide clearer visibility into role and scoped-role access decisions, helping administrators troubleshoot access issues and monitor authorization outcomes.

Updated October 13, 2026: We have updated the content. Thank you for your patience.

What and why

To improve transparency and troubleshooting for Microsoft Purview role-based access control (RBAC), we are enhancing audit logging for permission checks performed in the Microsoft Purview portal. These new audit records will provide administrators with clearer visibility into role and scoped-role authorization decisions, helping them investigate access issues and better understand how access evaluations are performed.

This message is associated with Microsoft 365 Roadmap ID 569363.

Rollout schedule

  • General Availability (Worldwide): Beginning in late September 2026 and expected to complete by late October 2026

Impact on your organization

Who is affected

Platforms and services

  • Microsoft Purview portal
  • Microsoft Purview Audit

What will happen

  • New audit records will be generated when access checks are performed in the Microsoft Purview portal.
  • Two new audit operations will be available:
    • CheckUsersInRoles
    • CheckUserInRolesWithScopes
  • Administrators will be able to review these audit records as part of SecurityComplianceRBAC audit activities.
  • The enhancement is enabled by default and requires no configuration.
  • Audit records will only be generated for access checks that occur after the feature is deployed.
  • No historical or retroactive audit records will be created for prior access checks.
  • There is no impact for organizations.
  • Supported permission-assignment and role-group change audit records will include the ClientPortal field within PreExecutionMessage, helping administrators distinguish changes initiated from Microsoft Purview and Microsoft Defender.
    • Supported activities for portal attribution
      • Permission assignments: Granting, updating, or removing permission assignments.
      • Role groups: Creating, updating, or deleting role groups.
  • Expected ClientPortal values:
    • Microsoft Purview portal: "ClientPortal": "Microsoft Purview"
    • Microsoft Defender portal: "ClientPortal": "Microsoft Defender"
    • Missing or unrecognized X-ClientPage value: "ClientPortal": "Unknown"

RBAC audit-CheckUserInRolesWithScopes:

RBAC audit-checkusersinroles:

Action required and recommendations

No action is required. We recommend that administrators:

  • Review internal monitoring and audit procedures to determine whether the new audit activities should be included in access investigations.
  • Inform compliance and security teams about the availability of the new audit operations.
  • Update any internal documentation or reporting processes that reference Microsoft Purview RBAC audit data.

Learn more

Compliance considerations

QuestionAnswerDoes the change modify, interrupt, or disable audit logging capabilities?Yes. The change enhances audit logging capabilities by adding two new audit operations.Does the change alter how admins can monitor, report on, or demonstrate compliance activities?Yes. Administrators gain additional audit visibility into RBAC access evaluation outcomes, improving monitoring and troubleshooting capabilities.