Shared Mailboxes Don't Need Licenses — Here's What That Mistake Costs

Here's one of the cheapest wins in Microsoft 365 licensing: shared mailboxes don't require a license as long as they're under 50 GB and don't need archiving, litigation hold, or their own sign-in. Yet almost every tenant we look at is paying full user licenses for at least a few of them.

How licensed shared mailboxes happen

Nobody decides to waste this money. It accumulates through three ordinary paths:

1. The departed employee conversion

An employee leaves. Their mailbox is converted to shared so the team keeps access to history — good practice. But the conversion doesn't remove the license, and the "remove license after conversion" step gets skipped. The account now sits disabled, shared, and paying $12.50–$36 a month forever.

2. The "info@" that started as a user

Someone created info@, accounts@, or support@ as a normal licensed user years ago because that was the quick way to do it. It behaves like a shared mailbox, several people have the password (its own security problem), and it's been billing as a full seat the whole time.

3. The over-cautious conversion

An admin read that shared mailboxes "sometimes need licenses" and assigned one to be safe. The actual rules are narrow — a license is only required if the mailbox:

• exceeds 50 GB, or
• needs an archive (Exchange Online Plan 2 or archiving add-on), or
• needs litigation hold, or
• is signed into directly (which you should block anyway)

What it costs

Each wrongly licensed shared mailbox costs whatever SKU it holds: $6/mo (Business Basic) to $36/mo (E3) or more. A mid-size tenant with 10 legacy conversions on Business Standard is burning $1,500/year on mailboxes that would work identically for free.

How to find them

In PowerShell: Get-Mailbox -RecipientTypeDetails SharedMailbox then cross-reference against Graph license assignments — any hit is a candidate. Check size (Get-MailboxStatistics) and hold status before removing the license.

SeatPrune does this join automatically: its shared-mailbox report lists every licensed shared mailbox, its size, whether anything actually blocks license removal, and the monthly saving. It's routinely the first finding new users act on because it's zero-risk: nothing about the mailbox changes.

The fix (safe order of operations)

1. Confirm the mailbox is under 50 GB and has no litigation hold or archive requirement
2. Ensure direct sign-in is blocked (disable the account — shared mailbox access works via delegation, not sign-in)
3. Remove the license
4. Add "remove license after mailbox conversion" to your offboarding runbook — this is where most of these come from, and it pairs with cleaning up disabled accounts that still hold licenses

This is the rare cost optimisation with no trade-off. The mailbox keeps working. You just stop paying for it.