Content reviewed: 12 October 2026

A basic shared mailbox can hold up to 50 GB without its own licence. People accessing it need a licensed Exchange Online mailbox. Additional capacity, archiving and advanced features have separate requirements. A setting being available in the admin centre is not proof of entitlement. Microsoft explains the baseline in its shared mailbox overview.

Separate three different requirements

Handling current correspondence, storing older messages and preserving content are different tasks. Your organisation may need all three, but each requires an appropriate feature and entitlement.

The primary mailbox is the team’s working space. An online archive is additional mail storage. Retention and holds determine how content is preserved or removed. An archive alone does not decide which records the business must keep or for how long. Moving messages to the archive does not increase the primary mailbox’s limit either.

Before choosing a licence, ask whether you need a larger primary mailbox, space for older messages, protection against deletion, or a combination. “We want to archive everything” is too vague to turn into an order.

Decision guide

Scenarios and checks
RequirementWhat to checkWhat it means
Shared correspondence up to 50 GB without additional featuresLicences of the people accessing itThe mailbox generally needs no separate licence
Primary mailbox above 50 GBAssignment of Exchange Online Plan 2Plan 2 supports a 100 GB primary mailbox limit
Online archiveSpecific archive entitlement and assigned licenceAn enabled archive is not proof of free entitlement
Auto-expanding archivePlan 2, or Plan 1 with Exchange Online ArchivingAssess it separately from primary mailbox capacity
Litigation HoldPlan 2, or Plan 1 with the appropriate archiving add-onPreservation requirements change the licensing assessment
Advanced protection and complianceRequirements of the specific featureThe basic shared mailbox exception is insufficient

This table follows the Exchange Online limits and their notes. The notes matter: they distinguish primary storage, archive storage and feature entitlements.

Why the admin centre may not prove entitlement

Check the actual quota and its origin. Microsoft notes that older unlicensed shared mailboxes created before July 2018 may technically have 100 GB. A displayed quota therefore does not prove a current entitlement to 100 GB without a licence. Base the decision on assigned products and current rules, rather than the capacity shown in the admin centre alone.

Do not compare your tenant with another administrator’s screenshot alone. Mailbox history, older configurations and subscriptions may differ. If documentation and service behaviour appear inconsistent, ask support a precise question: which product covers this particular archive? The answer should reference a rule, rather than merely confirm that the setting works.

Keep four pieces of evidence separate

Evidence for the decision
FieldWhat it showsWhat it does not prove
SharedMailbox typeThe resulting type after conversionThat a licence can be removed despite archives, holds or greater capacity.
Primary mailbox sizeThe amount of mail currently storedEntitlement to any displayed quota.
Archive size and quotaThe state of additional mail storageImmediate access to 1.5 TB or unlimited growth.
Assigned product and service planPart of the licensing and technical evidenceCorrect configuration or successful message movement.

Auto-expanding is not instant extra space

Auto-expanding archives have a 1.5 TB ceiling including Recoverable Items and support growth of no more than 1 GB per day. Additional space is provisioned incrementally and can take up to 30 days. Do not promise that enabling it instantly fixes a full mailbox or supports a rapid bulk import. The primary mailbox remains separate; archive expansion does not change its quota.

The enablement instructions say auto-expanding cannot subsequently be turned off, and an inactive mailbox using it cannot undergo the normal inactive-mailbox recovery or restore process; data instead requires export and import. This does not mean messages in an active shared mailbox cannot be read. Review future preservation, recovery and migration plans before enabling it. Keep enablement status separate from the assignment of a qualifying licence.

One mailbox archive is not a company archive

The Exchange limits notes expressly prohibit using one mailbox archive to store mail from multiple users or entities. Do not create a shared mailbox to collect all employees’ messages for archiving through Cc, Bcc or transport rules. The team’s own correspondence received and sent as invoices@ is a different scenario. Preserving mail across the organisation needs its own design and licensing assessment.

Sorting work folders and correspondence on an office desk

Convert a departing employee’s mailbox

