How to Convert a User Mailbox to a Shared Mailbox

Converting a user mailbox to a shared mailbox is a routine Microsoft 365 admin task — most commonly run when an employee leaves and the team needs to keep reading mail sent to that address. The result is a mailbox multiple people can access and send from, without consuming an individual Exchange Online licence, provided the mailbox stays under the 50 GB shared quota.

The Microsoft 365 admin centre handles the conversion in a handful of clicks. The Exchange admin centre and Exchange Online PowerShell cover the same operation and are more practical when you need to convert several mailboxes at once or want a scripted, auditable pipeline. This guide walks through all three paths, explains the size ceiling and what it means for licence economics, and covers what happens to inbox rules, In-Place Archives, and litigation holds along the way — including how to reverse the conversion if you need to.

What you need before you start#

The conversion requires a Global Administrator or Exchange Administrator role. A User Management Administrator role does not have permission to change the mailbox type, and the 'Convert to shared mailbox' button simply will not appear in the admin centre without the right role.

Check the mailbox size before acting. In the Microsoft 365 admin centre go to Users > Active users, select the user, and look at the Mailbox usage figure on the Mail tab. Alternatively, run Get-MailboxStatistics -Identity [email protected] in Exchange Online PowerShell and read the TotalItemSize output. The number you are looking for is 50 GB: if the mailbox is under that threshold after conversion you can safely remove the Exchange Online licence, and the shared mailbox will continue receiving mail. If it is over 50 GB, you need to either trim it below the threshold first or keep an Exchange Online Plan 2 licence assigned — otherwise the mailbox will eventually stop accepting new messages once it exceeds the unlicensed quota.

Note any special properties before converting. If the user has litigation hold enabled, that property is preserved on the shared mailbox, but maintaining it requires an Exchange Online Plan 2 licence. If the user has an In-Place Archive, the archive survives the conversion but requires an Exchange Online Archiving or Exchange Online Plan 2 licence to stay active. Run Get-Mailbox -Identity [email protected] | Select LitigationHoldEnabled,ArchiveStatus before touching the licence to avoid a surprise compliance gap.

How to convert a user mailbox to a shared mailbox#

The steps below use the Microsoft 365 admin centre, which is the most accessible path for a single conversion. The Exchange admin centre and PowerShell alternatives are covered in the next section.

1. 1

   Sign in to the Microsoft 365 admin centre

   Go to admin.microsoft.com and sign in with a Global Administrator or Exchange Administrator account.

2. 2

   Go to Users > Active users

   Find the user whose mailbox you want to convert. You can search by name or email address in the search bar at the top of the list.

3. 3

   Open the user's Mail tab

   Click the user's display name to open their properties pane, then select the Mail tab.

4. 4

   Click 'Convert to shared mailbox'

   Scroll to the Convert section near the bottom of the Mail tab. Click 'Convert to shared mailbox,' read the confirmation prompt, and confirm. If the button is missing, check that your account holds Global Administrator or Exchange Administrator — not just User Management Administrator.

5. 5

   Wait for the conversion to complete

   The conversion typically takes two to five minutes. The user account and its licence remain active during this time. You will see a success confirmation when it finishes. If you are unsure it worked, run Get-Mailbox -Identity [email protected] | Select RecipientTypeDetails in PowerShell — a successful conversion returns SharedMailbox.

6. 6

   Remove the Exchange Online licence if the mailbox is under 50 GB

   Go back to the user, select the Licenses and apps tab, uncheck the Exchange Online licence (and any Microsoft 365 Apps licence if the account is being offboarded), and save. If the mailbox is over 50 GB, keep an Exchange Online Plan 2 licence assigned or reduce storage first.

7. 7

   Grant access to the shared mailbox

   In the Microsoft 365 admin centre go to Teams and groups > Shared mailboxes, find the newly converted mailbox, and add members. Full Access lets a member read and send from the shared mailbox; Send As makes replies appear to come from the shared address rather than the individual's address. Both permissions can be assigned together.

Admin centre, Exchange admin centre, and PowerShell compared#

All three methods produce the same result. The differences are in how much control you get over the surrounding steps and whether you can process multiple mailboxes in one pass.

To convert via the Exchange admin centre, go to admin.exchange.microsoft.com, open Recipients > Mailboxes, select the target mailbox, and choose 'Convert to shared mailbox' from the mailbox details pane or the Actions menu. The conversion step is identical to the admin centre method; licence removal still happens in the Microsoft 365 admin centre.

For PowerShell, connect with Connect-ExchangeOnline -UserPrincipalName [email protected], then run Set-Mailbox -Identity [email protected] -Type Shared. Verify the result immediately with Get-Mailbox -Identity [email protected] | Select RecipientTypeDetails. Licence removal can be done through the Microsoft 365 admin centre or via the Microsoft Graph PowerShell SDK if you want a fully scripted offboarding pipeline.

