Microsoft Outlook Outage: What Went Wrong on 12 November 2026 and When Services Returned
*Disclaimer: We may earn a commission if you make a purchase through our affiliate links, at no extra cost to you.
Microsoft Outlook stopped working for users around the world on Thursday, 12 November 2026, in a disruption that also knocked out Teams, SharePoint Online and the Copilot assistant. The outage began in the Americas in the early afternoon and spread across 74 countries and territories within about an hour, leaving office workers unable to send or receive email for much of the working day.
Microsoft traced the failure to part of its own infrastructure, which it said was under elevated load, and to servers that became unexpectedly unavailable after failing automated health checks. The company said there was no indication of a cyberattack, and by the evening it reported limited recovery as restored servers gradually came back online.
| Microsoft Outlook Outage — Quick Reference Summary | Detail |
|---|---|
| Date | Thursday, 12 November 2026 |
| Incident start | 16:17 UTC (Exchange Online, incident EX1550543) |
| Services affected | Outlook, Microsoft 365, Teams, SharePoint Online, Copilot, Defender XDR |
| Peak Outlook reports | 138,058 on Downdetector around 1 pm ET, according to Reuters |
| Microsoft 365 reports | More than 47,000 at peak |
| Reach | 74 countries and territories within about an hour |
| Stated cause | Elevated load on infrastructure; servers failing automated health checks |
| Cyberattack | No indication, Microsoft told the ABC |
| Recovery | Limited recovery from around 6 pm ET; gradual restoration overnight |
| Incident IDs | EX1550543 (Exchange Online), MO1550821 (wider advisory) |
How the Outage Unfolded Across the Working Day
Complaints about Outlook began climbing at about 12:25 pm Eastern Time, and within half an hour the Microsoft 365 Status account on X acknowledged that users were struggling to reach Exchange Online mailboxes in the Americas. Microsoft opened a wider advisory at 1:26 pm ET covering Exchange Online, Teams, SharePoint Online, Microsoft 365 Copilot and Defender XDR.
By 1 pm ET, Downdetector had logged 138,058 Outlook reports, according to Reuters, while Microsoft 365 drew more than 47,000. At their peak, combined reports across five Microsoft services reached 19,650 a minute, against fewer than 15 a minute on an average Thursday. The disruption then went global, with Downdetector recording outage reports from 74 countries and territories.
The scale of the failure was visible beyond Microsoft’s own products. Connectors used by OpenAI and Anthropic also reported problems, showing how deeply Microsoft’s cloud services sit inside other companies’ tools. For many office workers, the outage arrived in the middle of the working day, when email and Teams calls carry the bulk of workplace communication.
What Microsoft Says Caused the Failure
Microsoft said a portion of its infrastructure was experiencing elevated load across multiple regions, which was likely contributing to the connectivity errors. It later determined that a number of servers had become unexpectedly unavailable because they failed during automated health checks, the routine tests that confirm a server is fit to take traffic.
The company paused deployments, redirected traffic away from the affected infrastructure and began restarting the impacted servers. A Microsoft spokesperson told the Australian Broadcasting Corporation there was no indication the disruption was a cyberattack, a point that matters because large outages often prompt speculation about malicious causes before the facts are known.
By about 6 pm ET, Microsoft said a portion of the affected servers had returned to service and were holding stable, and it told users to expect a gradual recovery as their email clients reconnected. Outlook reports on Downdetector had fallen to about 34,490 by the evening, though Microsoft warned that servers brought back online could become unresponsive again once they started taking traffic.
Why One Failed Health Check Can Take Down Email Worldwide
The outage is a reminder of how concentrated modern workplace technology has become. Outlook, Teams and Copilot all draw on the same Microsoft 365 backbone, so a fault in shared infrastructure can remove email, meetings and AI assistance at the same time. That concentration explains why a single incident produced tens of thousands of complaints within an hour.
Remote and hybrid teams felt the impact most directly, because their working day runs through the very tools that went down. When Teams calls and Outlook mailboxes fail together, the usual fallback of switching from one Microsoft app to another stops working, and teams are left with personal messaging apps or phone calls. Our guide to virtual meeting etiquette covers how teams normally keep online meetings running smoothly, and this outage showed what happens when the platform underneath those meetings disappears.
Copilot’s failure carried a different lesson. AI assistants are now woven into everyday office software, and modern digital tools increasingly depend on cloud services that users never see. When the cloud layer fails, the AI layer fails with it, which is worth remembering for any business building its workflows around a single provider.
The Business Cost of a Day Without Email
The financial impact of the outage is not publicly verified in a single figure, and Microsoft has not published an estimate of lost productivity or compensation. What is known is the scale: more than 130,000 Outlook complaints at the peak, tens of thousands more for Microsoft 365, and disruption across 74 countries and territories.
For Microsoft itself, the incident is the third major Microsoft 365 disruption of 2026, following multi-hour outages in January and a code-update failure in August that took several days to fully resolve. A pattern of repeated outages raises questions about resilience that investors and large corporate customers will keep asking, even though each incident has had a different technical cause.
Businesses that depend on Microsoft 365 for email, document sharing and meetings may now review their contingency plans. The practical options are limited — few companies run a second email provider in parallel — but the outage has already renewed discussion about backup communication channels and about how quickly teams can switch to them when the main system fails.
Frequently Asked Questions
Was the Microsoft Outlook outage caused by a cyberattack?
No indication of a cyberattack has been reported. Microsoft told the Australian Broadcasting Corporation there was no indication the disruption was an attack, and attributed it to elevated load on its infrastructure and servers failing automated health checks.
Which services were affected by the 12 November 2026 outage?
Outlook and Exchange Online were hit hardest, along with Microsoft 365, Teams, SharePoint Online, Microsoft 365 Copilot and Defender XDR. Connectors used by OpenAI and Anthropic also reported problems during the disruption.
How many users reported the Outlook outage?
Downdetector logged a peak of 138,058 Outlook reports around 1 pm ET on 12 November, according to Reuters, with more than 47,000 reports for Microsoft 365. Downdetector counts user-submitted reports rather than affected accounts, so the true number of affected users was likely higher.
When did Outlook come back online?
Microsoft reported limited recovery from around 6 pm ET on 12 November, with a portion of affected servers returning to service and holding stable. The company warned that full restoration would be gradual as email clients reconnected, and some restored servers could become unresponsive again under load.
What were the incident numbers for the outage?
Microsoft tracked the mailbox problem as incident EX1550543 and opened a wider advisory, MO1550821, covering the affected Microsoft 365 services. Both numbers were published through the Microsoft 365 admin centre and the Microsoft 365 Status account on X.
