Setting up SWOOP for Viva Engage - Actions required by customer and SWOOP

This page outlines the actions required to set up SWOOP for Viva Engage. These actions are split between the customer and SWOOP Analytics.

1. Preparing for set up

The table below outlines the key areas to investigate before starting the technical set-up of SWOOP for Viva Engage:

Area	Customer Action	SWOOP Action
Should a service account be created?	To connect SWOOP’s data miner to Viva Engage requires that a verified VE (yammer) admin account is used as Viva Engage does not offer application-level access, this account will be authenticated via a token to be used by the miner to retrieve the Viva Engage data needed for the analytics via the network data export. It is strongly recommended that a service account is used to connect the data miner to Viva Engage and to avoid data mining interruptions it is recommended that the password for the service account is set to not expire.	N/A.
Should additional user profile data be made available in SWOOP?	Many customers require the analytics to be segmented, eg by geography (eg country, state, city) or by hierarchy (eg department, function, team, job title). By default, SWOOP Analytics will fetch Department, Location and Job Title from each person’s profile information in M365. Consider which additional attribute data would be valuable, and if these are available in Azure Entra ID (previously called Azure AD). Sometimes these can be found in the ‘Extended Attributes’. Another option is to prepare a CSV file that has a list of all the users and their profile data which should look like this: email,country,city joe.smith@company.com,United States,Los Angeles mary.jones@company.com,United Kingdom,London In the example above the ‘country’ and ‘city’ attributes are provided but here is no limit to how many additional attributes can be added. Read more: https://support.swoopanalytics.com/hc/en-us/articles/115002714172-Where-does-SWOOP-get-people-attribute-data-from-Viva-Engage https://support.swoopanalytics.com/hc/en-us/articles/115002716951-How-to-integrate-with-Azure-Entra-ID-to-sync-Attribute-Data-and-Community-Group-Membership-Viva-Engage	N/A.
Privacy considerations	Is there a need to filter out certain people due to local requirements? For instance, it could be required to exclude users from a particular country. If so, determine which attribute can be used to identify this group of users. If the attribute is not available in Azure Entra ID (Azure AD), then prepare a CSV file of the people who are in scope. The CSV file should look like this: email,exclusion joe.smith@company.com,yes mary.jones@company.com,yes	N/A.
Who will be accessing SWOOP	SWOOP’s belief is that access to data should be democratised. Therefore the default access to SWOOP for Viva Engage is open to everyone who can access Viva Engage. However, this default setting can be changed and access can be restricted. Read more: https://support.swoopanalytics.com/hc/en-us/articles/115002714052-Admin-Access-rights-permissions-and-roles-in-SWOOP-Viva-Engage and determine who should have access to SWOOP.	N/A.
How will users authenticate? Does your organisation allow the use of SWOOP’s multi-tenant application?	When ‘Standard set up’ is selected during the technical set-up process SWOOP is using a multi-tenant app (see further below), and the set-up of user authentication is transparent and utilises standard Microsoft authentication (SSO). The customer can always try ‘Standard set up' if they are not certain about what to do. ‘Custom set up’ is for scenarios where the customer policy does not permit the use of a multi-tenant application and the application must be created in Azure Entra ID. Read more: https://support.swoopanalytics.com/hc/en-us/articles/17905312428313-Migration-to-Azure-or-Office-Authentication-for-Microsoft-Viva-Engage	N/A.

2. Technical Set-up of SWOOP for Viva Engage

Step	Customer Action	SWOOP Action
Initiate the set-up process	Click on the set-up URL. If you don’t know what this is please contact your SWOOP representative. This must be done by a M365 Administrator. Follow the steps outlined in this guide - https://support.swoopanalytics.com/hc/en-us/articles/115002714512-How-to-set-up-a-SWOOP-for-Viva-Engage-trial-technical-details Note that there is no difference in functionality and scope between a trial and the production system.	SWOOP is ready to assist if required during the set-up process.
Commence data mining	N/A.	SWOOP for Viva Engage commences data mining and the SWOOP team will monitor. An automated notification will be sent to the contact email designated by the customer during the set-up process once the initial data mining process has been completed.
Configure SWOOP	Any decisions made during the preparation steps now need to be implemented. Read the support material available from https://support.swoopanalytics.com/hc/en-us/categories/360001869191-SWOOP-for-Viva-Engage-Yammer find step-by-step instructions.	SWOOP is ready to assist if required during the set-up process.

Customer onboarding and ongoing use of SWOOP for Viva Engage

The following areas are included with the SWOOP Analytics subscription:

Area	Customer	SWOOP
Training for super users	The customer will identify a set of super users to be trained in the use of SWOOP for Viva Engage.	Deliver training.
CSM support	Business owner of SWOOP for Viva Engage to participate in quarterly review meetings.	Schedule quarterly review meetings.
Masterclasses and webinars	Sign up for masterclasses and webinars. The schedule is published on https://www.swoopanalytics.com/swoop-academy.	Schedule and run masterclasses and webinars.
Technical Support	Raise support requests when required.	Respond to requests.
Support Documentation	Use the help function within SWOOP Analytics. Click 'Help'.	Update documentation.