Fix it now
554 5.2.2 with STOREDRV.Deliver means the destination mailbox is past the quota at which it stops receiving. It is a permanent rejection, so nothing is queued and nothing arrives later. Get the mailbox back under quota, then have senders try again.
Get-MailboxStatistics -Identity user@contoso.com | Select TotalItemSize,ItemCount
Get-Mailbox -Identity user@contoso.com | Select *Quota*
Get-MailboxFolderStatistics -Identity user@contoso.com | Sort FolderSize -Descending | Select Name,FolderSize -First 15
- Compare TotalItemSize with ProhibitSendReceiveQuota. If it is at the ceiling, the code is telling the truth and the mailbox needs space.
- Read the folder list. Sent Items and Recoverable Items are where the volume usually is, and neither is the folder the user thinks of.
- Empty Deleted Items and remove the largest attachments, then re-run the statistics rather than assuming.
- If the plan includes an archive, turn it on with
Enable-Mailbox -Identity user@contoso.com -Archive, apply a retention policy that moves old mail into it, then runStart-ManagedFolderAssistant -Identity user@contoso.com. - If the address is a mail-enabled public folder rather than a mailbox, the quota to check is the public folder post quota, not a mailbox quota.
A quota set below the plan maximum by a script or a previous administrator produces this at a size the licence should easily allow. Check before you buy anything.
If mail is being accepted again you can stop here. If not, the next section explains which of the several 5.2.2 variants you actually have.
Why it happens
Every Exchange Online mailbox has a series of thresholds rather than one. There is a warning level, where the user is told they are running out of room. There is a prohibit-send level, where they can still receive but cannot send. Finally there is prohibit-send-and-receive, and that is the one that produces 554 5.2.2 to everyone who writes to them. The mailbox is not damaged and nothing has been deleted; it is simply closed to new mail.
The diagnostic text matters more than the number, because 5.2.2 covers two different failures with opposite fixes. 554 5.2.2 mailbox full; STOREDRV.Deliver.Exception:QuotaExceededException.MapiExceptionQuotaExceeded is a delivery refusal: the recipient’s mailbox, or a public folder’s post quota, is full. 554 5.2.2 mailbox full; STOREDRV.Submission.Exception:QuotaExceededException.MapiExceptionShutoffQuotaExceeded is a submission refusal: the sender’s own mailbox is past its shutoff quota, so the message cannot be written to Sent Items and therefore cannot be sent at all.
And 5.2.2 without the STOREDRV detail is a third thing again. Microsoft’s Exchange Online NDR reference lists 5.2.2 as “Submission quota exceeded”, meaning the sender passed the recipient rate limit or the message rate limit. That is a sending-limit problem with nothing to do with how full anybody’s mailbox is, and cleaning out the recipient will not touch it.
The ceiling itself comes from the licence. Exchange Online Plan 1, Business Basic, Business Standard, Business Premium and Office 365 E1 give a 50 GB primary mailbox. Exchange Online Plan 2 and Microsoft 365 E3 and E5 give 100 GB. Kiosk and F3 give 2 GB. Set-Mailbox can lower a quota below the plan maximum, or restore one that was lowered, but it cannot take a mailbox past what the licence provides.
The mailbox is genuinely full and there is no archive
You have this one if TotalItemSize is at the plan ceiling and the mailbox has no archive enabled.
- Enable the archive if the plan includes one:
Enable-Mailbox -Identity user@contoso.com -Archive. - Apply a retention policy that moves items older than a chosen age into the archive.
- Trigger it now with
Start-ManagedFolderAssistant -Identity user@contoso.comrather than waiting for the service’s own schedule. - Confirm the primary mailbox has fallen below the prohibit-send-and-receive quota before telling senders to retry.
The archive is a separate mailbox with its own allowance. Each user starts with 100 GB of archive storage, and where auto-expanding archiving is turned on it grows incrementally up to 1.5 TB.
The address is a mail-enabled public folder
You have this one if The full recipient is a public folder rather than a user mailbox, and mailbox statistics for it return nothing useful.
- Read the folder’s own quota:
Get-PublicFolder \pfname | FL *quota*andGet-PublicFolderStatistics \pfname | FL TotalItemSize. - Raise the individual limit with
Set-PublicFolder \pfname -ProhibitPostQuota 5GB -IssueWarningQuota 4GB. - Or raise the organisation default with
Set-OrganizationConfig -DefaultPublicFolderProhibitPostQuota 5GB -DefaultPublicFolderIssueWarningQuota 4GB. - Check the content public folder mailbox hosting it too:
Get-PublicFolder \pfname | FL name,*content*, then read that mailbox’s size and quotas.
The sender’s own mailbox is full, not the recipient’s
You have this one if The diagnostic says STOREDRV.Submission and MapiExceptionShutoffQuotaExceeded, and it is the same sender failing to everyone.
- Read the sending mailbox’s size and quotas, not the recipient’s.
- Look at Sent Items first: messages submitted through SMTP AUTH are stored there and count against the quota.
- Apply a retention policy that empties Sent Items before the mailbox fills, which is Microsoft’s documented remedy for high-volume senders.
Deleted content is still being counted
You have this one if The user says they deleted thousands of messages and the size has not moved.
- Empty Deleted Items, then re-check whether the space came back.
- Read the Recoverable Items folder size in the folder statistics output. It has its own allowance and grows fast under hold.
- If the mailbox is on hold, understand that Recoverable Items cannot be purged while the hold applies. Removing a hold has legal implications and is not a decision to take alone.
A quota was set by hand below the plan maximum
You have this one if The mailbox stops receiving well below the size the licence should allow.
- Read the current values:
Get-Mailbox -Identity user@contoso.com | Select *Quota*. - Raise them back towards the plan maximum with
Set-Mailbox -ProhibitSendQuota -ProhibitSendReceiveQuota -IssueWarningQuota. - Find the provisioning script that set them, or the same values will come back at the next onboarding.
Full reference
Telling the three 5.2.2 cases apart
| What the bounce says | What is actually full | Where to work |
|---|---|---|
| 554 5.2.2 … STOREDRV.Deliver … MapiExceptionQuotaExceeded | The recipient mailbox or a public folder post quota | The recipient |
| 554 5.2.2 … STOREDRV.Submission … MapiExceptionShutoffQuotaExceeded | The sender’s own mailbox, blocking the write to Sent Items | The sender |
| 5.2.2 Submission quota exceeded | Nothing. The sender passed a recipient rate or message rate limit | The sender’s sending pattern |
Where the space usually is
| Location | Why it fills |
|---|---|
| Sent Items | Every attachment the user ever sent, kept in full. Also where SMTP AUTH submissions land |
| Deleted Items | Retained until emptied, and still counted against the quota |
| Recoverable Items | Has its own allowance; grows fast and cannot be purged while a hold applies |
| Large shared attachments | Files mailed round rather than linked from SharePoint or OneDrive |
| Calendar and Conversation History | Meeting attachments and chat archives accumulating quietly |
What the licence actually buys
| Plan | Primary mailbox | Archive |
|---|---|---|
| Exchange Online Kiosk, Office 365 F3 | 2 GB | Not available |
| Exchange Online Plan 1, Business Basic, Business Standard, Office 365 E1 | 50 GB | 50 GB |
| Microsoft 365 Business Premium | 50 GB | 100 GB, auto-expanding to 1.5 TB |
| Exchange Online Plan 2, Microsoft 365 E3 and E5, Office 365 E3 and E5 | 100 GB | 100 GB, auto-expanding to 1.5 TB |
| Shared mailbox, no licence | 50 GB | – |
| Shared mailbox with Exchange Online Plan 2 | 100 GB | 100 GB, auto-expanding to 1.5 TB |
Note the archive figure. Each user starts with 100 GB, and auto-expanding archiving adds storage incrementally as that fills, up to a capacity of 1.5 TB. It is very large. It is not unlimited, and any page that tells you it is has stopped reading the service description.
Setting quotas deliberately
You can hold a mailbox below its plan ceiling on purpose, which is a reasonable thing to do where a shared or service mailbox should never grow past a certain size:
Set-Mailbox user@contoso.com -IssueWarningQuota 18GB -ProhibitSendQuota 19GB -ProhibitSendReceiveQuota 20GB
Get-Mailbox user@contoso.com | Select *quota*
The order matters: warning below prohibit-send below prohibit-send-and-receive. Setting them the other way round produces a mailbox that refuses mail before it has warned anyone.
When the mailbox is under quota and mail still bounces
- Confirm the sender is retrying. 554 is permanent, so the original message was returned and will not be delivered by itself.
- Check whether the recipient is a distribution group or Microsoft 365 group with its own restrictions, which produces a different code entirely.
- Look at the timing. A mailbox that dips under quota and climbs straight back is not fixed; the retention policy is not moving anything.
- Confirm the managed folder assistant actually ran.
Start-ManagedFolderAssistantrequests processing; on a very large mailbox it is not instant. - If the recipient is a shared mailbox, check whether anyone has ever put a retention policy on it. Shared mailboxes are the ones that quietly fill for years.
When a licence is the actual fix
Where the mail genuinely has to be kept and the mailbox is at the ceiling of a 50 GB plan, clean-up buys you weeks rather than a solution. Microsoft 365 E3 raises the primary mailbox to 100 GB and brings the archive that auto-expands to 1.5 TB, and it is the right answer when the rest of the suite is wanted anyway. Where it is not, Exchange Online Plan 2 gives the same 100 GB mailbox and the same archiving without the desktop applications. For a shared mailbox specifically, Plan 2 is the licence that takes it from 50 GB to 100 GB; Plan 1 is itself a 50 GB mailbox and buys no extra capacity at all. Arco supplies both and will tell you which one your situation actually needs before you order.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
554 5.2.2 |
Permanent delivery refusal because the recipient mailbox, or a public folder’s post quota, is full: “554 5.2.2 mailbox full; STOREDRV.Deliver.Exception:QuotaExceededException.MapiExceptionQuotaExceeded” | Microsoft Learn |
550 5.2.2 |
Not the same fault. Microsoft’s Exchange Online NDR reference gives 5.2.2 as “Submission quota exceeded” – the sender passed the recipient rate limit or the message rate limit | Microsoft Learn |
ShutoffQuotaExceeded |
Appears as MapiExceptionShutoffQuotaExceeded on the submission path: the sender’s own mailbox is past its shutoff quota, so the message cannot be written to Sent Items | Microsoft Learn |
QuotaExceededException |
The store exception class that appears in both the Submission and Deliver forms of the 5.2.2 diagnostic | Microsoft Learn |
MapiExceptionQuotaExceeded |
The MAPI-level detail on the delivery-side 554 5.2.2, naming the quota as the reason the store refused the item | Microsoft Learn |
Confirm the fix worked
Get-MailboxStatisticsshows TotalItemSize below ProhibitSendReceiveQuota.- A test message sent from outside the organisation is delivered.
- The user can send as well as receive, which proves you are below the prohibit-send threshold too.
Get-Mailbox | Select *Quota*shows the quotas you intended, not values left by a script.- A week later the mailbox is still under quota, which tells you the retention policy is actually moving mail into the archive.
Questions people ask about this
Can I just raise the quota?
Only up to what the plan allows. Set-Mailbox can lower a quota or restore one that was lowered, but it cannot take a 50 GB plan past 50 GB. Above that ceiling the routes are archiving, deleting, or a plan with a larger mailbox.
Will the bounced messages arrive once space is freed?
No. 554 is a permanent refusal, so the sending system has already given up and returned the message. Senders have to send again once the mailbox is back under quota.
Does the archive count against the mailbox quota?
No. The archive is a separate mailbox with its own allowance, which is exactly why moving old mail into it relieves the primary mailbox. Each user starts with 100 GB of archive and auto-expanding archiving grows it incrementally to 1.5 TB.
I am getting 5.2.2 but the recipient’s mailbox is nearly empty. Why?
Read the diagnostic text rather than the number. If it says STOREDRV.Submission, the sender’s mailbox is full. If it says “Submission quota exceeded” with no STOREDRV detail, the sender has passed a rate limit and no mailbox is full at all.
Is a bigger plan the only fix?
No, and it should not be the first move. Emptying Deleted Items, clearing large attachments and enabling the archive with a sensible retention policy recovers a great deal for nothing. Buy a larger plan when the mail genuinely has to be retained and the ceiling is genuinely reached.
