Should You Delete a User After Converting a Mailbox to Shared in Microsoft 365?
Question details
The user wants to know if it is safe to delete the original Microsoft 365 user account after successfully converting their personal mailbox into a shared mailbox.
- Product
- Microsoft 365 Exchange
- Device & OS
- not provided
- Scenario
- An administrator is managing user offboarding or reorganizing mailboxes by converting a licensed user's mailbox into a shared mailbox.
- Observed behavior
- Deleting the original user account inadvertently deletes the newly converted shared mailbox and all associated email data due to system associations.
Ensure you have active Global Administrator or Exchange Administrator privileges in the Microsoft 365 admin center before making modifications to user accounts.
Retain the Account and Block Sign-In
The recommended approach is to keep the original user account active but block their ability to sign in. This preserves the shared mailbox data while completely preventing unauthorized access.
In Microsoft 365, a shared mailbox remains deeply tied to the original user object in Entra ID (Azure Active Directory). Deleting the user account will result in the immediate deletion of the shared mailbox and its contents.
Instead of deleting the user, you should block their sign-in capabilities and optionally remove their paid license to save costs.
Log in to the Microsoft 365 admin center and navigate to the 'Users' menu on the left sidebar, then select 'Active users'.
Locate and click on the display name of the user whose mailbox you recently converted to shared.
In the user pane that slides out on the right, remain on the 'Account' tab and click on the 'Block sign-in' icon.
Check the box to block the user from signing in, then click the 'Save changes' button at the bottom.
Restore an Accidentally Deleted Shared Mailbox
If you have already deleted the user account and subsequently lost the shared mailbox, you must restore the deleted user account from the admin center to recover the data.
Manage Your Documents Effectively with WPS Office
While managing Exchange server configurations requires Microsoft 365 admin tools, you don't need expensive subscription plans for your daily document productivity. WPS Office offers a free, lightweight, and highly compatible alternative to Microsoft Office for creating, editing, and sharing documents.
- 1. Download the Installer: Visit the official WPS Office website and click the free download button for your operating system.
- 2. Install WPS Office: Run the downloaded executable file and follow the on-screen prompts to complete the lightweight installation.
- 3. Open Your Office Documents: Launch WPS Office and directly open any existing Microsoft Office files to start editing instantly.
Frequently Asked Questions
Can I remove the Microsoft 365 license after converting to a shared mailbox?
Yes. Once the mailbox has been successfully converted to a shared mailbox, you can safely remove the license from the original user account via the 'Licenses and apps' tab. The shared mailbox will continue to function properly without a paid license, provided its total storage size remains under 50 GB.
What happens if I accidentally delete the user account instead of blocking it?
If you delete the user account, the attached shared mailbox and all its emails will be deleted immediately. Fortunately, you have a 30-day grace period to navigate to 'Deleted users' in the admin center and restore the account, which will automatically recover the shared mailbox.
Does a shared mailbox require its own password to access?
No. A shared mailbox does not have or need its own password. Instead, administrators grant delegation or read/write permissions to specific active users. Those users then access the shared mailbox by logging in with their own personal Microsoft 365 credentials.
Why is the shared mailbox still tied to the original user account?
This is due to the fundamental architecture of Microsoft 365 and Exchange Online. The shared mailbox relies on the underlying user object in Entra ID (formerly Azure Active Directory) to exist. Although the mailbox type attribute changes from 'User' to 'Shared', the primary directory object must remain intact.
