Content reviewed: 12 October 2026
After mailbox conversion, a former employee’s licence can be removed only if the resulting state meets the unlicensed shared-mailbox conditions. Check primary size, archive, holds and other features. While the mailbox remains shared, keep its user account as the anchor and block direct sign-in. The Microsoft procedure requires a licence during conversion.
Choose the required outcome first
| Post-departure need | Possible state | Key condition |
|---|---|---|
| Colleagues keep receiving and processing email | Shared mailbox | Delegated access, retained account and appropriate licensing |
| Short handover of unfinished work | Temporary shared mailbox | Owner, review date and approved retention plan |
| Preservation only for eDiscovery | Inactive mailbox | Supported hold or retention applied before account deletion |
An inactive mailbox cannot receive new email and is not a regular mailbox for a successor. Microsoft’s creation procedure requires correctly licensed preservation before deleting the account and waiting for the settings to apply. The Exchange licence becomes available after account deletion. This differs from conversion to an operational shared mailbox; accidental deletion is not a substitute.
Under the standard retention policy described in this guide, the period runs from the item’s original received or created date, not automatically from departure. A hypothetical six-year-old message under seven-year retention therefore need not remain for another seven years after offboarding; where receipt is the reference date and no other hold applies, roughly one year may remain. Translate “keep seven years after departure” into a specific supported configuration and test older messages. Microsoft explains the reference date and retention application sequence.
Measure the primary mailbox and archive separately
In a hypothetical example, the primary mailbox contains 32 GB and the online archive 80 GB. The 50 GB unlicensed shared-mailbox limit is not evaluated by adding those figures. The primary mailbox is below the ceiling, but archive availability and capacity still require qualifying entitlement. Deciding from 32 GB alone would overlook the archive.
| Requirement | Microsoft guidance | What to verify |
|---|---|---|
| Primary mailbox up to 50 GB without additional requirements | May run without its own licence | Size and other features used |
| 100 GB primary ceiling | Exchange Online Plan 2 | Licence assigned to the shared mailbox |
| Expanded and auto-expanding archive | Plan 2 or Plan 1 with Exchange Online Archiving | Archive entitlement and actual state |
| In-Place / Litigation Hold | Plan 2 or Plan 1 with Exchange Online Archiving | Licensing and applied hold |
| Advanced Defender or Purview scenario | Additional licences may be required | Exact feature and its licensing rules |
The table follows shared-mailbox requirements and the conversion guide. See our separate shared-mailbox licence and archive guide for archive comparisons. Offboarding should check intended use rather than the bundle currently assigned.
Conversion alone does not block former-user access
Microsoft warns that the original username and password may continue to work after conversion if credentials remain unchanged. The shared account is not intended for direct sign-in. Its recommended state is to keep sign-in blocked. Former-user access and active sessions must be addressed through the leaver process before handing over content.
Colleagues use their own licensed Exchange Online accounts with delegated permissions. Do not share the former password. Conversion preserves email, calendar and inbox rules, so inspect forwarding and automatic rules too. They may reflect the former role and be unsuitable for the new use.
A sequence with verifiable evidence
- 01
Secure access and record the state
Block former-user access under your internal process; record size, archive, holds, rules and ownership
- 02
Confirm the target state
Choose operational shared or inactive preservation; define the retention purpose and duration
- 03
Convert while licensed
For the shared route, retain the licence during conversion and verify the resulting mailbox type
- 04
Delegate successor access
Use their own licensed accounts; retain the shared-mailbox anchor account with direct sign-in blocked
- 05
Test operation and content
Verify inbound email, successor access, sending, rules, archive and required preservation
- 06
Adjust licences and schedule review
Remove only entitlements not required by the target state; record a review date and owner
If the licence or account was already removed
For a prematurely removed licence, the Microsoft guide says to assign it again so conversion can proceed. For a deleted account, use the supported recovery procedure and verify mailbox availability. Do not promise recovery after any historical deletion. In hybrid environments, also inspect the on-premises object and synchronisation; a cloud-only change may not complete the process.
Close the ticket only with a tested result and a traceable retention decision. Converting the mailbox type is one technical step. Handover, permissions and preservation of required records each need verification and ownership.
Frequently asked questions
Can I remove the licence before conversion?
Microsoft requires an assigned licence for conversion. Assess removal after verifying the target state.
Is primary size below 50 GB enough?
No. Check archive, holds and other features separately; they may require licensing.
Can I delete the converted shared-mailbox account?
Not while it must operate as shared. The account anchors it. Account deletion for an inactive mailbox belongs to a different, prepared retention procedure.
Does conversion alone prevent the former employee signing in?
No. Secure sign-in and sessions separately; keep the shared account blocked for direct sign-in.








