Does a Shared Mailbox Need a Microsoft 365 License?

Does a shared mailbox need a license? No, not by default. Microsoft 365 lets you create a shared mailbox and hand it to a whole team without buying it a seat, and it stays that way up to a documented size ceiling.

The catch is that the ceiling is real, and three other things quietly cross the same line: an archive, a legal hold, and direct sign-in. Each one needs the mailbox itself to carry a license, not just the people reading it. This is the part finance usually finds out about during an audit, after someone has already turned a feature on.

A support inbox that's grown past 50 GB of attachments, a legal team asking for a hold during a dispute, or an admin who wants to log into the mailbox directly instead of relying on automapping — any one of those is enough on its own to trigger a license requirement, regardless of the other two.

Everything below is checked against Microsoft's own Exchange Online service description, current as of August 2026, so you can point IT or a vendor at the same numbers.

The short answer#

A shared mailbox does not require its own Microsoft 365 license to exist, send, or receive mail, and it is capped at 50 GB while unlicensed. The people who open it still need their own Exchange Online license — that requirement never goes away — but the mailbox object itself is free at that size.

Four things push it into needing a license of its own:

• Size — past 50 GB, the mailbox stops accepting mail until it's under quota or licensed for 100 GB
• In-place archive — a separate archive mailbox for older mail requires a license on the shared mailbox
• Litigation hold — preserving mail for legal or compliance reasons requires a license on the shared mailbox
• Direct sign-in and advanced features — logging in as the mailbox itself, or turning on Defender for Office 365, Purview eDiscovery, or automatic retention policies, all require licensing it

Before you start#

You'll need Exchange administrator or global administrator access to check and assign this correctly — a user who only has access to the shared mailbox itself can't see its license or size status.

Two things are worth confirming before you touch anything: the mailbox's current size, and whether anyone has actually asked for an archive or a hold, versus just wanting more headroom.

• Admin role: Exchange administrator or global administrator in the Microsoft 365 admin center
• Current size: Admin center > Active mailboxes usage report, or the Get-EXOMailboxStatistics PowerShell cmdlet
• A real compliance requirement, not a guess: check with legal or records management before licensing for hold or archive
• Your existing license inventory: an unused Exchange Online Plan 2 or E3/E5 seat is often already sitting idle from an offboarded employee

What the license actually costs to assign#

An Exchange Online Plan 2 seat is billed the same way whether it's sitting on a person or a shared mailbox — a recurring per-license charge, not a one-time upgrade fee. Assigning it to a mailbox nobody is actively using for archive or hold is the same ongoing cost as assigning it to an idle user account.

That's why the license-inventory check matters more than it looks. Most organizations that have been running Microsoft 365 for a few years already have at least one Plan 2 or E3/E5 seat freed up by an offboarded employee, sitting unused in the license pool. Reassigning that seat to a shared mailbox that genuinely needs it costs nothing extra at the next invoice — buying a new one when a freed seat already exists is the cost this whole check is meant to catch.

Steps to check and license a shared mailbox correctly#

This is the order that avoids the two most common mistakes: licensing the wrong object, and licensing before confirming the license actually solves the problem.

1. 1

   Check the mailbox's current size

   In the Microsoft 365 admin center, open Active mailboxes usage, or run Get-EXOMailboxStatistics against the mailbox in PowerShell. If it's under 50 GB and nobody needs an archive or hold, you're done — it doesn't need a license.

2. 2

   Decide which of the four triggers actually applies

   Size, archive, hold, or direct sign-in. "We might need it eventually" isn't a trigger — licensing ahead of an actual requirement is exactly how idle Plan 2 seats accumulate.

3. 3

   Assign the license to the mailbox object itself

   In the admin center, find the shared mailbox under Teams & groups > Shared mailboxes, or Recipients > Mailboxes in the Exchange admin center, and assign an Exchange Online Plan 2 license (or any Microsoft 365 E3/E5 seat) directly to it — not to the staff who use it.

