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

Microsoft Copilot (Microsoft 365): Local inferencing

Local inferencing expands Microsoft Copilot’s sovereign controls by enabling AI inferencing for supported Copilot interactions to occur within...

1 day ago

Dynamics 365 Customer Service: Quality evaluation supports knowledge source in criteria

Criteria questions can now use knowledge sources to help evaluate customer interactions. This allows organizations to ground evaluation criter...

1 day ago

Microsoft Viva: Ability for leaders to publish Power BI reports

Microsoft Viva Insights is extending its report publishing capabilities from analysts to leader personas such as Chief Officers, Managers and ...

1 day ago

Dynamics 365 Customer Service: Detailed quality evaluation score breakdown

Evaluation details now include a scoring breakdown at the overall, section, and question level. Users can see how the final evaluation score w...

1 day ago

Dynamics 365 Customer Service: Support Not Applicable answer option for quality evaluation criteria

Criteria questions now support a Not Applicable answer option. When a question is marked as not applicable, it is excluded from scoring instea...

1 day ago

Dynamics 365 Customer Service: Inactivate quality evaluation records

Quality managers can now inactivate evaluation records that should no longer contribute to scoring or reporting. Inactive evaluations are pres...

1 day ago

Microsoft Teams: Granular Conditional Access for Teams meetings

Granular Conditional Access for Teams meetings gives organizations greater control over access to sensitive meetings. Administrators can apply...

1 day ago

Customized PowerBI reports behavior after major report updates

Microsoft Viva Insights customized Power BI reports will remain tied to their original report versions and won’t auto-update with major report...

1 day ago

Microsoft SharePoint: Changes to the FAQ web part authoring experience

The SharePoint FAQ web part will shift AI-assisted FAQ creation to Copilot in SharePoint, while retaining manual FAQ editing in the web part. ...

1 day ago

Microsoft 365 Copilot: Federated Copilot connectors support create, update, and delete actions

Microsoft 365 Copilot’s federated connectors will support create, update, and delete actions in third-party services starting October 20...

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.