Loading...

Microsoft Viva Engage: Microsoft Entra permissions required for community and membership administration

Microsoft Viva Engage: Microsoft Entra permissions required for community and membership administration

Starting late September 2026, Microsoft Viva Engage will require Microsoft Entra permissions—Yammer Administrator role or Community Admin assignment—for community and membership management tasks previously allowed to Verified or Network Admins. Administrators should review and update role assignments accordingly. To align community administration in Microsoft Viva Engage with the Microsoft Entra security and administration model, we are changing how certain community and membership management actions are authorized. Today, users assigned the Verified Admin or Network Admin role within Viva Engage can perform a limited set of community and membership administration tasks, even if they do not have the corresponding permissions in Microsoft Entra. After this rollout, those actions will require the appropriate Microsoft Entra administrative permissions. To continue performing these actions, users must either: Be assigned the Yammer Administrator role in Microsoft Entra Be assigned as a Community Admin for the specific community they manage. This change improves alignment between Viva Engage administration and Microsoft Entra access controls. Rollout schedule General Availability (Worldwide): Beginning in late September 2026 and expected to complete by late September 2026 Impact on your organization Who is affected Organizations using Microsoft Viva Engage Users assigned the Verified Admin or Network Admin role within Viva Engage Community owners and administrators responsible for community and membership management Platforms and services Microsoft Viva Engage Microsoft Entra ID What will happen After this rollout, users assigned only the Verified Admin or Network Admin role within Viva Engage will no longer be able to modify the following community settings unless they are also assigned the Yammer Administrator role in Microsoft Entra or are designated as a Community Admin for the affected community: Community name Community description Community avatar Community privacy settings (public or private) Membership management Community deletion No changes are being made to Community Admin capabilities. Action required and recommendations Administrators should review current Viva Engage administrative assignments before rollout. Recommended actions: Review users currently assigned the Verified Admin and Network Admin roles in Viva Engage. Identify users who need to continue managing community settings or membership. Determine whether those users should be assigned the Yammer Administrator role in Microsoft Entra. […]

The post Microsoft Viva Engage: Microsoft Entra permissions required for community and membership administration appeared first on M365 Admin.

Published on:

Learn more
Need help with this product?

We can help you with Microsoft Viva Engage: Microsoft Entra permissions required for community and membership administration

If you want help implementing, troubleshooting, or improving this product, contact us and we’ll point you in the right direction.

M365 Admin
M365 Admin

by João Ferreira

Share post:

Related posts

Dynamics 365 Sales: Choose the data sources AI-powered Data Enrichment uses, including CRM notes

AI-powered Data Enrichment now lets admins choose which data sources the agent uses to enrich records. Outlook emails, Teams meetings, and the...

1 day ago

Microsoft Teams: Pro Management portal Analytics & Reports Design Refresh

We are refreshing the way we organize the Analytics & Reports area in the Pro Management portal to make it more user-friendly. Product Mic...

1 day ago

Copilot: Audio overviews on PDF Reteirement

Microsoft 365 Copilot mobile app’s Audio Overviews on PDFs, which create AI-generated podcast-style summaries for commercial users, will...

1 day ago

Public CDN is becoming optional during Brand Center setup

Brand Center setup will no longer require enabling Public CDN by default, allowing organizations to use branding governance without it. Public...

1 day ago

Microsoft 365 Copilot and Power Apps: Retirement of App Builder agent and vibe.powerapps.com

Microsoft is retiring the App Builder agent and vibe.powerapps.com by November 30, 2026, consolidating app creation into Copilot Cowork and Mi...

1 day ago

Outlook: Reply With a Template in Rules

New Outlook for Windows and Outlook on the web will let users create inbox rules that auto-reply with saved templates, automating routine resp...

1 day ago

Microsoft Purview Audit: AuditLogQuery API generally available and Search-UnifiedAuditLog retiring

The Microsoft Graph AuditLogQuery API will be generally available in October 2026, replacing the Search-UnifiedAuditLog PowerShell cmdlet, whi...

1 day ago

Dynamics 365 Sales – Information regarding the retirement of the Dynamics 365 Sales Insights standalone add-on

Starting November 1, 2026, Dynamics 365 Sales Insights as a standalone add-on will have reached end of support. Sales Insights is a legacy off...

1 day ago

Work IQ: Updating documents in Office

Work IQ enables agents to create and edit Microsoft Office documents using organizational context, helping users produce and update content mo...

1 day ago

Microsoft Purview: Information Protection – Apply default SharePoint library labels to data at rest

Enables auto‑labeling of existing SharePoint files to match the default sensitivity label configured on their document library. This helps org...

1 day ago

Newsletter

Get the latest Dynamics 365 and Power Platform content in your inbox

A curated digest of community blogs, product news, videos, and podcasts — delivered without the noise.

Weekly updates Unsubscribe anytime Fresh community picks
We use your email only for the newsletter and you can unsubscribe at any time.
By subscribing, you agree to the privacy policy.