Viva Engage Migration from Yammer Token into Entra ID

This article is only relevant to customers of SWOOP for Viva Engage who have been contacted by SWOOP technical support, and require migration by 1st July 2025.

Overview

Microsoft is removing "private content mode" and the current third-party application registration process. This has some critically important implications that we need your help to address. See https://techcommunity.microsoft.com/blog/viva_engage_blog/embracing-a-fully-modern-viva-engage-experience/4403008 for the announcement.

Currently, some customers are experiencing that Viva Topics are not accessible/visible in the SWOOP platform. This behaviour will be corrected once the steps outlined below have been completed.

Third-party Application Registration

The Third-party Applications, such as SWOOP, were registered within Viva Engage, and this was the official and approved way to connect SWOOP for Viva Engage to the customer's Viva Engage networks. After 1st July 2025, none of the third-party applications, SWOOP included, will work.

To keep using SWOOP, customers will need to allow SWOOP access to their Viva Engage network using a different process.

After 1 July 2025, all Viva Engage logins must go via Microsoft Entra ID.

Step 1 - Schedule a meeting with SWOOP support to do the change.

Log in to SWOOP and click Help, then Request Support and ask for a meeting to complete the migration. During the meeting between SWOOP and the customer, we will perform the process outlined below.

The customer must have an M365 Admin participating in the call.

Step 2 - Allow the SWOOP multi-tenant app permission to connect to Viva Engage

This step will require admin consent to a Multi-Tenant App, provided by SWOOP for this purpose. The app includes permissions (see below) that are closely equivalent to the existing third-party app. In particular, take note of the "user_impersonation" permission, which gives SWOOP's Entra ID Application access to the Viva Engage (Yammer) API. This will substitute for the current login process.

During the migration process the customer will see a new content screen:

Permissions granted to SWOOP's app

The permissions listed below are used for SWOOP's standard Multi-Tenant App. This allows OIDC login, which is a common style of Single Sign On, and this will be the preferred style of SWOOP login for the future. For more information about Microsoft authentication, see Microsoft OpenID Connect Protocol (OIDC).

App Roles

These are the SWOOP for Viva Engage app roles, which may be used for assigning permissions to users or groups, via Entra ID administration. This is optional, and not required for SWOOP login, but for larger organizations, assigning suitable security groups is good practice.

Also see the following links and screen shots for details about this change from Microsoft.

• https://learn.microsoft.com/en-us/rest/api/yammer/oauth-2
  
  
  
  
• https://learn.microsoft.com/en-us/rest/api/yammer/rest-api-rate-limits
  
  

Private Content Mode disappearing - implications for customers

Two areas are impacted by the deprecation of the Private Content Mode permission:

1. Without Private Content Mode, it will no longer be possible to see the Most Engaging Posts in a private community that the SWOOP Admin is not a member of.

Instead, we will show a message along the lines of "Content only visible to members". To see the content in Most Engaging Posts you will need to join the group.

None of the numbers, percentages, etc in all the SWOOP for Viva Engage reports will change.

2. Without Private Content Mode our current data-mining process will not work.

We are currently working together with Microsoft to explore alternative API calls / methods of getting the same analytics to our customers. We will keep updating this page with information as we progress.