The Microsoft 365 outage that started Thursday, Nov. 12, 2026 left Outlook email down or badly delayed for more than 20 hours. If your website sends contact form, quote request or booking emails to an Outlook or Microsoft 365 inbox, assume some of those notifications arrived late, and check whether any never arrived at all. The people behind them think they already reached you.
Search rankings aren't the worry here. None of the reports we read named Bing search, Microsoft Advertising or Azure among the affected services. The cost is in leads that went unanswered for a day.
What happened?
CNBC says connection problems started shortly before 1 p.m. Eastern (18:00 UTC) on Nov. 12 and lasted more than 20 hours. Microsoft first reported trouble reaching Exchange Online mailboxes in the Americas, then listed Teams, SharePoint Online, Microsoft 365 Copilot and Defender XDR, according to SecurityWeek. Downdetector logged reports from 74 countries and territories, so this was not a US-only problem.
Microsoft said the load on its servers was not caused by more traffic, began rolling back a recent network configuration change, and said it had "no evidence of malicious activity." By about 9 a.m. Eastern on Nov. 13, CNBC reports, email queues were "approaching normal levels," with intermittent issues still expected. The incident IDs in the Microsoft 365 admin center are EX1550543 (Exchange Online) and MO1550821 (Microsoft 365). Microsoft says it will publish a post-incident report with the root cause.
Were emails lost or only delayed?
Mostly delayed, from what Microsoft has said. CNBC reports Microsoft extended its retry window to 48 hours so delayed messages would keep trying to deliver. But your website's emails don't start at Microsoft. They start at whatever service your site uses to send mail, and that service has its own limit on how long it keeps retrying an inbox that won't accept mail.
Here is what the sending services' own documentation says:
The outage ran longer than Mailgun's default window. If your forms send through Mailgun and Exchange Online refused mail during the worst hours, some notifications may have expired before Outlook took them in. SendGrid's 72 hours covers an outage of this length. We don't know yet whether Exchange Online refused incoming mail or accepted it and delivered it late inside Microsoft; that depends on details Microsoft hasn't published. Your sending service's log will tell you which happened to your messages.
How to check your website for missed leads
- Compare saved form entries with your inbox. Most form plugins keep a copy of every submission on the site (Gravity Forms and Fluent Forms do, WPForms does on its paid plans, and Contact Form 7 needs an add-on such as Flamingo). List the entries from Nov. 12 and 13 and match each one against the notification emails you received.
- Read your sending service's log. If you use SendGrid, Mailgun, Amazon SES, Postmark, Brevo or an SMTP plugin with an email log, filter for messages to your own domain on Nov. 12 and 13. Delivered is fine. Deferred, blocked, bounced or Too old means the email never reached the inbox.
- Download ad platform leads directly. Google Ads lead forms, Meta Instant Forms and LinkedIn Lead Gen Forms store submissions in the platform. If you rely on an email alert or a connector to your CRM, check the leads list in the platform for those two days, and download it this week, since platforms keep leads only for a limited time.
- Check your CRM's import or automation history. Zapier, Make and native CRM integrations that send an email step to an Outlook address may show failed runs for the outage window.
- Reply to everyone you find. A short note works: your message reached us late because of the Microsoft outage on Nov. 12, here is our answer. Someone who asked for a quote on Thursday afternoon may already be talking to a competitor.
Desktop Outlook can still show mail it downloaded before the outage, Al Jazeera notes, so an inbox that looks normal on one computer isn't proof nothing was missed.
How to avoid this next time
- Send form notifications to two addresses on different providers, for example your Microsoft 365 inbox and a Gmail or Google Workspace address. One outage then can't hide a lead.
- Keep form entries stored on the site, so the email is a convenience, not the only copy.
- Know your sender's retry window. If you use Mailgun, its retry window can be set per message up to 24 hours; check with whoever built your site whether that is worth raising.
- Test the form after any outage or site change. Submit a test entry and watch it arrive. Our pre-launch website QA checklist includes the form checks we run.
One more detail from SecurityWeek: some Google Workspace users also had trouble reading their Gmail through the Outlook app during the outage. If your team reads Gmail in Outlook, check the Gmail web inbox too.
What we don't know yet
- The root cause. Microsoft has promised a post-incident report.
- Whether Exchange Online refused incoming mail from outside senders or accepted it and delayed delivery internally, which decides whether short sender retry windows actually expired.
- Whether any messages were lost after Microsoft's own 48-hour retry window.
We'll update this post when Microsoft publishes its report.