What happens to rules, archive, and holds after conversion#

Inbox rules created by the original user are preserved after conversion and are visible to delegates who have Full Access to the shared mailbox. Delegates can view and update those rules from Outlook's Rules settings while signed in to the shared mailbox. Rules created by delegates run under the delegate's own account scope unless you configure them as server-side rules targeting the shared mailbox identity via the New-InboxRule PowerShell cmdlet.

Calendar items and contacts move with the mailbox unchanged. Any automatic reply configured by the original user remains in place — which means a departed employee's out-of-office message will still greet external senders unless you update or clear it. Go to the shared mailbox settings in the Microsoft 365 admin centre or use Set-MailboxAutoReplyConfiguration in PowerShell to update it.

In-Place Archives survive the conversion, but the licence entitling the archive does not stay active automatically. If you remove the Exchange Online Plan 2 or Exchange Online Archiving licence, the archive enters a read-only state: existing archived items remain visible to delegates but no new items can flow into it, and the archive policy stops running. To keep the archive fully active after conversion, assign a standalone Exchange Online Archiving licence to the shared mailbox separately — it does not require a full Exchange Online Plan 2 user licence.

Litigation hold is a mailbox-level property and is preserved through the conversion. However, the entitlement to maintain litigation hold on a shared mailbox requires an Exchange Online Plan 2 licence. Removing the licence while hold is active does not immediately break the hold, but it removes the Microsoft 365 entitlement that backs it, which creates a compliance risk. Resolve this before the licence is removed.

What to do when the conversion does not work#

The most common reason the 'Convert to shared mailbox' button is missing is an insufficient admin role. Confirm that the account performing the conversion holds Global Administrator or Exchange Administrator in the admin centre under Settings > Admin roles. User Management Administrator cannot change the mailbox type.

If the conversion appears to succeed but the mailbox still shows as a user mailbox several minutes later, verify with PowerShell: Get-Mailbox -Identity [email protected] | Select RecipientTypeDetails. If it returns UserMailbox, the conversion silently failed — retry from the Exchange admin centre, or run Set-Mailbox -Identity [email protected] -Type Shared in PowerShell and look for any error output. A common cause is a conflicting mailbox type; resource mailboxes (room or equipment) cannot be converted to shared mailboxes through the standard path.

If you remove the licence and later discover the mailbox is over 50 GB, do not panic — Microsoft does not immediately block the mailbox. The unlicensed 50 GB quota is enforced going forward: once the mailbox exceeds the limit, it enters a send-prohibited state for new inbound messages. Assign an Exchange Online Plan 2 licence, archive older items to bring the primary mailbox below 50 GB, or both.

Delegates who are granted Full Access sometimes find the shared mailbox does not appear automatically in Outlook. Outlook automapping usually propagates the new permission within one to two hours. To force it sooner, have the delegate remove and re-add their Microsoft 365 account in Outlook, or confirm automapping is enabled by running Get-MailboxPermission -Identity [email protected] and checking the AutoMapping column.

How to convert a shared mailbox back to a user mailbox#

The reverse operation requires PowerShell — there is no button for it in either admin centre. Connect to Exchange Online PowerShell and run Set-Mailbox -Identity [email protected] -Type Regular. Then immediately assign a valid Exchange Online licence to the account in the Microsoft 365 admin centre; a regular user mailbox without a licence is suspended within 30 days and mail stops flowing to it.

If the user account was deleted after the original conversion, you have a 30-day window to restore it from the deleted users list in the Microsoft 365 admin centre before the account is permanently deleted. Restore the account first, then convert the mailbox type back and assign the licence. After 30 days the account enters a permanently deleted state, and recovery requires working with Microsoft Support to retrieve an inactive mailbox — a significantly more involved process.

Managing the shared mailbox after conversion#

The conversion is a one-time admin step. The ongoing work is making sure the people reading and responding from the shared mailbox can do it efficiently — especially if it is a support address, a team inbox, or a role address like billing@ that multiple people monitor.

We build AI Emaily, an AI-native email client that connects to shared mailboxes alongside personal Gmail, Outlook, and IMAP accounts. Once a team is working from a converted shared mailbox, AI Emaily can draft replies in a consistent voice, route threads to the right person, and keep an audit trail of what was sent and by whom — so a shared inbox does not become a pile of unattributed, unanswered mail. A 7-day free trial covers shared mailbox setup at no cost; see AI Emaily pricing for the full plan comparison.

The conversion itself does not break any existing mail flow. External senders who emailed the original user address continue to reach the same mailbox, now accessible to everyone you have granted access — no DNS changes, no forwarding rules, and no update to the sender's address book required.