MC1239891 Medium
Power Platform - Information regarding removal of field-level value changes in audit events sent to Microsoft Purview
Summary AI-generated
From May 1, 2026, Dataverse audit events in Purview will no longer include before-and-after field change values, improving data protection but impacting solutions that depend on this data.
Suggested actions AI-generated
- Update monitoring and workflows to get field-level changes directly from Dataverse
- Inform Power Platform admins
- Review dependencies on Purview audit data
Written by Azure OpenAI (gpt-4.1) from the text of the post below. It can be incomplete or wrong; the original post is authoritative.
Similar posts
Search for more like this- MC1189685 Power Platform - Improved security for column-level audit events in Microsoft Purview
- MC1259827 Microsoft Purview: Data Security Investigations – analyze files tied to audit log activities
- MC1181768 Microsoft Purview: eDiscovery admin content access restrictions when not in compliance with Entra policies
- MC1473155 Microsoft Purview: permissions audit log improvements
- MC1215681 Microsoft Dataverse - Ending Support for configuring Table‑Level Deleted-Records Keeping
- MC1162273 Microsoft Purview | eDiscovery - Metadata field enhancements in process reporting
Original post from Microsoft
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:
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.
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.