MC1187781 - Viva Engage: Community feeds improvements

Message Center

Summary

Viva Engage communities will default to viewing conversations by recent posts instead of recent activity starting October 2026. Users can still choose their preferred feed and sort order, with settings saved across communities. Unread indicators will appear in both new and all feeds. No action required.

Discussionpowered by zap.ms

Last Updated

Oct 15, 2026

Published Nov 18, 2025

View version history

Service

Microsoft Viva

Tag

Updated message
New feature
User impact
Admin impact

Platforms

Web

More information

Updated October 15, 2026: We have updated the timeline. Thank you for your patience.   

Introduction:

We’re introducing a simpler way to view conversations in Viva Engage communities, organized by recent posts rather than recent activity. This new view is designed to make it easier for users to follow discussions and will be available as an option, alongside the current system, for those who prefer sorting by recent activity and filtering to new conversations only.

This message is associated with Microsoft 365 Roadmap ID 513275.

When this will happen:

General Availability (Worldwide): We will begin rolling out in October 2026 and expect to complete by the end of October 2026. 

How this will affect your organization:

This change should align better with how people expect to browse and engage with content in their communities, while still preserving the triage flow for those who prefer it.

Who is affected: All Viva Engage users in your organization.

Current experience:

  • Communities default to “new” and “recent activity” if there’s any new content (posts or replies).
  • If there’s no new content, the feed falls back to “all.”
  • Unread indicators on content only exist in the “new” feed.

New experience:

  • The feature will be ON by default.
  • Communities will default to “all” and “recent posts”:

user settings

  • Unread indicators will exist in both the “new” and “all” feeds.
  • A sticky user preference will be introduced:
    • If someone changes the feed (new/all) or sort order (recent posts/recent activity), we will maintain that setting across their communities.
    • If someone picks “new” and there’s no new content in the next community, we will fall back to “all” for that community visit, but “new” will remain the preference for that user.

What you can do to prepare:

No action is required.

Compliance considerations:

No compliance considerations identified, review as appropriate

Version history

8 versions tracked

Updated 7 times since Nov 18, 2025. Microsoft only ever shows the current version; this archive preserves the history.

Compare any two versions

From
To
  1. Oct 15, 2026 · 10:45 PMLatest · v8

    Changed: Body, End date

  2. Oct 1, 2026 · 10:19 PMv7

    Changed: Body, End date

  3. Jul 23, 2026 · 07:02 PMv6

    Changed: Body

  4. Jul 23, 2026 · 07:02 PMv5

    Changed: Body, End date

  5. May 15, 2026 · 07:40 PMv4

    Changed: Body, End date

  6. Mar 26, 2026 · 08:26 PMv3

    Changed: Body, End date

  7. Jan 27, 2026 · 05:49 PMv2

    Changed: Body, Tags, End date

  8. Nov 18, 2025 · 08:37 PMOriginal · v1

    Changed: Initial version