RM576863 - Microsoft Power Platform governance and administration: Security and compliance - Prevent sending sensitive data to Purview audit logs

Microsoft 365 Roadmap

Summary

To help prevent leaking sensitive customer data from Dataverse audit logs, all customer data is removed before these audit events are sent to Purview activity logging. Examples of sensitive customer data include financial information, medical and health data, and personally identifiable information.

Discussionpowered by zap.ms

Published

Oct 16, 2026

Status

Launched

Release

General Availability

Platforms

Web

Service

Microsoft Power Platform governance and administration

Tag

Launched
General Availability
Worldwide (Standard Multi-Tenant)

Cloud

Worldwide (Standard Multi-Tenant)

Description

To help prevent leaking sensitive customer data from Dataverse audit logs, all customer data is removed before these audit events are sent to Purview activity logging. Examples of sensitive customer data include financial information, medical and health data, and personally identifiable information.

In Dataverse audit logs, create and update events—including a column’s before-and-after values—are captured. These values remain in Dataverse audit logs, but aren’t sent to Purview activity logging.

Business Value:

This feature restricts customer business data in Dataverse audit logs from being sent to Purview auditing streams. This helps ensure compliance and reduces the risk of leaking sensitive customer data.

Enabled for:

Enabled by admins/makers/marketers for end users

More info: https://learn.microsoft.com/en-us/power-platform/important-changes-coming#removal-of-before-and-after-field-change-values-in-audit-events-sent-to-microsoft-purview

GA date: June CY2026