Account Security Problems

How to Deactivate Former Yammer Users with Shared Mailboxes

Tauseeq Magsi Oct 23, 2026 869 views

Question details

The user wants to deactivate or block former employees in Yammer without deleting their Microsoft Entra ID accounts, in order to preserve their shared mailboxes containing important messages.

How to Deactivate Former Yammer Users with Shared Mailboxes

Product: Microsoft Yammer
Device & OS: not provided
Scenario: Managing former employee accounts that have been converted to shared mailboxes.
Observed behavior: Deactivated users with shared mailboxes still appear as active accounts in the Yammer directory.

Before you start

Ensure you have Microsoft 365 Global Administrator or Yammer Administrator privileges before modifying user access and licenses in the admin center.

Solution 1Recommended

Remove Yammer Licenses and Block Sign-in

This method prevents the former employee from accessing Yammer while keeping their Azure AD/Entra ID account active, ensuring the shared mailbox is not deleted.

By simply removing the Yammer (or Viva Engage) license and blocking user sign-in from the Microsoft 365 Admin Center, you maintain the integrity of the shared mailbox while securing the Yammer environment.

Access Active Users

Select the User

Find and click on the name of the former employee whose account you wish to deactivate in Yammer.

Remove the License

Go to the 'Licenses and apps' tab, scroll down to the Apps section, uncheck the box for 'Yammer' (or 'Viva Engage'), and click 'Save changes'.

Block Sign-in

Return to the user's 'Account' tab and click on 'Block sign-in' to completely prevent the former employee from accessing any Microsoft 365 services.

Data Preserved: Because the Entra ID account remains intact, designated team members can still access the shared mailbox without interruption.

Solution 2

Disable Yammer Access Using PowerShell

For administrators needing to manage multiple users at once, PowerShell can efficiently disable Yammer access without affecting shared mailboxes.

Free Microsoft Office alternative

Manage Your Team's Documents with WPS Office

While resolving Microsoft 365 administrative tasks like Yammer deactivations, consider exploring WPS Office as a lightweight, highly compatible, and cost-effective alternative for your organization's document processing needs.

1. Download the Installer: Visit the official WPS Office website and download the free installation package for your operating system.
2. Install WPS Office: Run the downloaded installer and follow the quick on-screen instructions to set up the software.
3. Open Your Documents: Launch WPS Office and instantly open your existing Microsoft Office files without worrying about formatting issues.

Fully compatible with Microsoft Word, Excel, and PowerPoint formats (.docx, .xlsx, .pptx)Lightweight and fast, consuming minimal system resources on employee devicesIncludes powerful PDF editing, conversion, and collaboration toolsFamiliar user interface ensuring seamless employee onboarding with zero learning curve

microsoft office alternative - wps office

Frequently Asked Questions

Will deleting a user in Azure AD delete their shared mailbox?

Yes, if you fully delete a user's account in Microsoft Entra ID (formerly Azure AD), the associated shared mailbox that depends on that account may also be deleted. It is always recommended to remove licenses and block sign-in instead of deleting the account.

Why do former employees still appear active in Yammer after their accounts are disabled?

Yammer may still display deactivated Microsoft 365 users as active if their Yammer license wasn't explicitly removed, or if the Yammer directory hasn't fully synchronized with Microsoft Entra ID. Manually unchecking the Yammer app license resolves this.

What is Yammer Native Mode?

Yammer Native Mode is a state where all Yammer users, groups, and files are fully integrated and managed through Microsoft 365 and Microsoft Entra ID. In Native Mode, user management is streamlined through the Microsoft 365 admin center.

Microsoft Office Security Issues