Power Platform – Information regarding removal of field-level value changes in audit events sent to Microsoft Purview

Starting on May 1, 2026, Dataverse will no longer include before-and-after field change values in the audit events that are sent to Microsoft Purview. This change strengthens data protection by reducing the risk of exposing sensitive business or personal information through downstream monitoring or analytics systems that consume Purview audit data. How does this affect me? After May 1, 2026, new Dataverse audit events will no longer include before-and-after field change values. Existing Dataverse audit event data in Purview will remain the same. Purview continues receiving audit event metadata, but field-level value changes will no longer be included. If you have existing monitoring, alerting, or reporting solutions that depend on before-and-after field change values within Purview audit events, those solutions will stop working once this deprecation takes effect. Examples include: Rules that compare old/new values for anomaly detection. Data pipelines that analyze field-level deltas. Custom compliance checks running in Purview. What action do I need to take? Update your monitoring or downstream workflows to retrieve detailed field-level audit information directly from Dataverse, not from Purview. Dataverse continues to store and expose before-and-after field changes through its native audit APIs and tables. No changes are required if your solution uses Dataverse audit logs as the source of truth. Communicate as appropriate with your Power Platform administrators. If you would like more information about this deprecation, please visit Important changes (deprecations) coming in Power Platform. Message ID: MC1239891

The post Power Platform – Information regarding removal of field-level value changes in audit events sent to Microsoft Purview appeared first on M365 Admin.