Microsoft Viva Engage (Yammer): Enhanced audit log schema

Microsoft Viva Engage (Yammer) is updating its audit log schema to improve transparency and accountability by including unique identifiers for both the user performing an action and the user/object affected, along with a parameter for capturing old and new values of modified fields. These changes will be available for users with an E3 license and will roll out by late December 2024. Administrators should ensure documentation and scripts are updated accordingly.

Following the rollout, the UserKey field in the compliance portal will represent the Entra ID ObjectId of the actor, and the new TargetObjectId parameter will capture the Entra ID ObjectId of the user affected by the action. Additionally, the ModifiedProperties parameter will capture both the old and new values of modified fields, making it easier to track changes to admin roles and other key scenarios.

If you are an admin querying audit logs in the Microsoft Purview compliance portal, you will need to ensure that your scripts and queries are updated to use the new parameters correctly. Before the rollout, UserKey was populated with the target user's Passport ID, and existing queries using this parameter will need to be updated. These changes will begin rolling out in late November 2024 and will be available worldwide by late December 2024.

Overall, these updates to the audit log schema reflect Microsoft's ongoing commitment to transparency and data governance, and will help ensure that users can trust and rely on Microsoft Viva Engage (Yammer) to communicate and collaborate securely.

The post Microsoft Viva Engage (Yammer): Enhanced audit log schema appeared first on M365 Admin.