Microsoft 365 Mailbox Full? Restore Mail Flow Without Deleting the Wrong Email

Reader ratingRate this article

Loading reader rating…

★★★★★

Privacy-conscious voting uses a signed random browser identifier and a short-lived network hash; the rating tables contain no raw IP-address column.

Practical fix: If a Microsoft 365 mailbox is full or close to its limit, do not begin with a mass delete. First confirm which mailbox is affected, measure its largest folders, protect business records, and decide whether the right remedy is cleanup, an online archive, a license change, or a retention-policy review. The goal is not merely to make the warning disappear—it is to restore reliable mail flow without deleting evidence or creating an unmanaged pile of local data.

What “mailbox full” can actually stop

Exchange Online uses warning, prohibit-send, and prohibit-send/receive thresholds. Microsoft says a mailbox at the prohibit-send threshold cannot send new messages until enough mail is removed, while the prohibit-send/receive threshold causes incoming mail to be rejected and an NDR, or bounce message, to be returned to the sender.[1] That makes a quota warning an availability problem, not just an untidy-inbox problem.

Published limits differ by plan. Microsoft’s current Exchange Online limits table shows common prohibit-send/receive values of 50 GB for Exchange Online Plan 1 and 100 GB for Exchange Online Plan 2, but the assigned license and any organization-specific configuration control the real limit for a particular mailbox.[1] Read the user’s live mailbox usage and license instead of relying on a remembered number.

Who is affected—and who is not automatically affected?

Step by step: restore capacity without deleting the wrong mail

1. Capture the warning and test mail flow

• Save the exact warning, affected address, time, and device or browser where it appeared.
• Send one harmless message from the mailbox and record whether it leaves.
• Send one harmless message from an outside address and preserve any NDR or bounce.
• Do not keep repeating tests if messages are bouncing; repeated attempts create noise without adding diagnosis.

Practical interpretation: if sending fails but receiving still works, the mailbox may be at a prohibit-send threshold. If outside senders receive an NDR, it may be at prohibit-send/receive. The exact NDR and live quota remain the deciding evidence because transport rules, licensing, or another service condition can produce different failures.

2. Prove the server-side size and the assigned limit

Check mailbox usage in the Microsoft 365 or Exchange admin center, or have the administrator inspect it with the supported Exchange tools. Record the current size, warning threshold, prohibit-send threshold, prohibit-send/receive threshold, license, archive status, and whether the mailbox is on hold.

Good evidence: a live server-side usage reading tied to the correct user and license. Weak evidence: the number of messages in Inbox or a screenshot with no account name. Use the hosted mailbox’s live usage reading for the quota decision.

3. Find the large folders and messages before choosing a remedy

In classic Outlook, Microsoft’s Mailbox Cleanup tool can show total and per-folder size, find old or large items, and display the size of Deleted Items and Conflicts.[2] Outlook on the web and the new Outlook can expose different storage views; use the supported view available to that account.

• Sort large folders by size and identify oversized attachments, Sent Items, Deleted Items, Junk Email, conversation copies, and automated reports.
• Separate disposable mail from business records that must be retained.
• Check shared mailboxes and Online Archive separately; a user may be looking at the wrong store.
• Record what you plan to remove or move before doing it.

4. Choose the least risky repair path

Phone readers: swipe the table left to compare all options.

Repair path	Best when	Main caution
Remove clearly disposable mail	Large junk, redundant copies, or obsolete automated reports are confirmed unnecessary.	Emptying Deleted Items can cross a recovery boundary; preserve required records first.
Save needed attachments elsewhere	The message can remain as a record while a large working file belongs in an approved team location.	Do not break retention, permissions, or version history. A saved attachment is not proof the email itself may be deleted.
Enable or use Online Archive	The license includes archiving and older retained mail should remain searchable under managed controls.	Verify the license and archive status, then remeasure the primary mailbox rather than assuming capacity changed.
Change the license or quota design	The business legitimately needs a larger primary mailbox and the chosen plan supports it.	A larger quota postpones cleanup; it does not replace retention design.
Export to PST	A deliberate, approved backup or migration needs a portable copy.	A PST is a separate local file with its own security, backup, access, and support limits.

5. If cleaning up, remove low-risk material first

1. Delete obvious junk and obsolete automated notices only after checking the sender, date range, and business need.
2. Review Deleted Items and Junk Email deliberately rather than pressing “empty” without a scope check.
3. For attachments you must keep, place the file in an approved team site, OneDrive location, or managed folder and verify access before deciding whether the message can be removed. Microsoft lists storing attachments outside the mailbox as one way to control mailbox size.[2]
4. Recheck the server-side mailbox size and quota state.
5. Repeat the inbound and outbound test once.

Practical caution: moving a file out of email can change who can access it, how it is backed up, and whether the original message remains a complete record. Use an organization-approved destination, not a random personal folder.

