(Updated) Microsoft Viva: A new reactions design in Viva Engage [MC892641]

(Updated) Microsoft Viva: A new reactions design in Viva Engage [MC892641]

Message ID: MC892641 (Updated)

Updated July 25, 2025: After further review, we are not able to continue rolling this out at this time. We apologize for any inconvenience.

Customers will see a new design for reactions in conversation cards across Microsoft Viva Engage web, Microsoft Teams and Outlook apps, and interactive emails in Outlook Web app and new Outlook for Windows.

This message is associated with Microsoft 365 Roadmap ID 416644.

[When this will happen:]

General Availability (Worldwide): We will communicate via Message center when we are ready to proceed.

[How this will affect your organization:]

Engage conversations will have a new design to show reactions across threadstarters, comments, and replies. The redesign brings a more interactive style, showing users’ reactions as clickable pills like what’s seen in other Microsoft 365 applications.

There are no changes to the number of icons available. The change will first show in Engage web (browser), Teams and Outlook apps, and interactive emails in Outlook Web app and new Outlook. In the future, we will launch in other surfaces, including the Engage iOS and Android apps.

Users will also see a dedicated copy link button and streamlined share button in threadstarters.

cc0bbfc2 4c18 4523 b383 65cb093d0f71

There are no changes to the core reactions capabilities, nor does the new design affect any data handling. This redesign is solely focused on the end-user experience.

[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.

Source: Microsoft

<<< [MC892641] Archive
Tooltip: View earlier revisions of this post

Latest Posts

Leave a Comment

Comments

No comments yet. Why don’t you start the discussion?

Leave a Reply

Your email address will not be published. Required fields are marked *