Microsoft Power Platform governance and administration: Security and compliance - Prevent sending sensitive data to Purview audit logs Beta
Data as of 2 hours ago (26 October 2026)
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
Change history
Added to the roadmap 16 October 2026. Tracked here since 16 October 2026. Earliest target we recorded: June 2026 (since tracked — Microsoft may have moved it before we started watching).
Nothing has changed on this item since tracking began on 16 October 2026. Changes appear here as Microsoft updates the feed.