6. If archiving, verify eligibility and expectations

Microsoft describes an archive mailbox as additional mailbox storage that an administrator can enable when the assigned license supports it.[3] Microsoft also says the default archive policy moves qualifying items to the archive two years after delivery or creation; enabling the archive today does not mean every old message moves immediately.[3]

• Confirm that archiving is included in the assigned license.
• Enable the archive through the supported admin path and record the change.
• Verify that the archive appears for the user.
• Review the retention policy that controls when items move.
• Do not promise immediate relief until mailbox usage and mail flow are rechecked.

Microsoft documents an optional organization setting that can automatically provision an archive when an eligible Exchange Online mailbox reaches 90% of its quota, but only when its listed mailbox, licensing, and directory-synchronization conditions are met.[3] That is an administrative design choice, not a universal emergency switch.

7. Treat PST export as a managed exception, not the default fix

Microsoft supports exporting Outlook data to a PST for backup and migration scenarios, and advises copying the resulting file to a safe location.[5] Microsoft also notes that AutoArchive moves old items rather than making a complete copy of old and new mail, and that new Outlook currently has limitations for calendar and contacts stored in PST files.[5]

If a business approves PST use, document its owner, location, encryption, backup, retention period, and restore test. Never leave the only copy on the same computer that created it, and never delete the hosted originals merely because an export wizard finished.

8. Recheck mail flow and preserve the evidence

• Refresh the server-side usage and quota state.
• Send one new message from the mailbox and confirm that it appears in Sent Items and reaches the recipient.
• Send one new message from an outside account and confirm delivery with no NDR.
• Check any scanner, application, or shared-mailbox workflow that depended on the affected address.
• Record what was deleted, moved, archived, licensed, or changed.
• Review the result again after the archive or retention process has had time to run.

Good fixes and bad shortcuts

Two realistic examples

Harmless cleanup: automated reports filled Sent Items

Illustrative example: A small business mailbox can still receive mail but cannot send. The admin confirms that Sent Items contains years of replaceable automated reports and that no hold applies. The business preserves the reports it must retain, removes the approved obsolete batch, rechecks server-side usage, and tests one inbound and outbound message. The repair is complete only when the live quota drops and mail flow works.

Costly wrong turn: deleting mail that a hold was preserving

Illustrative caution: A manager sees a large Recoverable Items footprint and asks IT to remove the retention policy so space can be reclaimed. That change could affect records being preserved for compliance or discovery. Microsoft explains that retention policies and legal holds use the Recoverable Items area.[6] The safe response is to identify the hold, its owner, and the governing requirement before any retention change.

Frequently asked questions

Why did incoming email bounce?

Microsoft says Exchange Online rejects incoming mail at the prohibit-send/receive threshold and returns an NDR to the sender.[1] Preserve the exact NDR because a bounce can also have another cause.

Will emptying Deleted Items fix it?

It can reclaim visible mailbox space when those items are no longer needed, but it is not a universal answer. Microsoft says permanently deleted items normally move into Recoverable Items and are retained for 14 days by default, with administrators able to configure up to 30 days; litigation hold changes that normal retention behavior.[4] Check the live quota after cleanup instead of assuming the space returned immediately.

Is an Online Archive the same as a backup?

Practical distinction: No. An Online Archive is additional managed mailbox storage and search space; it remains part of the Microsoft 365 mail system and its policies.[3] A backup is a separate recovery control designed around your organization’s recovery requirements.

Should I save attachments to OneDrive and delete the email?

Microsoft recommends storing attachments you want to keep outside the mailbox as one space-saving option.[2] For business mail, verify the approved location, access, retention, and backup first. Saving the file does not automatically mean the message itself is disposable.

Can I export everything to a PST?

Microsoft provides PST export for backup and migration uses, but the file becomes a separate asset that must be protected and tested.[5] For a business, use PST only with a documented owner, safe location, encryption, backup, retention decision, and restore test.

Related guides from The IT Guys

• Cloud Storage Full? Fix It Before Email and File Sync Stop — use this broader guide when the problem involves pooled file storage or several cloud services rather than one Exchange mailbox.
• Microsoft 365 Email Account Hacked? Contain It Before Fraud Spreads — follow the containment path when the mailbox shows suspicious rules, sign-ins, forwarding, or sent mail.
• Unexpected MFA Prompt? Deny It, Then Check Whether Your Password Is Already Exposed — use this when the warning is accompanied by unrecognized sign-in prompts.

Sources

1. Microsoft Learn: Exchange Online limits
2. Microsoft Support: Manage my mailbox size in Outlook
3. Microsoft Learn: Enable archive mailboxes for Microsoft 365
4. Microsoft Learn: Change how long permanently deleted items are kept
5. Microsoft Support: Export emails, contacts, and calendar to a PST
6. Microsoft Learn: Recoverable Items folder in Exchange Online