Viva Engage is aligning community and membership management with the Microsoft Entra model. From late September 2026, users with only the Verified Admin or Network Admin role need Yammer Administrator or Community Admin permissions to perform some actions.
The new Viva Engage Brand Center lets administrators customize the tenant’s logos, brand name, and theme color across the Engage web and mobile apps.
Microsoft accidentally created a new “All Company” Microsoft 365 group in some tenants during a July incident. Administrators should check whether their tenant now has two such groups for Viva Engage.
Microsoft has released independent admin settings for Viva Engage Communities and Storylines in Teams. Teams administrators should review and configure their preferred settings before Communities in Teams reaches general availability in June.
Viva Engage introduces new community and storyline event types: Broadcast (Town Halls), Meeting (Webinars), and Async (AMA) events, alongside a unified events landing page.
Viva Engage communities now support Microsoft Purview sensitivity labels assigned to Microsoft 365 groups and their connected SharePoint sites, bringing consistent privacy and access controls across Viva Engage, Microsoft 365 groups, and SharePoint.
Viva Engage communities are now rolling out in Microsoft Teams, bringing conversations and leadership engagement into the flow of daily collaboration. The new experience is enabled by default for users with access to Viva Engage.
Microsoft has announced a second Copilot in Viva Engage. While some Viva Premium licenses still include the previous Engage Copilot v1, the new Microsoft 365 Copilot in Viva Engage requires an additional Copilot license.
Depending on the age of the Microsoft 365 tenant, Viva Engage stores data either in the US or in the EU.