Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 272/272 feeds/APIs · 469/469 docs · 7/9 advisories · checked 05:36 UTC Customize Public modeDiscuss ChangeIntel on Discord

Viva Engage: Community membership and experts management in iOS and Android for Engage and Engage app in Teams

Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.

Rollout

Roadmap
532722, 537270

Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".

What the notice says

Microsoft’s text, with source markup removed
Introduction We’re rolling out new community membership management and trusted‑answer capabilities in the Viva Engage mobile experience for iOS and Android, available in both the standalone Viva Engage app and the Viva Engage app in Microsoft Teams. These updates extend existing web functionality to mobile, enabling more consistent community governance and moderation across devices and allowing key actions to be completed without switching to a desktop experience. This message is associated with Roadmap ID 532722 and 537270. When this will happen: General Availability (Worldwide): Rollout begins late March 2026 and is expected to complete by late April 2026. How this affects your organization: Who is affected: Organizations using Viva Engage communities Community admins and designated experts Users accessing Viva Engage on iOS or Android (standalone app or within Microsoft Teams) What will happen: Community admins can manage community members directly from mobile, including adding or removing members Community admins can assign or remove community admin roles from mobile Community admins can assign or remove expert roles from mobile Eligible roles can mark verified answers from mobile devices Users will see community expert indicators and verified-answer indicators in conversations The feature is enabled by default and respects existing role-based permissions No tenant-level configuration or policy changes are required What you can do to prepare: No action is required to enable this feature Review current community admin and expert role assignments to ensure they align with your governance model Inform community admins and moderators that these moderation and role-management tasks are now available on mobile Update internal documentation or helpdesk guidance if you document Viva Engage moderation workflows Learn more: Learn more about Viva Engage | Microsoft Learn Introducing Community Experts in Viva Engage Introducing Verified Answers in Viva Engage Manage a community in Viva Engage | Microsoft Support Compliance considerations: Question Explanation Does the change alter how existing customer data is processed, stored, or accessed? Existing community membership data, role assignments, and conversation answers can now be accessed and managed from mobile clients. No new data types are introduced, and data storage locations remain unchanged. Does the change include an admin control or role-based permission impact? Existing community admin and expert roles govern access to these capabilities on mobile. No new roles are introduced, and existing permission models are respected. Does the change allow a user to enable or perform new actions themselves? Eligible users can now perform moderation and verified-answer actions directly from mobile apps, whereas these actions were previously limited to web experiences.

What changed

Between archive captures, newest first

The archive supplies one version of this notice.

Linked documentation

Microsoft pages the notice links to

No related evidence found in this installation's recent collection. This does not establish that no announcement exists.

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.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 27 Oct 05:36 UTC · 272 of 272 readable · 271 fully read · documentation 469/469 current