Outlook outage: when to wait, resend or ask IT to find your email

Queued or Pending → wait: Microsoft is holding delayed mail for up to 48 hours. Bounce received → fix the stated cause, then resend. Delivered but not found → ask IT to check Junk Email and quarantine.

Exchange Online can retry delivery automatically, so sending another copy while the first is still being processed risks duplicates. Before choosing an action, locate the original message and check for a known service incident. A copy in Sent Items tells you where Outlook saved it; it does not confirm arrival in the recipient’s mailbox.

Who was affected, and when will mail recover?

The announced incidents covered work and school Exchange Online mailboxes, according to the publication Carly’s November 12 report. It reported no separate incident announcement for personal Outlook.com accounts. Personal users experiencing problems should also check the account and app fixes below. You can generally read messages that your desktop Outlook app downloaded before the disruption.

The outage began on Thursday, November 12, and continued into Friday, November 13, The National reported. Microsoft’s Friday update described incremental improvement, but service health remained variable and capacity was below normal. The extended timeout gives Microsoft longer to process queues and backlogs before delayed messages expire. It is a delivery-processing window, not a deadline for restoring service.

The November 12–13 reports provided no firm recovery time or arrival estimate for an individual message. Microsoft said it would explain the root cause and further protective measures in a report after recovery, according to Tom’s Guide.

Sent from Gmail or another provider?

If you emailed a work or school address from Gmail or another provider, hold off sending a replacement unless you receive a bounce. The recipient’s Exchange Online mailbox can be affected even when you send through a different service. Microsoft extended the window to protect delayed incoming mail from being bounced while it works through the backlog, as covered in the outage updates.

Check the right service status

Start with Microsoft’s public service status page. The page lagged complaints early in this outage, Carly reported, so a green page doesn’t rule out a problem. Workplace administrators can look for incident EX1550543 for Exchange Online and MO1550821 for Microsoft 365 to find the specific entries.

For your organization’s information, ask an administrator to open the Microsoft 365 admin center and select Health > Service health. Service Support and Helpdesk admins can view those records. If the admin center is inaccessible, Microsoft recommends its public status page and @MSFT365status on X for information about certain incidents. Use the service-health instructions to check for a cloud-service problem before spending time changing account settings.

Match an incident’s symptoms to your problem. A Microsoft notice reproduced by University of Pennsylvania ISC concerns missing contacts and Speed Dial entries. It addresses a different symptom from missing email delivery and supplies no recovery deadline for delayed messages.

Find the original email

For an Outlook.com message that will not send, check Drafts and Outbox first. An email still in Outbox can reflect a connection or sign-in problem, so investigate that condition before composing a replacement.

Next, open Sent Items under the account you actually used. Each Outlook account has its own sent folder, so check the sending account if several are connected. Search with To: followed by the recipient or Subject: followed by the subject. If you find no copy, check whether Outlook is configured to save sent messages: a missing entry can result from that setting. Microsoft’s sent-email guidance covers these checks.

Get evidence of delivery

A delivery receipt confirms mailbox delivery; a read receipt confirms that the email was opened. Recipients can decline read receipts, and some email programs do not support them, so a missing receipt cannot tell you that delivery failed. Microsoft says receipt functionality for Outlook.com accounts requires a Microsoft 365 subscription. The Outlook.com website cannot request read receipts, while Outlook for Windows can request them for messages sent from an Outlook.com account.

For workplace mail, give IT the sender’s address, recipients and approximate send time, and request an Exchange Online message trace. Messages normally take 5–10 minutes to appear in trace data. Pending identifies an unresolved delivery attempt; Failed records a failure. IT can inspect the event details to establish where a message went, including filtering routes that leave it outside the recipient’s inbox.

Treat a bounce as a troubleshooting instruction: read its reason before trying again, because an unchanged resend may fail again. For Outlook.com, verify the recipient’s address. If it is correct and the message still bounces, Microsoft directs you to Sender Support.

If it’s not the outage

Try sending and receiving through webmail. If that works while desktop Outlook fails, investigate the app or account settings. In classic Outlook, Working Offline prevents a server connection. Open Send/Receive > Work Offline to reconnect using Microsoft’s offline instructions.

For Outlook.com, full Microsoft cloud storage blocks sending and receiving; incoming messages bounced during that period cannot be recovered, so request fresh copies after fixing storage. Update a changed password and check for an account block caused by unusual sign-in activity. For missing incoming mail, check the Other tab and filters. If an attachment exceeds 25MB, reduce its size or use a OneDrive link before trying again.