Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 272/272 feeds/APIs · 469/469 docs · 6/9 advisories · checked 14:23 UTC Customize Public modeDiscuss ChangeIntel on Discord

Microsoft Viva Engage: New reply and reaction notifications in Microsoft Teams

From Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.

Rollout

Roadmap
474126

Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".

Schedule dates changed in the text

Date phrases in schedule sentences differ between the versions this installation saw
  • Seen 7 Nov 2025 mid-January 2025, late June 2025
  • Seen 6 May 2025 late April 2025 → late June 2025
  • Seen 5 Mar 2025 late February 2025 → late April 2025
  • Seen 5 Feb 2025 late January 2025 → late February 2025

Read from date phrases in Microsoft's text, not from notice metadata. A changed phrase can be a moved rollout, a new milestone or just rewording; "What changed" below shows which.

What the notice says

Microsoft’s text, safely structured

Updated November 6, 2025: We have paused rollout of this item. We will communicate via Message center when we are ready to proceed. We apologize for any inconvenience this may have caused and thank you for your patience.

Coming soon for Microsoft Viva Engage: Users will have a new way to engage with the Viva Engage app in Microsoft Teams through new notifications in the Teams Activity feed. This message applies to Teams for the web, Teams for Windows desktop, Teams for Mac desktop, and Teams for iOS/Android.

After this rollout, users with the Engage app installed can be notified in Teams for replies and reactions to their community posts. This new feature helps large organizations stay connected and informed of news, updates, and safety while in Microsoft Teams.

This message is associated with Microsoft 365 Roadmap ID 474126.

When this will happen

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

How this will affect your organization

This feature will be available by default and the notifications will be on by default.

After this rollout, users can change notification settings in Teams for desktop or the web: Go to Activity on the left side of Teams, select the gear icon, and change settings in the Viva Engage section. In Teams for iOS/Android, users can turn notifications on or off for all apps from the notifications settings page.

User documentation: Manage notifications in Microsoft Teams - Microsoft Support

What you need to do to prepare

This rollout will happen automatically by the specified date with no admin action required before or after the rollout.

Share this news with users at your organization and consider pinning Engage next to Chats and Teams. Ensure your corporate communications team is aware of this additional channel of reaching users across the organization.

You may want to update any relevant documentation.

What changed

Between archive captures, newest first
  1. Updated MayNovember 6, 2025: We have updated the timeline below. Thankpaused rollout of this item. We will communicate via Message center when we are ready to proceed. We apologize for any inconvenience this may have caused and thank you for your patience. Coming soon for Microsoft Viva Engage: Users will … Teams for Windows desktop, Teams for Mac desktop, and Teams for iOS/Android. Updated February 5, 2025: We have updated the rollout timeline below. Thank you for your patience. After this rollout, users with the Engage app installed can be notified … Microsoft 365 Roadmap ID 474126. When this will happen: General Availability (Worldwide): We will begin rolling out mid-January 2025 and expect to complete by late June 2025 (previously late April). Rollout is currently paused. We will communicate via Message center when we are ready to proceed.  How this will affect your organization: This feature will be available by …

  2. Only details this page does not show changed.

  3. Updated March 5,May 6, 2025: We have updated the rollout timeline below. Thank you for your patience. Coming soon for Microsoft Viva … will begin rolling out mid-January 2025 and expect to complete by late AprilJune 2025 (previously late February).April). How this will affect your organization: This feature will be available by …

  4. Updated FebruaryMarch 5, 2025: We have updated the rollout timeline below. Thank you for … will begin rolling out mid-January 2025 and expect to complete by late FebruaryApril 2025 (previously late January).February). How this will affect your organization: This feature will be available by …

    • Tags New feature, User impact → Updated message, New feature, User impact

    Updated February 5, 2025: We have updated the rollout timeline below. Thank you for your patience. Coming soon for Microsoft Viva Engage: Users will have a new way … Teams for Windows desktop, Teams for Mac desktop, and Teams for iOS/Android. Updated February 5, 2025: We have updated the rollout timeline below. Thank you for your patience. After this rollout, users with the Engage app installed can be notified … will begin rolling out mid-January 2025 and expect to complete by late January 2025.February 2025 (previously late January). How this will affect your organization: This feature will be available by …

  5. · first version seen

Learn more

Links from the notice and their documentation checks

No related evidence found in this installation's recent collection. This does not establish that no announcement exists.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
  • 2 linked pages have not been read yet.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 27 Oct 14:23 UTC · 272 of 272 readable · 270 fully read · documentation 469/469 current