{"id":15611,"date":"2026-03-27T06:01:43","date_gmt":"2026-03-26T21:01:43","guid":{"rendered":"https:\/\/m365jp.net\/?p=15611"},"modified":"2026-03-27T06:06:07","modified_gmt":"2026-03-26T21:06:07","slug":"mc1187781-updated-viva-engage-community-feeds-improvements-2","status":"publish","type":"post","link":"https:\/\/m365jp.net\/index.php\/2026-03-27-mc1187781-updated-viva-engage-community-feeds-improvements-2","title":{"rendered":"MC1187781 | (Updated) Viva Engage: Community feeds improvements"},"content":{"rendered":"<div class=\"postie-post\">\n<div>\n<hr>\n<table id=\"section\">\n<tbody>\n<tr>\n<th width=\"95%\">MC1187781 | (Updated) Viva Engage: Community feeds improvements<\/th>\n<\/tr>\n<\/tbody>\n<\/table>\n<hr>\n<table id=\"data\">\n<tbody>\n<tr>\n<th>Classification<\/th>\n<td>stayInformed<\/td>\n<\/tr>\n<tr>\n<th>Last Updated<\/th>\n<td>03\/26\/2026 20:26:02<\/td>\n<\/tr>\n<tr>\n<th>Start Time<\/th>\n<td>11\/18\/2025 20:36:57<\/td>\n<\/tr>\n<tr>\n<th>End Time<\/th>\n<td>06\/30\/2026 08:00:00<\/td>\n<\/tr>\n<tr>\n<th>Message Content<\/th>\n<td>\n<p>Updated March 26, 2026: We have updated the timeline. Thank you for your patience.&nbsp;<\/p>\n<p><b>[Introduction:]<\/b><\/p>\n<p>  <\/p>\n<p>We\u2019re introducing a simpler way to view conversations in <i>Viva Engage communities<\/i>, 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.<\/p>\n<p>  <\/p>\n<p>This message is associated with Microsoft 365 Roadmap ID <a href=\"https:\/\/www.microsoft.com\/microsoft-365\/roadmap?filters=&amp;searchterms=513275\" target=\"_blank\">  513275<\/a>.<\/p>\n<p><b>[When this will happen:]<\/b><\/p>\n<p>  <\/p>\n<p><b>General Availability (Worldwide): <\/b>We will begin rolling out in May 2026 (previously February).<\/p>\n<p><b>[How this will affect your organization:]<\/b><\/p>\n<p>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.<\/p>\n<p>  <\/p>\n<ul>  <\/ul>\n<p><b>Who is affected:<\/b> All Viva Engage users in your organization.<\/p>\n<ul>  <\/ul>\n<p><b>Current experience:<\/b><\/p>\n<ul>\n<li>Communities default to \u201cnew\u201d and \u201crecent activity\u201d if there\u2019s any new content (posts or replies).<\/li>\n<li>If there\u2019s no new content, the feed falls back to \u201call.\u201d<\/li>\n<li>Unread indicators on content only exist in the \u201cnew\u201d feed.<\/li>\n<\/ul>\n<p><b>New experience:<\/b><\/p>\n<ul>\n<li>The feature will be <b>ON by default<\/b>.<\/li>\n<li>Communities will default to \u201call\u201d and \u201crecent posts\u201d:<\/li>\n<p>&nbsp;<img decoding=\"async\" style=\"width: 400px\" alt=\"user settings\" src=\"https:\/\/cxcs.microsoft.net\/static\/public\/messagecenter\/neutral\/f69d6653-11e2-483c-b294-eefcee2a99d4\/0ffa13ee2548d3211499540d4c97bfb9e0ffa654.png\"><\/p>\n<li>Unread indicators will exist in both the \u201cnew\u201d and \u201call\u201d feeds.<\/li>\n<li>A sticky user preference will be introduced:\n<ul>\n<li>If someone changes the feed (new\/all) or sort order (recent posts\/recent activity), we will maintain that setting across their communities.<\/li>\n<li>If someone picks \u201cnew\u201d and there\u2019s no new content in the next community, we will fall back to \u201call\u201d for that community visit, but \u201cnew\u201d will remain the preference for that user.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<ul>  <\/ul>\n<\/p>\n<\/p>\n<ul>  <\/ul>\n<\/p>\n<p><b>[What you can do to prepare:]<\/b><\/p>\n<p>  <\/p>\n<p>No action is required.<\/p>\n<p><b>[Compliance considerations:]<\/b><\/p>\n<p>  <\/p>\n<p>No compliance considerations identified, review as appropriate<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>MC1187781 | (Updated) Viva Engage: Community feeds improvements Classification stayInformed Last Updated 03\/26 [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-15611","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/posts\/15611","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/comments?post=15611"}],"version-history":[{"count":0,"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/posts\/15611\/revisions"}],"wp:attachment":[{"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/media?parent=15611"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/categories?post=15611"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/m365jp.net\/index.php\/wp-json\/wp\/v2\/tags?post=15611"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}