M365 Changelog: Microsoft Viva: Required approval for Viva Amplify – Aug 26, 2024

Summary

The new 'Required approval' feature in Microsoft Viva Amplify ensures content undergoes review before publishing. It's an optional setting found under 'Campaign settings'. Rollout begins late August 2024, with no admin action needed but users should be informed. Viva Amplify on mobile is excluded.

MC873749 – Like Lists and libraries, Viva Amplify campaigns can contain sensitive information, such as marketing campaign budgets or human resources initiatives. The Required approval feature brings compliance, accountability, and workflows to Lightweight Approvals in Viva Amplify. Whether you require multiple levels of approvals or approvals from a single decision maker, the new Required approval feature in Viva Amplify empowers communicators to customize the process to suit their approval workflow and ensure every piece of content undergoes a thorough review process before it is published.

The Required approval button is present under the Advanced settings of the Campaign settings experience, which can be accessed in any given campaign’s header section. When the Required approval setting is enabled, all newly created publications will be required to go through the approval process before content can be published. 

This is an optional setting. 

This message is associated with Microsoft 365 Roadmap ID 409233.

When this will happen: 

General Availability (Worldwide): Microsoft will begin rolling out late August 2024 and expects to complete by late September 2024.

How this will affect your organization:

Viva Amplify users will be able to set a campaign’s setting so that approval is required across all publications before the content is published. This feature is available for users in the web/desktop experience. Please note that Viva Amplify on Mobile iOS and android applications is currently out of scope.  

This update is available by default.

What you need to do to prepare:

This rollout will happen automatically with no admin action required. You may want to notify your users about this change and update any relevant documentation as appropriate.