MC1189685 Low
Power Platform - Improved security for column-level audit events in Microsoft Purview
Summary AI-generated
Audit events for columns with security restrictions in Microsoft Purview will filter before-and-after values in logs starting December 1, 2025, enhancing sensitive data protection.
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- MC1239891 Power Platform - Information regarding removal of field-level value changes in audit events sent to Microsoft Purview
- MC1473155 (Updated) Microsoft Purview: permissions audit log improvements
- MC1486027 Microsoft Power Platform governance and administration - Secure Dataverse record with column-based filtering
- 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
- MC1191257 (Updated) New Microsoft Purview data security posture management experience
Original post from Microsoft
We are announcing enhancements to the handling of audit events that capture, create, and update activities on columns protected by column-level security in Microsoft Purview. These enhancements will take effect on December 1, 2025.
How does this affect me?
Currently, certain audit events may include details that could potentially reveal sensitive information when columns with security restrictions were created or updated. Following these enhancements, these specific events will now be protected, and the before-and-after column values will be filtered in activity logs. You may notice changes in the granularity of audit event data for operations involving column-level security.
What action do I need to take?
This message is for awareness, and no action is required.
For more information about Column-level security, please visit Column-level security to control access.
How does this affect me?
Currently, certain audit events may include details that could potentially reveal sensitive information when columns with security restrictions were created or updated. Following these enhancements, these specific events will now be protected, and the before-and-after column values will be filtered in activity logs. You may notice changes in the granularity of audit event data for operations involving column-level security.
What action do I need to take?
This message is for awareness, and no action is required.
For more information about Column-level security, please visit Column-level security to control access.