Microsoft Viva Engage: Mute user for network
From Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.Rollout
- Roadmap
- 396168
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 we saw- Seen 28 Nov 2024
mid-November 2024→ mid-December 2024 - Seen 8 Nov 2024
late October 2024→ mid-November 2024
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 structuredUpdated November 27, 2024: We have updated the rollout timeline below. Thank you for your patience.
Starting in early September 2024, customers will see a new setting in the Microsoft Viva Engage admin center to mute users across their networks. Muting a user removes new posts from that user from the Home feed, Storylines feed, and all email digests.
This message is associated with Microsoft 365 Roadmap ID 396168.
When this will happen
General Availability (Worldwide): We will begin rolling out early September 2024 and expect to complete by mid-December 2024 (previously mid-November).
How this will affect your organization
Network, Engage, and Global admins will be able to add or remove a user from mute for network status. The feature can be found in the Engage admin center under the Governance and Compliance tab. All admin activity related to muting users for the network is captured in the user audit log for Engage.
While muted, new ThreadStarters from a user cannot show in discovery surfaces, including the Home feed, Storylines feed, and email digests. Comments and replies from a muted user can show in discovery surfaces.
Muting a user does not affect visibility of ThreadStarters, comments, or replies in community feeds. Users and their content remain visible through search.
Muted users will not see any indication they’ve been muted. Admins can only see who is muted within the admin center. Users do not receive a notification when added or removed from mute status. Customers own all internal communication around the use of the feature.
Admins can mute any user in their network, including guest users. Muting applies per user per network. Up to 1,000 users can be muted simultaneously per network.
This new feature is available by default.
What you need to do to prepare
This rollout will happen automatically with no admin action required. You may want to notify your users about this change and update any relevant documentation as appropriate.
Please review the available documentation on Microsoft Support and Microsoft Learn, which will be available publicly after general availability rollout begins in September 2024: Reduce visibility of a user's posts in Viva Engage (Private Preview) | Microsoft Learn
What changed
Between archive captures, newest firstUpdated November
7,27, 2024: We have updated the rollout timeline below. Thank you for your … will begin rolling out early September 2024 and expect to complete bymid-Novembermid-December 2024 (previouslylate October).mid-November). How this will affect your organization: Network, Engage, and Global admins will …- Tags
Feature update, Admin impact→ Updated message, Feature update, Admin impact
Updated November 7, 2024: We have updated the rollout timeline below. Thank you for your patience. Starting in early September 2024, customers will see a new setting in … will begin rolling out early September 2024 and expect to complete by mid-November 2024 (previously late
October 2024.October). How this will affect your organization: Network, Engage, and Global admins will …- Tags
- · first version seen
Learn more
Links from the notice and their documentation checksRelated public changes
No related announcements were found in the saved public history. Check the source for newer announcements.
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.
- 1 linked page has not been read yet.