Extending Azure Active Directory to Synchronise Group/Community Members (Viva Engage)

Scope

This article applies to organisations that have large community (or groups in Azure Active Directory) memberships. The Viva Engage API is slow at providing and synchronising group information so this article provides a method of using the Microsoft Graph API (part of Azure) to achieve the same result more efficiently.

Requirements

1. In order to perform the configuration described below Viva Engage must be running in Office 365 Native Mode (see https://www.yammer.com/swoopanalytics.com/admin/m365_native_mode ).
   
   
2. You must set up Azure Active Directory attribute integration (see https://support.swoopanalytics.com/hc/en-us/articles/115002716951-Adding-attribute-data-How-to-integrate-with-Azure-Active-Directory-Yammer- ). 

Instruction

The existing Azure Application you have configured needs to be extended by adding some additional application permissions:

• Group.Read.All
• GroupMember.Read.All

The instruction you may have previously used to create this application is here: https://support.swoopanalytics.com/hc/en-us/articles/115002716951-Adding-attribute-data-How-to-integrate-with-Azure-Active-Directory-Yammer- . The section regarding permission is steps 6-10 (but do not contain the above permissions).

After configuration your app permission should look like this (Note: 'SWOOP' should be your organisation):



After adding in new permissions please raise a support request via support@swoopanalytics.com so we can configure and test the new settings.