Converting a User Mailbox to a Shared Mailbox

Comprehensive step-by-step guide to converting a Microsoft 365 user mailbox to a shared mailbox: prerequisites, conversion in the admin center, licensing rules (50 GB limit), permissions, offboarding cleanup, and common pitfalls.

Updated Oct 6, 20267 min readmicrosoft 365exchangeshared mailboxlicensingoffboarding

Converting a User Mailbox to a Shared Mailbox

Step-by-Step: Converting via Microsoft 365 Admin Center

Check Prerequisites: Ensure the mailbox meets conversion requirements. It should be an active user mailbox with an Exchange license assigned (unlicensed mailboxes won’t show the Convert to shared mailbox option). Also verify the mailbox’s data size is within 50 GB if you plan to remove the license later. Do not delete the user’s account at any point during this process.

Navigate to Users: Sign in to the Microsoft 365 Admin Center and go to Users > Active users. From the active users list, find and select the user whose mailbox you want to convert.

Open Mail Settings: In the user’s detail pane, click on the Mail tab (or Mailbox section). You should see an option labeled “Convert to shared mailbox.” Click this Convert to shared mailbox button.

Confirm Conversion: A confirmation dialog will appear explaining that all of the user’s email and calendar data will be retained in the new shared mailbox. To proceed, click Convert (confirm the action). The admin center will process the request; within a short time you should see a success message indicating the mailbox was converted to a shared mailbox.

Post-Conversion Actions: After conversion, the mailbox will appear as a shared mailbox in your organization. Now:

Remove License if Applicable: If the mailbox is under 50 GB, you can remove the license from the user’s account to free up that subscription cost. (Shared mailboxes do not consume a license up to 50 GB of content. If the mailbox was larger than 50 GB or had an archive or legal hold, see Precautions below about licensing.)

Do NOT Delete Account: Keep the user account intact (albeit unlicensed). The shared mailbox depends on the original user account as an anchor object. Deleting the account will orphan the mailbox.

Block Sign-In: For security, especially if this conversion is for a former employee, block the sign-in for the associated user account (or reset its password) so nobody can use those credentials. Shared mailboxes aren’t meant to be logged into directly.

Add Members (Assign Access): In the admin center, go to the Groups > Shared mailboxes section (or use the Exchange admin center) to add members to the new shared mailbox. Grant the appropriate users Full Access permission so they can open and read the mailbox, and Send As (or Send on Behalf) permission if they should send emails as this mailbox. Only internal users in your organization can be added as members to a shared mailbox.

Inform Users to Reconfigure (if needed): Users who are given access may need to restart Outlook or add the shared mailbox manually to their Outlook profile. In many cases, Outlook auto-maps the shared mailbox for users with Full Access, but if not, provide instructions for opening the shared mailbox in Outlook or Outlook on the web. This ensures they can see the mailbox and its calendar. (On mobile, users can add the shared mailbox via the Outlook app).

Precautions and Considerations (Before & After Conversion)

Converting a mailbox is straightforward, but several important considerations ensure a successful transition and continued email functionality:

Mailbox Size & Licensing: After conversion, shared mailboxes can hold up to 50 GB of data without a license. If the converted mailbox is larger than 50 GB or if you plan to enable features like In-Place Archiving or Litigation Hold on it, you must assign a license (e.g. Exchange Online Plan 2) to that shared mailbox to avoid disruption. With an Exchange Online Plan 2 license, shared mailboxes can grow up to 100 GB and support archiving and legal holds. Tip: If the mailbox is near 50 GB and you want to remove the license, consider cleaning up or exporting old emails to get under the limit before removing the license.

Account and Login: The shared mailbox will retain the original user account (just without a license and typically with sign-in disabled). Remember that a shared mailbox does not have its own login that people use interactively. Users access it through their own accounts via the permissions you grant. Microsoft recommends blocking the sign-in on the shared mailbox’s associated account to prevent any direct login attempts. (When you created or converted to a shared mailbox, no password reset was required; if you don’t disable sign-in, the old username/password would still grant direct access, which is usually not intended.)

Permissions and Access: Assign permissions to the shared mailbox immediately after conversion. At minimum, grant Full Access to relevant users so they can open and read email from the mailbox, and Send As rights if they need to send emails as that shared address. This is done in Exchange admin center or via the Shared mailboxes section in the Microsoft 365 admin center by editing the mailbox’s members. Only users within your organization can be granted access; you cannot add external (e.g., Gmail or other tenant) users as shared mailbox members. If external sharing is required, consider alternate solutions (like a distribution group or M365 Group).

Data Retention and Holds: All emails and calendar items remain intact through the conversion. If the user’s mailbox was subject to any Litigation Hold or eDiscovery hold, note that shared mailboxes require a suitable license for holds to remain in effect. Before conversion, consider removing the hold temporarily or be prepared to assign an Exchange Plan 2 license to the shared mailbox to keep it on hold. Always double-check that any compliance requirements (e.g. retention policies) are still enforced after conversion – you may need to reapply certain policies to the mailbox now that it’s shared.

Email Functionality and Client Setup: After adding users to the shared mailbox:

Users can access the shared mailbox in Outlook (Desktop or Web) by expanding the mailbox in their folder list or by opening it as an additional mailbox. They can also add it in mobile Outlook apps. If a user doesn’t see the shared mailbox, they might need to manually add it via Outlook’s account settings.

Users with Send As or Send on Behalf can compose emails from the shared address (e.g., sending as “support@company.com”) provided those permissions have replicated. If a user encounters a “not authorized to send on behalf” error immediately after being added, it may be a replication delay – wait some time and try again.

The shared mailbox also includes a shared calendar. Members with access can schedule meetings on its calendar just as they would on a personal calendar.

Post-Conversion Cleanup: If the conversion was part of an offboarding (employee departure):

Double-check that auto-forwarding or redirect rules that might have existed on the mailbox are still appropriate (or disabled if not needed).

Remove the converted user from any distribution groups or Teams that were tied to their user identity, if those are no longer relevant. (The shared mailbox account typically won’t be used as a normal user identity anymore.)

Communicate the new shared mailbox address to any internal or external contacts if the address is meant to replace the individual’s address for correspondence (often the email address remains the same as the old user’s, so this may not be necessary).

Common Pitfalls to Avoid:

Missing Convert Option: If you don’t see “Convert to shared mailbox” in the admin center for a user, it’s usually because the account does not have an active Exchange license. Assign a license, wait a short while, and the option should appear.

Deleting the User Account: As emphasized, do not delete the user’s account after conversion. That will cause the shared mailbox to lose its connection. If the goal was to free up an Office 365 license, just remove the license assignment (the account will then appear as unlicensed, but the mailbox remains as shared).

Not Assigning Permissions: Converting the mailbox doesn’t automatically give anyone access to it (except global/Exchange admins). Failing to grant Full Access to at least one user means nobody can actually use the mailbox. Always add the intended users or a security group as members of the shared mailbox.

Forgot to Disable Sign-In: If an ex-employee’s mailbox is converted and you don’t disable their login, they could potentially still access the mailbox (now shared) with their old password. Prevent this by blocking sign-in on the account.

Oversized Mailbox without License: Removing the license on a >50 GB mailbox will render it inaccessible for sending/receiving once it exceeds the limit. Make sure to reduce size or keep a license on large mailboxes.

Expecting External Access: Remember that shared mailbox access is limited to your organization’s users – you cannot directly share it with external users or customers. To allow external parties to reach the shared mailbox, they can still send emails to its address; they just can’t log in or be true members of it.

Related articles