The Microsoft Viva Engage keyword monitoring feature will move from the Yammer admin center to the new Viva Engage Communications Dashboard's Advanced moderation experience. This change, affecting various Engage apps, will roll out from mid-April to late June 2025. Admins need to review configurations and may notify users.
We will soon relocate the Microsoft Viva Engage keyword monitoring feature from the classic Microsoft Yammer admin center to a central Advanced moderation experience in the new Viva Engage Communications Dashboard, as communicated in MC1041122 Microsoft Viva Engage: New Communications Dashboard (published March 2025). Network admins, verified admins, and corporate communicators with Advanced moderation access (a granular permission in the corporate communicator role that must be explicitly enabled) will be able to add and monitor keywords in the new location.
This message is associated with Microsoft 365 Roadmap ID 478658.
This message applies to:
When this will happen:
General Availability (Worldwide): We will begin rolling out mid-April 2025 and expect to complete by late June 2025.
How this will affect your organization:
After this rollout:
Keyword monitoring from the Advanced moderation tab in the Communications dashboard:
This change will be on by default.
What you need to do to prepare:
This rollout will happen automatically by the specified dates with no admin action required before the rollout. Review your current configuration to determine the impact for your organization. You may want to notify your users about this change and update any relevant documentation.
Network admins, verified admins, and Engage admins can assign new or existing corporate communicators with Advanced moderation access from the Role management page in the Engage admin center. This granular permission in the corporate communicator role is disabled by default. This permission must be specifically enabled to facilitate moderation.
Learn more
We will update these documents before rollout:
Before rollout, we will update this post with new documentation.