<p>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.</p> <p>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.</p> <p>Business Value:</p> <p>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.</p> <p>Enabled for:</p> <p>Enabled by admins/makers/marketers for end users</p>
Roadmap › 576863
Microsoft Power Platform governance and administration: Security and compliance - Prevent sending sensitive data to Purview audit logs
- General availability
- 2026-06
- Preview
- —
- Added
- 16 Oct 2026
- Last modified
- 16 Oct 2026 19:09 UTC
- First archived
- 16 Oct 2026
- Release rings
- General Availability
- Clouds
- Worldwide (Standard Multi-Tenant)
Description
More information
© Microsoft — from the Microsoft 365 Roadmap · View on microsoft.com · Content notice