MC1413304: Viva Engage Adds Recent Feed in Home for Chronological Content View

MWPRO IMPACT SCORE
OPERATIONAL IMPACT
35
0 25 50 75 100
MODERATE IMPACT • ASSESS BUSINESS IMPACT
Recommended Action:
Take a look and decide whether this affects your tenant, users or support teams.
What is MWPro Impact Score? Watch our 60‑second explainer

Primary Audience

Microsoft 365 AdminsTenant AdminsIT ManagersService OwnersEnd Users
Why this score?
AI Confidence
HIGH
Enough detail is available to trust this assessment.
Assessment Reasoning
Timeline was adjusted to mid to late August, reducing immediate urgency. The change introduces a new Recent feed in Viva Engage Home, but requires no tenant configuration. Admin work focuses on communication, updating adoption materials and preparing support resources. Users will notice a new feed option but main workflows and navigation remain intact.
30
🛡️ Admin Impact
40
👥 User Impact
40
Urgency
30
🔧 Effort
ℹ️ WHAT YOU NEED TO KNOW
📌

AT A GLANCE

A new Recent feed is coming to Viva Engage Home, giving users a chronological view alongside the existing For you feed.
👥

END USERS

Users will see a Recent feed option in Home with chronological content from followed communities and people.
🛡️

IT ADMINS

Review internal materials, inform comms teams, update documentation, and prepare help desk for user questions.
📅

ROLLOUT TIMELINE

Upcoming:
Mid–late August 2026

📢 Official Microsoft Message Center Announcement


(Updated) Viva Engage: New Recent feed in Home
Message ID: MC1413304 (Updated)

Updated August 6, 2026: We have updated the timeline. Thank you for your patience. 

[What and Why:]

Microsoft is introducing a new Recent feed in Viva Engage Home, giving users a chronological view of content from followed communities, followed people, and priority communications. This enhancement complements the existing For you feed, which continues to provide personalized content recommendations.

This update improves personal productivity by providing users with a more predictable way to stay current with the content and communications most relevant to them, while preserving the discovery experience offered through personalized recommendations.

This message is associated with Microsoft 365 Roadmap ID 559482.

[Rollout Schedule:]

  • General Availability (Worldwide): Beginning in mid-August 2026 (previously early August); expected to complete by late August 2026 (previously mid-August)

[Impact on Your Organization:]

Who is affected:

  • All Viva Engage users accessing the Home experience.
  • Communications teams publishing organizational communications.
  • Community managers and leaders who rely on user engagement with community content.

Platforms/Services:

  • Viva Engage (Web)
  • Viva Engage (Mobile)
  • Viva Engage app in Teams (all clients)

What will happen:

  • A new Recent feed option will appear in Home. The default For you feed remains unchanged.
  • Users can switch between For you and Recent views.
  • The Recent feed displays content in a more chronological and predictable order.
  • Content surfaced in Recent includes:
    • Posts from followed communities.
    • Content from followed people.
    • Priority communications.
  • The existing For you personalized feed remains available.
  • User feed preferences are preserved across web and mobile clients.
  • The option to use the feature is enabled by default as part of the service update.
  • No tenant configuration changes are required.

[Action Required / Recommendations:]

No admin action is required.

We recommend that you:

  • Review internal Viva Engage adoption materials.
  • Inform communications teams about the new feed experience.
  • Notify community managers and leaders of the update.
  • Prepare help desk teams for user questions.
  • Update user documentation where appropriate.
  • Monitor feedback after rollout.

[Compliance Considerations:]

No compliance considerations identified, review as appropriate for your organization.

Source: Microsoft Message Center • Analysed by MWPro

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

Share This Update