Overview of Viva Engage in Native Mode for Microsoft 365
As of January 2020, all new Viva Engage tenants start in Native Mode.
Note
Native Mode is strongly recommended for reasons of security, compliance, and Microsoft 365 integration. Existing Viva Engage tenants are eligible to migrate to Native Mode. The retirement of hybrid and non-native networks was announced in 2022. Any existing non-native networks are automatically migrated to Native Mode. For more information, see Automatic Native Mode migration and network consolidation
Frequently asked questions
In Native Mode, all Viva Engage users are in Microsoft Entra ID, all groups (communities) are Microsoft 365 groups, and all files are stored in SharePoint Online.
Note
There are no bandwidth requirements for Native Mode migration because nothing is downloaded. You are essentially moving from a separate Viva Engage site to Microsoft 365 and SharePoint Online. The only consideration is the SharePoint Online quota if Viva Engage has been extensively used.
A tenant must be in one of three modes:
Native Mode for Microsoft 365. In this mode, the network only uses features that allow users, groups, and content to be compatible with and mapped to their counterparts in Microsoft Entra ID and Microsoft 365.
When Viva Engage content is in Native Mode, you can search for it in the Microsoft Purview compliance portal.
In this mode, users and admins can't add features that would take the network out of Native Mode.
Non-Native Mode. In this mode, the network doesn't meet one or more requirements. For example, the network might not enforce Microsoft 365 identity. All external networks and Viva Engage Basic networks are in this mode because they can't connect to Microsoft 365.
Hybrid Mode. In this mode, users and groups might not be associated with their counterparts in Microsoft Entra ID and Microsoft 365, and files might not be stored in SharePoint. The network might be in the process of meeting all requirements for Native Mode, but the admin hasn't committed the network to Native Mode.
Note
As of 2023, non-Native and Hybrid modes are retired.
When you align your network in Native Mode, the Native Mode Alignment Tool automates the process and guides you through the steps to get there.
Note
All Company now works like any other community in Native Mode. Admins can customize All Company and use advanced management features, such as restricting posts and promoting others as admins. For more information, see All Company now works like other Viva Engage communities.
Key differences between modes
Native Mode
- No one can inadvertently take your network out of Native Mode.
- eDiscovery through the Microsoft Purview compliance portal is supported for your home network.
- All Viva Engage groups, users, and group memberships are managed through Microsoft 365. Management should be done through the Microsoft 365 admin center, Microsoft Entra admin center, or other Microsoft Entra management tools.
- All communities or groups, including All Company, are Microsoft 365-connected, which means they have access to Microsoft 365 features, including live events.
- Viva Engage honors Microsoft 365 Group creation rights and enforces Microsoft 365 Group creation restrictions.
- Guests can only be added at the community level. But external networks are supported in the US geo.
- All files uploaded to groups are stored in SharePoint.
- Files can't be uploaded to Viva Engage private messages.
- Engage admins (Yammer administrators) must have Group admin privileges from Microsoft 365 to administer changes to communities they don't own.
Non-Native Mode (not connected)
- All Viva Engage users can create communities.
- Files aren't stored in SharePoint.
- Files can be attached to Viva Engage private messages.
- Engage admins (Yammer administrators) aren't required to have any more admin privileges from Microsoft 365 to administer changes to groups.
Hybrid Mode
- This step on the way to Native Mode lets you learn how Native Mode works.
- All Viva Engage users can create communities.
- New files uploaded to Microsoft 365-connected groups are stored in SharePoint.
- Files can be attached to Viva Engage private messages.
- Engage admins (Yammer administrators) aren't required to have any other admin privileges from Microsoft 365 to administer changes to groups.