check before: 2024-12-15
Product:
Entra, Microsoft Viva, Microsoft Viva Engage, Purview Communication Compliance
Platform:
Online, World tenant
Status:
Change type:
Admin impact, Feature update, Updated message
Links:
Details:
Summary:
The Microsoft Viva Engage (Yammer) audit log schema will be updated to include unique identifiers for both the user performing an action and the user/object affected. New parameters and field changes will enhance transparency and tracking capabilities. Rollout will begin mid-December 2024 and complete by late December 2024.
Details:
Updated December 11, 2024: We have updated the rollout timeline below. Thank you for your patience.
Coming soon to Microsoft Viva Engage (Yammer): We will update the audit log schema to include parameters that uniquely identify both the user performing an action (actor) and the user/object affected by that action (target).
After this rollout:
The actor will be identified by their unique Microsoft Entra ID ObjectId, stored in the UserKey field.
The target will be identified by a new parameter TargetObjectId that will also store the target's Entra ID ObjectId.
To improve transparency on changes to admin roles and other key scenarios, a new ModifiedProperties parameter will capture both the old and new values of modified fields.
These new parameters will be available for users with an E3 license.
[When this will happen:]
General Availability (Worldwide): We will begin rolling out mid-December 2024 (previously late November) and expected to complete by late December 2024 (previously mid-January 2025).
Change Category:
XXXXXXX ... free basic plan only
Scope:
XXXXXXX ... free basic plan only
Release Phase:
Created:
2024-10-25
updated:
2024-12-12
Task Type
XXXXXXX ... free basic plan only
Docu to Check
XXXXXXX ... free basic plan only
MS How does it affect me
XXXXXXX ... free basic plan only
MS Preperations
XXXXXXX ... free basic plan only
MS Urgency
XXXXXXX ... free basic plan only
MS workload name
XXXXXXX ... free basic plan only
summary for non-techies**
Microsoft is updating the audit log system for Viva Engage to include unique identifiers for actions and targets, such as Entra ID ObjectId for actors and TargetObjectId for targets, with a new ModifiedProperties field to track changes, requiring updates to queries in Microsoft Purview compliance portal for users with an E3 license.
Direct effects for Operations**
Audit Log Changes
The update to the audit log schema may lead to confusion among users if they are not informed about the new parameters (UserKey and TargetObjectId) and their implications. This could result in misinterpretation of audit logs and potential compliance issues.
- roles: Compliance Officer, IT Administrator
- references: https://learn.microsoft.com/purview/audit-search?view=o365-worldwide&tabs=microsoft-purview-portal" target="_blank" rel="nofollow noopener noreferrer">https://learn.microsoft.com/purview/audit-search?view=o365-worldwide&tabs=microsoft-purview-portal, https://learn.microsoft.com/viva/engage/track-engage-events#view-the-audit-sign-in-the-microsoft-365-security--compliance-portal
" target="_blank" rel="nofollow noopener noreferrer">https://learn.microsoft.com/viva/engage/track-engage-events#view-the-audit-sign-in-the-microsoft-365-security--compliance-portal
Script Compatibility
Existing PowerShell scripts and custom queries that rely on the old UserKey mapping (Passport ID) will fail or return incorrect results, leading to operational disruptions and increased troubleshooting time.
- roles: IT Administrator, DevOps Engineer
- references: https://learn.microsoft.com/purview/audit-search?view=o365-worldwide&tabs=microsoft-purview-portal" target="_blank" rel="nofollow noopener noreferrer">https://learn.microsoft.com/purview/audit-search?view=o365-worldwide&tabs=microsoft-purview-portal, https://sip.compliance.microsoft.com/homepage
User Experience
Users may experience delays or issues in accessing audit logs if they are not aware of the changes, leading to frustration and decreased productivity as they adapt to the new schema.
- roles: End User, Compliance Officer
- references: https://learn.microsoft.com/viva/engage/track-engage-events#view-the-audit-sign-in-the-microsoft-365-security--compliance-portal, https://learn.microsoft.com/purview/audit-search?view=o365-worldwide&tabs=microsoft-purview-portal" target="_blank" rel="nofollow noopener noreferrer">https://learn.microsoft.com/purview/audit-search?view=o365-worldwide&tabs=microsoft-purview-portal
Configutation Options**
XXXXXXX ... paid membership only
Opportunities**
XXXXXXX ... free basic plan only
Potentional Risks**
XXXXXXX ... paid membership only
Data Protection**
XXXXXXX ... paid membership only
IT Security**
XXXXXXX ... paid membership only
Hypothetical Work Council Statement**
XXXXXXX ... paid membership only
DPIA Draft**
XXXXXXX ... paid membership only
explanation for non-techies**
XXXXXXX ... free basic plan only
** AI generated content. This information must be reviewed before use.
a free basic plan is required to see more details. Sign up here
A cloudsocut.one plan is required to see all the changed details. If you are already a customer, choose login.
If you are new to cloudscout.one please choose a plan.
change history
| Date | Property | old | new |
| 2024-12-12 | MC Messages | Updated December 5, 2024: We have updated the rollout timeline below. Thank you for your patience.
Coming soon to Microsoft Viva Engage (Yammer): We will update the audit log schema to include parameters that uniquely identify both the user performing an action (actor) and the user/object affected by that action (target). After this rollout: The actor will be identified by their unique Microsoft Entra ID ObjectId, stored in the UserKey field. The target will be identified by a new parameter TargetObjectId that will also store the target's Entra ID ObjectId. To improve transparency on changes to admin roles and other key scenarios, a new ModifiedProperties parameter will capture both the old and new values of modified fields. These new parameters will be available for users with an E3 license. [When this will happen:] General Availability (Worldwide): We will begin rolling out mid-December 2024 (previously late November) and expected to complete by mid-January 2025 (previously late December). | Updated December 11, 2024: We have updated the rollout timeline below. Thank you for your patience.
Coming soon to Microsoft Viva Engage (Yammer): We will update the audit log schema to include parameters that uniquely identify both the user performing an action (actor) and the user/object affected by that action (target). After this rollout: The actor will be identified by their unique Microsoft Entra ID ObjectId, stored in the UserKey field. The target will be identified by a new parameter TargetObjectId that will also store the target's Entra ID ObjectId. To improve transparency on changes to admin roles and other key scenarios, a new ModifiedProperties parameter will capture both the old and new values of modified fields. These new parameters will be available for users with an E3 license. [When this will happen:] General Availability (Worldwide): We will begin rolling out mid-December 2024 (previously late November) and expected to complete by late December 2024 (previously mid-January 2025). |
| 2024-12-12 | MC Last Updated | 12/06/2024 01:07:16 | 2024-12-11T20:56:20Z |
| 2024-12-12 | MC Summary | The Microsoft Viva Engage (Yammer) audit log schema will be updated to include new parameters for identifying users and changes. The rollout timeline has been updated, starting mid-December 2024 and ending mid-January 2025. Users with an E3 license will have access to these updates. Admins should prepare by updating documentation and configurations. | The Microsoft Viva Engage (Yammer) audit log schema will be updated to include unique identifiers for both the user performing an action and the user/object affected. New parameters and field changes will enhance transparency and tracking capabilities. Rollout will begin mid-December 2024 and complete by late December 2024. |
| 2024-12-06 | MC MessageTagNames | Feature update, Admin impact | Updated message, Feature update, Admin impact |
| 2024-12-06 | MC Summary | Microsoft Viva Engage (Yammer) will update its audit log schema to include unique identifiers for the user performing an action (actor) and the user/object affected (target), along with a parameter to capture old and new values of modified fields. These changes will be available for E3 license users and will roll out by late December 2024. Admins should update documentation and scripts accordingly. | The Microsoft Viva Engage (Yammer) audit log schema will be updated to include new parameters for identifying users and changes. The rollout timeline has been updated, starting mid-December 2024 and ending mid-January 2025. Users with an E3 license will have access to these updates. Admins should prepare by updating documentation and configurations. |
| 2024-12-06 | MC Last Updated | 10/25/2024 00:55:10 | 2024-12-06T01:07:16Z |
| 2024-12-06 | MC Messages | Coming soon to Microsoft Viva Engage (Yammer): We will update the audit log schema to include parameters that uniquely identify both the user performing an action (actor) and the user/object affected by that action (target).
After this rollout: The actor will be identified by their unique Microsoft Entra ID ObjectId, stored in the UserKey field. The target will be identified by a new parameter TargetObjectId that will also store the target's Entra ID ObjectId. To improve transparency on changes to admin roles and other key scenarios, a new ModifiedProperties parameter will capture both the old and new values of modified fields. These new parameters will be available for users with an E3 license. [When this will happen:] General Availability (Worldwide): We will begin rolling out end-November 2024 and expected to complete by late December 2024. | Updated December 5, 2024: We have updated the rollout timeline below. Thank you for your patience.
Coming soon to Microsoft Viva Engage (Yammer): We will update the audit log schema to include parameters that uniquely identify both the user performing an action (actor) and the user/object affected by that action (target). After this rollout: The actor will be identified by their unique Microsoft Entra ID ObjectId, stored in the UserKey field. The target will be identified by a new parameter TargetObjectId that will also store the target's Entra ID ObjectId. To improve transparency on changes to admin roles and other key scenarios, a new ModifiedProperties parameter will capture both the old and new values of modified fields. These new parameters will be available for users with an E3 license. [When this will happen:] General Availability (Worldwide): We will begin rolling out mid-December 2024 (previously late November) and expected to complete by mid-January 2025 (previously late December). |
| 2024-12-06 | MC Title | Microsoft Viva Engage (Yammer): Enhanced audit log schema | (Updated) Microsoft Viva Engage (Yammer): Enhanced audit log schema |
| 2024-12-06 | MC End Time | 01/30/2026 09:00:00 | 2025-02-24T09:00:00Z |
Last updated 3 days ago