Conversion is useful when colleagues need to continue handling the correspondence. It is not an automatic solution for preserving all of a former employee’s work data.

  1. Check the primary mailbox size, archive status and active preservation rules.
  2. Decide who will use the converted mailbox and for what purpose.
  3. Convert it and verify the resulting mailbox type.
  4. Assign access to named colleagues and block direct sign-in to the original account.
  5. Test incoming mail, access and sending through their own accounts.
  6. Only then assess licence removal against capacity and feature requirements.

Microsoft provides a user-to-shared mailbox conversion procedure. In a hybrid environment, also check where the mailbox type and related attributes are managed.

Keep the account anchoring the shared mailbox after conversion: Microsoft explicitly warns against deleting it. The user mailbox should be licensed before conversion. Conversion itself may not block the old credentials, so block direct sign-in. In hybrid environments, check the authoritative management source as well, to prevent synchronisation from reversing the mailbox type.

Access and sending are different permissions

Distinguish opening the mailbox, sending as the shared address and sending on behalf of it. Recipients see the difference. A message from invoices@ is different from a colleague’s message sent “on behalf of invoices@”.

Prepare two tests: a colleague opens an incoming message, then sends a reply in the required way. Folder access alone does not verify the entire workflow. Agree where the team will find sent replies and how it will know a customer has already received an answer.

Having everyone sign in with one shared password makes this harder to manage. It becomes difficult to identify who handled content, and every departure creates another shared-access issue. Use personal accounts and delegated permissions.

Hypothetical example: a 72 GB sales mailbox

A hypothetical sales mailbox holds 72 GB in its primary area. The team uses it daily and needs to find recent enquiries quickly. Converting it to a shared mailbox does not make it eligible for the unlicensed 50 GB allowance.

The administrator must make two separate decisions: the required primary capacity and the way older mail will be handled. If archiving is chosen, the team needs to know which messages move and how to find them later. Licensing and configuration must cover both requirements.

Preservation of contractual correspondence also belongs in the decision. The sales manager defines the content needed, the responsible person confirms preservation rules, and IT checks implementation. Random bulk moves of messages should not replace the organisation’s rules.

In the 72 GB model, Plan 1 plus the archiving add-on alone does not supply the required 100 GB primary capacity. If all 72 GB must stay in the primary mailbox, assess Plan 2 entitlement. Moving mail to an archive requires the appropriate archive licence, verified functionality and preservation rules; do not delete data simply to meet the threshold for licence removal.

Prevent the mailbox from filling up

Monitor its size, growth and owner. Alert the owner while a change can still be planned, rather than after customer mail is rejected.

  • Distinguish large attachments from ongoing growth.
  • Check for unnecessary automated copies arriving in the mailbox.
  • Verify that archiving actually runs.
  • Discuss every planned preservation change with the content owner.
  • Repeat incoming and outgoing mail tests after a change.

Do not promise savings simply because a licence is removed. If the seat remains part of a paid commitment, changing its assignment may not reduce the current invoice.

Frequently asked questions

Does every team member need a licence?

People accessing the shared mailbox need their own licensed Exchange Online mailbox. The exception for the shared mailbox does not cover its users.

Can an archive give us more space completely free?

An available switch does not establish that. Check archive entitlement, the assigned product and capacity conditions. Auto-expanding archives have explicit requirements.

Is a shared mailbox suitable as the entire company’s archive?

Not as a common archive for copies of every employee’s mail. Microsoft prohibits using one entity’s archive that way. Archiving the shared address’s own correspondence is a different case.

When can we remove the original licence after conversion?

After verifying the resulting mailbox, its capacity, archive, hold and other features. Conversion and licence removal are separate changes.

Does auto-expanding mean unlimited storage?

No. The limit is 1.5 TB including Recoverable Items, growth is limited and new capacity can take up to 30 days. It does not enlarge the primary mailbox.

Can I delete the original user account after conversion?

Not in this workflow. It anchors the shared mailbox. Block direct sign-in and assess licensing separately.

Prepare the information for a licensing review

Record the exact mailbox type, primary and archive sizes, assigned products, active preservation features and roles with access. These details support a much more reliable decision than the general question “are shared mailboxes free?”