Guides / Outlook not receiving email or empty Inbox: Exchange or the client?

Part of: Email not sending, receiving or syncing

Last reviewed 5 Oct 2026 · By Harry

Outlook not receiving email or empty Inbox: Exchange or the client?

Outlook Inbox empty or no new mail? Split a quiet mailbox from Focused Inbox, rules, OST corruption, quota and a real Exchange Online outage.

"My Inbox is empty" and "I am not getting email" are the tickets that ruin a morning. They sound like Exchange is down. Most of the time the mailbox is fine and the client, a rule, Focused Inbox, or a quota is hiding the mail. Work the split before you rebuild anything.

Is it Microsoft?

Open Outlook on the web for the same mailbox in a private window. Check the Outlook and Microsoft 365 pages, which read Microsoft's official feeds. Three outcomes:

• OWA empty for many people in the company at the same minute. Now you may talk about Exchange. Check Service health in the Microsoft 365 admin centre. Do not start new Outlook profiles yet.
• OWA has mail, desktop Inbox looks empty. The mailbox is answering. The desktop client, sync, or view is the patient.
• OWA empty for one user, colleagues fine. Rules, Focused Inbox, retention, delegation, or the wrong mailbox. Still not a global outage.

User-level checks (do these first)

1. Focused Inbox. On the View ribbon, turn Focused Inbox off, or open the Other tab. Plenty of legitimate mail lands in Other and users swear the Inbox is dead.
2. Folders and views. Check Junk, Clutter (legacy), Deleted Items, and any folder a rule created. Clear view filters: View → Current View → Reset View. A filter on "Unread" or a category makes a full mailbox look empty.
3. Rules and Sweep. File → Manage Rules and Alerts (classic) or Settings → Mail → Rules (new Outlook / OWA). Look for move-to-folder, delete, and forward rules. Sweep and Inbox rules in OWA apply even when the desktop client is closed.
4. Wrong account. Shared mailboxes, archive mailboxes, and a second work account often leave people staring at an empty primary Inbox while mail arrives elsewhere.
5. Search across the mailbox. Search for a known sender with All Mailboxes / All folders. If search finds messages the Inbox list does not show, the view or sync folder is wrong, not Exchange.
6. Ask the sender for the bounce. A non-delivery report names the exact failure: quota, policy reject, or the message never left their side.

Desktop client still wrong

• Connection status. Ctrl + right-click the Outlook tray icon → Connection Status. No rows means the client never found Exchange. Rows stuck on Disconnected mean transport, not an empty folder.
• New profile, leave the OST alone. Create a new Outlook profile and add the account fresh. Do not run scanpst as step one. If the new profile fills correctly, the old OST or profile was the fault.
• Cached Exchange mode. A huge or corrupt OST sits on "Updating inbox" and can show a stale empty snapshot. Online mode (temporarily) is a diagnostic, not a permanent lifestyle.
• Add-ins. Disable COM add-ins, especially anything that rewrites mail or touches the Inbox, then restart.

Admin-level checks

• Message trace. In the Exchange admin centre, run a message trace for recipient, sender and time window. If Exchange accepted the message, it is in the service somewhere (folder, quarantine, or transport rule). If there is no trace, the message never reached Microsoft — DNS, MX, or the sender.
• Quota. A full mailbox stops new mail. Check mailbox usage and the Recoverable Items folder if litigation hold inflated it.
• Transport and mail-flow rules. Recently added rules that redirect, quarantine or reject are a classic "whole company stopped getting mail from X" cause.
• MX and domain. Wrong or missing MX after a DNS change hits every mailbox. Compare with your documented records.
• Licence and user state. Soft-deleted users, blocked sign-in, or a missing Exchange licence produce empty or inaccessible mailboxes that look like outages.
• Quarantine and Defender for Office 365. Admin quarantine and user quarantine hold mail that never reaches the Inbox. Release or tune the policy; do not declare Exchange down.

Delivery delay versus missing

During a real Exchange incident, mail is often delayed and then delivered. That is different from mail that never arrives because of a rule or MX failure. See also Exchange Online mail delivery delay when traces show accept-then-hold behaviour.

When to escalate

Escalate to Microsoft when message trace shows the service accepted mail that never appears for many users, Service health names Exchange Online, and OWA fails company-wide. Include message IDs, UTC times, and tenant ID. One empty Inbox on one PC with healthy OWA is a desk fix — say so on the ticket.

Related status pages

• Outlook
• Microsoft 365
• Microsoft Entra ID

Related guides

• Outlook disconnected or not syncing: is it Microsoft or you?
• Exchange Online mail delivery delay or messages stuck in queue
• Gmail not receiving email in Google Workspace: what to check

FAQ

Why is my Outlook Inbox empty but colleagues still get email?

Usually Focused Inbox (mail in Other), a rule moving messages, a view filter, the wrong account selected, or a broken local profile. Check Outlook on the web for the same mailbox before blaming Exchange.

How do I tell an Exchange outage from a client problem?

If Outlook on the web shows mail and works for colleagues, Exchange is answering. If OWA fails for many users at once and Microsoft Service health agrees, treat it as a service incident.

What should an admin run first for missing mail?

Exchange message trace for that recipient and time window. A trace proves whether Microsoft received the message; no trace points at DNS, MX or the sender.

Can a full mailbox stop new email in Microsoft 365?

Yes. When a mailbox hits quota, new messages can bounce or stop delivering until space is freed or the quota is raised.