Why User still access his yammer account as Local AD account is disabled 2 month ago

Saqib Fayaz Rehan 0 Reputation points
2023-08-28T05:42:46.21+00:00

Recently we had a complain a user which left organiation 2 month ago but can still access his yammer account

  1. Account Disabled on AD and in Disabled OU
  2. Office 365 License is un assigned

however in last we before not did to blocked signin on office 365 admin center.

Now we need justificaiton despite of user license unlicensed and inactive/disable on primeses AD how user can access Yammer App?

Microsoft 365
Microsoft 365
Formerly Office 365, is a line of subscription services offered by Microsoft which adds to and includes the Microsoft Office product line.
3,840 questions
Viva Connections
Viva Connections
A Microsoft Viva module that provides a gateway to a modern engagement experience.
87 questions
Windows Server 2016
Windows Server 2016
A Microsoft server operating system that supports enterprise-level management updated to data storage.
2,381 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Ling Zhou_MSFT 13,260 Reputation points Microsoft Vendor
    2023-08-31T07:46:30.55+00:00

    Hi @Saqib Fayaz Rehan,

    If a user's local AD account is disabled, it should also disable the user's access to Yammer. However, if the user is still able to access Yammer, it is possible that the user's account was not properly synced with Microsoft 365. The life cycle of users who are using their Microsoft 365 credentials to sign in to Yammer is now managed by Microsoft 365. Users who are deleted in Microsoft 365 will be suspended in Yammer.

    So, if you want the user to stop logging in to access Yammer, then remove the user in M365.

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments