MC1413304: Viva Engage Adds Recent Feed to 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 OwnersTeams Admins
Why this score?
AI Confidence
HIGH
Enough detail is available to trust this assessment.
Assessment Reasoning
Feature is rolling out globally with a new Recent feed in Viva Engage Home. No admin configuration is required, but internal communication and user support may be needed for awareness and documentation updates. User experience impact is moderate as feed navigation changes slightly but remains optional and intuitive.
30
🛡️ Admin Impact
40
👥 User Impact
40
Urgency
30
🔧 Effort
ℹ️ WHAT YOU NEED TO KNOW
📌

AT A GLANCE

Viva Engage adds a Recent feed in Home for chronological posts from followed sources, alongside the existing For you feed.
👥

END USERS

Users can switch between For you and Recent feeds for a different view of content.
🛡️

IT ADMINS

Update user guidance, inform comms and community teams, and prepare support teams for questions.
📅

ROLLOUT TIMELINE

Rolling out:
Mid-Aug to Early Oct 2026

📢 Official Microsoft Message Center Announcement


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

Updated September 11, 2026: We have updated the content. 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 early October 2026 (previously late 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.

Screenshot – Recent feed option in Viva Engage Home

21162

[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