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

🚨 The Signal: Viva Engage community and membership administration now requires corresponding Microsoft Entra permissions. Users with only Viva Engage roles will lose admin capabilities, enforcing a stronger identity-based access control model.

The Impact

Viva Engage admins without Entra ID roles are affected, reducing the risk of over-privileged accounts.

• Viva Engage Verified Admins will lose community management if not also Entra ID Yammer Admins.
• Viva Engage Network Admins will lose membership management if not also Entra ID Yammer Admins.
• Community owners retain specific community admin rights.
• Risk of unauthorized access to community settings is reduced.

The Action

1. Identify all users currently assigned the 'Verified Admin' or 'Network Admin' role within Viva Engage.
2. For each identified user, determine if they require continued community or membership administration.
3. Assign the 'Yammer Administrator' role in Microsoft Entra ID to users requiring broad Viva Engage administrative capabilities.
4. Alternatively, ensure users are assigned as 'Community Admin' for specific communities they manage.
5. Review and update internal documentation for Viva Engage administration roles and responsibilities.

Domain: Entra · Impact: medium · Workload: Entra ID · Essential Eight: Restrict Administrative Privileges · ISM: ISM-0445, ISM-1175, ISM-1380, ISM-1507, ISM-1508, ISM-1509, ISM-1647, ISM-1648, ISM-1650, ISM-1686, ISM-1688, ISM-1689, ISM-1883, ISM-1897, ISM-1898