A module within Microsoft Viva that serves as an enterprise social networking platform. It fosters community building, open dialogue, and knowledge sharing across an organization.
Common causes are:
- The sign-in path changed. Viva Engage sign-in for Microsoft Entra ID users goes through
https://engage.cloud.microsoftor the Microsoft 365 portal athttps://www.office.com/. If access is attempted throughhttps://www.yammer.com, that URL is for external networks only. Ifhttps://web.yammer.comis used, it redirects tohttps://engage.cloud.microsoftand requires Microsoft Entra ID credentials. - Browser session confusion across tenants. If there are multiple Viva Engage accounts or tenants, an existing browser session can keep the wrong identity signed in. Close all browser windows and reopen them before switching tenants. If access to multiple tenants is needed at the same time, use a different browser or an InPrivate/Incognito window for each tenant.
- Tenant/account mapping issues. If sign-in goes to the wrong tenant, or a different account appears under the same name and the original account shows as Former member, that is a configuration issue that must be resolved by the Viva Engage tenant admin.
- If the groups were external networks, access behavior is different. External users without a Microsoft Entra ID account can still use the external sign-in option on
https://engage.cloud.microsoft. Access throughhttps://www.yammer.comcontinues only for the external network experience.
Practical checks:
- Try signing in from
https://engage.cloud.microsoft. - If available, try from
https://www.office.com/and open Viva Engage there. - Close all browser windows first, then retry.
- If multiple company/community accounts exist, use a separate browser or InPrivate/Incognito session.
- If sign-in lands in the wrong tenant or the old account is no longer tied to the messages/groups, contact the Viva Engage tenant admin.