Anyone know how to remove Viva Engage as the MS KB article is out of date

Anonymous
2025-03-12T00:17:00.9866667+00:00

I need to remove the access to Yammer/Viva Engage on our tennant.

I found various PS scripts and this KB article.

https://xtls-v4.hkg1.meaqua.org/en-us/viva/engage/manage-engage-licenses-microsoft-365

In typical MS fashion they've made changes and "new looks" for this area and changes to the PS commands, so the KB article is no longer valid and the code on the page is no long working as Set-MsolUserLicense is now a dead command. (https://answers.microsoft.com/en-us/msoffice/forum/all/why-set-msoluserlicense-is-no-longer-working/9e10ddbe-0990-4bb8-ba42-0e4d854de0d3)

Is there any other ways? I have also tried removing users via the admin center but they can still access Viva Engage after this is done.

Thanks in advance

Microsoft 365 and Office | Development | Microsoft 365 App Publishing
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Vasil Michev 123.6K Reputation points MVP Volunteer Moderator
    2025-03-12T08:24:40.9233333+00:00

    Microsoft is in the process of deprecating the MSOnline module and they are yet to update all the affected documentation, as you have noted above. You can of course remove licenses via the UI, but that's only feasible for small tenants. If you want an automated approach, PowerShell remains the best option. Tony has a good script on doing just that here: https://office365itpros.com/2024/04/23/remove-service-plan-powershell-2/

    As for the latter part of your questions, removing the license is just a part of the solution. You must also configure the Yammer/Engage settings to block users without license. This is done on a per-network basis, you need to access the Network admin settings > Security settings > toggle the Block Office 365 users without Yammer licenses checkbox under Office 365 Identity enforcement.


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.