There's an 78.3% chance your domain can be spoofed right now. Run DMARC Check

Microsoft 365 / Outlook

Microsoft 365 error 554 5.2.2 — mailbox full (QuotaExceeded)

554 5.2.2

The recipient's Exchange Online mailbox has exceeded its storage quota, so the message was rejected rather than delivered. Unlike Gmail's temporary 452, Exchange commonly returns this as a permanent 5xx — the message will not be retried, and the sender gets an NDR immediately. The fix belongs to the recipient (or their admin); the sender's only real decision is what the bounce means for their list.

How to fix it

  1. 1

    If you're the sender

    Nothing on your side caused this and re-sending hits the same wall until the recipient clears space. For anything important, use another channel. On mailing lists, treat repeated 5.2.2s from an address the way you treat a hard bounce: suppress it until it proves alive.

  2. 2

    If you're the recipient

    Delete large mail (sort by size, empty Deleted Items and Junk — they count against quota), or archive old mail out of the mailbox. Outlook shows current usage under Settings → General → Storage.

  3. 3

    If you're the recipient's admin

    Check the mailbox's quota in the Microsoft 365 admin center or Exchange admin center (ProhibitSendReceiveQuota is the limit that triggers this NDR). Raise it within your license's cap, enable archiving, or clean up — and check whether some rule or connector is ballooning the mailbox, like a journaling loop.

  4. 4

    If it's a shared or resource mailbox

    Shared mailboxes without a license have a lower quota cap and hit 5.2.2 sooner than user mailboxes. Assigning a license or enabling archive raises the ceiling.

Meaning current as of 2026-07-25, cross-checked against the provider's own documentation. Providers do occasionally redefine codes — if this doesn't match what you're seeing, the source link is the authoritative reference.

Common questions

Why did Gmail defer with 452 but Microsoft hard-bounce with 554 for the same condition?+

Provider policy. RFC 3463's x.2.2 status covers mailbox-full in both temporary and permanent flavors — Gmail chooses to defer and let you retry; Exchange Online typically rejects permanently and tells the sender immediately. Both are standards-compliant.

The recipient says they deleted mail but bounces continue.+

Deleted items still count against quota until purged from Deleted Items (and Recoverable Items retains data for a further period). Truly freeing space can lag by a purge cycle — have them empty Deleted Items and wait briefly before re-testing.

As a sender, does this bounce hurt my reputation?+

The bounce itself doesn't — receivers know it's the recipient's condition. What hurts is continuing to send to addresses that consistently bounce; that pattern is what reputation systems read as poor list hygiene.