Can you remove a leaver's Microsoft 365 license and keep their mailbox?

A leaver's mailbox may no longer need its own license after conversion to a suitable shared mailbox, but removing a license and deleting the identity are different decisions. Microsoft says conversion preserves existing email and calendar information and requires retaining the account that anchors the shared mailbox. Microsoft's conversion guidance.

The practical question is whether authorized colleagues can retrieve the records they need after the change. This guide concerns Exchange Online mailboxes, not the rest of a departing employee's files or services. Sources were checked on October 21, 2026. No mailbox, license, identity or retention policy was changed.

Decide what “keep the mailbox” means

Write down which outcome is required before choosing an administrative action:

Needed outcome	Decision to investigate with the administrator
Colleagues must read historical mail and handle new messages	Shared mailbox with appropriate delegation and retained identity
Records must remain available through an approved preservation process	Retention and retrieval arrangements, including an inactive mailbox where appropriate
Only selected messages need an approved archive	Export scope, readable attachments, access controls and a tested retrieval process
The former employee must lose access	Offboarding access controls, separately from the mailbox's storage and license state

An inactive mailbox is not a shared inbox. Microsoft documents access through authorized eDiscovery search/export and says inactive mailboxes cannot receive new mail. The route requires correctly licensed preservation to be applied before deletion. Microsoft's inactive-mailbox documentation. Have the organization's responsible records or compliance owner decide requirements; this article does not determine legal retention duties or prescribe a hold.

Do not simply unlicense an ordinary mailbox and assume it becomes an accessible archive. Microsoft's leaver guidance describes deletion consequences after license removal. Microsoft's offboarding overview. Establish the chosen preservation route first rather than relying on a recovery window.

Branch on cloud-only versus synchronized identity

Ask the administrator to record the identity's source of authority, mailbox location and conversion procedure. “The email is in Microsoft 365” does not answer all three.

Cloud-only identity: Microsoft's standard conversion instructions require the user mailbox to be licensed before conversion and explicitly say not to delete its account afterward. Microsoft's user-to-shared conversion. This is a route to evaluate for shared access, not a universal sequence for every leaver.

Directory-synchronized identity: Microsoft's offboarding guidance says deletion and restoration of synchronized users are handled in the local Active Directory service. Microsoft's Active Directory distinction. That is not an instruction to delete the on-premises account when the shared mailbox still needs its anchor.

Hybrid Exchange management: Microsoft requires on-premises Exchange management tools and distinguishes a remotely provisioned mailbox from one previously migrated to Exchange Online; the latter also needs the cloud mailbox object updated. Microsoft's hybrid conversion requirements. Stop if the administrator cannot confirm the applicable path or whether synchronization will preserve the intended state. Do not improvise by deleting the account or moving it outside synchronization scope.

Check the conditions before removing a license

A shared mailbox can hold up to 50 GB without its own license; increasing the primary mailbox limit to 100 GB requires Exchange Online Plan 2. Archiving, litigation hold and certain advanced features have additional licensing requirements. Delegates need their own licensed Exchange Online mailboxes. Microsoft's shared-mailbox licensing conditions.

Have the administrator inspect actual primary and archive usage, active holds, retention settings and dependent features. Obtain confirmation of the required licenses for that combination. Do not delete messages, disable a hold or drop a required feature merely to fit an unlicensed limit. Keep enough capacity for the new mail the mailbox is expected to receive.

Shared-mailbox sign-in should remain blocked; colleagues access it through their own identities. Microsoft's shared-mailbox access rules. Conversion is not proof that the former employee's access has been revoked. Have the administrator complete and verify the organization's offboarding controls separately.

Delegation also needs precision. Full Access permits reading and modifying mailbox contents but does not itself grant sending. Send As and Send on Behalf serve different sending needs. Microsoft's delegation permissions. Give the successor only the access the job needs, plus a named backup. Full Access is not a read-only archive permission.

UNEXECUTED pilot: a dummy leaver and an archive retrieval

The following rehearsal is proposed, not tested. An authorized administrator should use a dedicated dummy identity and an approved test mailbox matching the real identity-management pattern. Keep the actual employee's account unchanged during the rehearsal. If the test cannot reproduce the relevant archive, hold or synchronization configuration, mark that portion untested and stop the corresponding production change.

1. Define a retrieval set. Put ten clearly labeled test messages in several folders, including two attachments, a sent reply and a calendar item. Designate one thread as the historical record to retrieve. Record item identifiers, folder locations and expected contents. Use no personal or customer data.
2. Record the starting state. Capture license assignments, mailbox type, sizes, delegation, sign-in status and identity source. Name the administrator responsible for recovery. Confirm that the required license is available if the test must return to a user mailbox.
3. Rehearse the selected route. For shared access, the administrator follows the applicable Microsoft conversion guidance while retaining the anchor identity. They confirm completion, delegation and blocked direct sign-in before considering removal of a license that is no longer required. In a synced environment, verify the intended state again after synchronization.
4. Retrieve as the successor and backup. Each uses their own account to find the designated thread, open both attachments and inspect the calendar item. If continued receiving or sending is required, test a dummy inbound message and only the approved sending permission. Record client, date, result and failure details.
5. Test the separate archive. If an export or preservation route is part of the plan, its authorized operator must find the same designated items through that route. Record missing folders, unreadable attachments and required software or permissions. Success in Outlook does not prove the archive works.
6. Rehearse rollback on the dummy. Return the test to its documented starting arrangement and repeat retrieval. Microsoft's shared-to-user route includes conversion and license assignment; the administrator must adapt it to the identity environment. Microsoft's reversal guidance. Record timing and any remaining differences.

For an inactive-mailbox proposal, have the responsible administrator design a separate dummy preservation and retrieval test under the approved policy. The shared-mailbox rehearsal does not validate that route, and this checklist does not authorize deletion.

Stop conditions and the remaining bill

Keep the current license arrangement pending administrator confirmation if identity authority is unclear, a required hold or archive entitlement is unresolved, synchronization changes the mailbox state, or the backup cannot retrieve the selected records. Also stop if the former employee can still sign in or a required incoming-mail path fails. Assign an owner and review date to every unresolved item.

Once technical acceptance is documented, distinguish an available license from a canceled purchase. Microsoft's shared-mailbox instructions explicitly warn that removing the assignment leaves you paying until the subscription quantity is reduced. Microsoft's license-removal note.

Compare your current invoice with an actual seat-reduction or renewal quote over the same term. Calculate current organization charge − remaining organization charge, including retained delegate licenses, any necessary mailbox/archive licenses and replacement costs once. Track administration and archive maintenance separately. If the purchased quantity cannot fall yet, current contractual savings are zero even though the license can be reassigned.

Record the confirmed decision in the subscription audit, and use the cancellation checklist for the billing follow-through. Current OneLessTool options are on pricing.