4. 4

   Turn on the feature the license unlocked

   For an archive, enable it in the Exchange admin center under mailbox features. For a hold, place it through the Microsoft Purview compliance portal. Give the license up to 24 hours to propagate before either option appears reliably.

5. 5

   Confirm the change took, and record it

   Recheck the size limit warning has cleared, or that the archive/hold shows active in the compliance portal. Note which shared mailboxes now carry a paid license — this is the list IT gets asked for at renewal time.

Which Microsoft 365 plan actually unlocks 100 GB#

"I already pay for Microsoft 365" doesn't answer the question, because which plan you pay for changes what a shared mailbox gets for free. Business Basic, Standard, Premium, and Enterprise E1 all include Exchange Online Plan 1-equivalent mailboxes for users, and none of them include Plan 2 on a shared mailbox by default.

E3 and E5 are the exception: they already bundle Exchange Online Plan 2, so assigning any E3 or E5 seat to a shared mailbox is enough — you don't need a separate Plan 2 purchase on top of it.

The Exchange Online Archiving add-on is the other route worth knowing about, because it's sold and billed separately from Plan 1 itself, as its own recurring line item. It gets you the archive and the hold without a full Plan 2 upgrade, which is usually cheaper if size was never the actual problem — the mailbox is fine at 50 GB and the only reason it needed licensing was a hold request from legal.

What to do when it doesn't work#

Most of the trouble here isn't Microsoft's rule being unclear — it's the license landing on the wrong object, or a real compliance need getting confused with a size complaint.

Assigned Plan 2 but the mailbox still shows the 50 GB warning: give it up to 24 hours to propagate. If it's still capped after that, check whether the license actually landed on the shared mailbox's own account rather than on the admin who assigned it, or on a distribution group instead of the mailbox object.

Archive or litigation hold options are greyed out in the Purview compliance portal: open the license details for that specific mailbox in the Microsoft Entra admin center and confirm the SKU includes Plan 2 service plans, not just a friendly bundle name. Some plans are marketed as "includes Exchange Online" while actually shipping Plan 1.

Removed the license after converting a mailbox to shared, and the size warning came back: the mailbox likely still holds more than 50 GB of mail. Exchange won't let an unlicensed mailbox stay above the free ceiling, so either trim the data first or keep the license until usage drops under 50 GB.

Licensed the mailbox but still can't sign in to it directly: shared mailboxes are created with sign-in blocked by default on a system-generated password. An admin has to explicitly reset that password and enable sign-in in Microsoft Entra ID — the license alone doesn't turn this on.

Assigned a license, but it went to the wrong place entirely: a common mistake is licensing the manager who oversees the shared mailbox rather than the mailbox object itself. That manager's own mailbox gets the upgrade, and the shared mailbox stays capped at 50 GB with no hold or archive available. Check the recipient list in the Exchange admin center, not the user list, to confirm which object actually received the license.

Several shared mailboxes all need an archive, but the budget only covers a couple of extra seats: license the ones with an active legal or records-retention requirement first, and revisit the rest at the next audit. A mailbox that merely might need it later doesn't need it now — that's the same discipline as step two of the process above, applied across a whole license pool instead of one mailbox.

A faster way to run a shared inbox once it's licensed#

Getting the license right solves the compliance side. It doesn't solve the coordination side: several people replying from one address, no reliable record of who already answered a thread, and an admin left guessing which shared mailboxes actually earned their license at the next renewal.

AI Emaily connects to a shared mailbox once and routes each thread to an owner instead of leaving it to whoever opens it first. In Copilot mode, replies are drafted for approval rather than sent automatically, and every send is logged — so the audit trail this post keeps pointing at exists without anyone building a spreadsheet for it. We build AI Emaily.

It doesn't change what Microsoft requires you to license — that rule is unaffected. It changes what happens inside the mailbox once the license question is settled.