A module within Microsoft Viva that serves as an enterprise social networking platform. It fosters community building, open dialogue, and knowledge sharing across an organization.
To verify that the Viva Engage network is configured for communities connected to Microsoft 365 Groups, and to control who can create those communities, use these steps.
- Verify the network is eligible and enabled for Microsoft 365‑connected communities
- Open the Viva Engage admin center.
- Go to Network Admin > Security Settings.
- In the Microsoft 365 Connected Viva Engage Groups section, confirm that the status for the network shows Enabled.
- If it is not enabled, first ensure that Microsoft 365 identity is enforced and committed:
- In the same admin area, check Microsoft 365 Identity Enforcement.
- After enforcement is committed, about 24 hours later the Microsoft 365 Connected Viva Engage Groups status changes to Enabled and new eligible communities will automatically be connected to Microsoft 365 Groups.
- If it is not enabled, first ensure that Microsoft 365 identity is enforced and committed:
- Confirm the configuration requirements for connected communities Once the status is Enabled, communities are connected to Microsoft 365 Groups according to these rules:
- The community owner must have Microsoft 365 Group creation privileges.
- The community must be a public or private internal community (not an unlisted private or external group).
- The community must have an owner and at least one member.
- Control who can create Microsoft 365‑connected communities
- Microsoft 365 Group creation permissions in the tenant directly control who can create Microsoft 365‑connected Viva Engage communities.
- To restrict or manage who can create these groups, configure the Microsoft 365 Group creation policy as described in manage who can create Microsoft 365 Groups. Only users with group creation permission will be able to create Microsoft 365‑connected communities in Viva Engage.
- Handling existing and unconnected groups
- Existing eligible communities are automatically converted to Microsoft 365‑connected communities about one week after the network becomes eligible.
- If there are unconnected communities that later become eligible (for example, after changing group creation policies or adding an owner with group creation permission), submit a support request to have all eligible groups in the network connected.
References: