The Microsoft outage that struck on Thursday, 12 November 2026, knocked Outlook, Teams and Copilot offline in the middle of the working day, with outage reports for Outlook alone peaking at more than 130,000. Microsoft said servers in the Exchange Online infrastructure that handles mailbox access had unexpectedly become unavailable, and that it was redistributing traffic and restarting servers to bring services back. By Friday, 13 November, Microsoft said it had addressed the underlying issue and was seeing broad recovery and stability across its services. On Saturday, 14 November, Microsoft confirmed the incident was fully resolved: in its final update, at 03:51 UK time, the company said services across the previously affected environments had fully recovered and the backlog of email messages had been processed, and that "this issue is remediated". Microsoft put the end time at Friday, 13 November, 4:10 PM UTC. It also named the cause — a problem during an earlier network capacity upgrade that surfaced after a recent network change — and apologised for the disruption.

What went down in the Microsoft outage

Microsoft's advisory for the wider incident, tracked as MO1550821 in the Microsoft 365 admin center, listed five services customers may have been unable to connect to: Exchange Online, Microsoft Teams, SharePoint Online, Microsoft 365 Copilot and Microsoft Defender XDR, BleepingComputer reported. Users also reported trouble with OneDrive, Azure and the Microsoft Store, according to outage tracker Downdetector.

For most people the failure looked the same: Outlook would not open mailboxes on the web, desktop or mobile apps, Teams messages were delayed or failed, and Copilot was unreachable. Downdetector, which counts user-submitted problem reports, recorded more than 130,000 Outlook reports at 1:27 p.m. ET, Reuters reported, while reports for Microsoft 365 as a whole topped 46,000. USA Today reported that Teams peaked at almost 4,600 reports around 1:58 p.m. ET and Copilot at almost 6,000. The disruption reached beyond Microsoft's own apps: CNET reported that OpenAI and Anthropic both saw their Microsoft 365 connectors fail during the outage. Downdetector also logged elevated reports for some other services, including Google services, Steam and Amazon Web Services, though nothing linked those to Microsoft's incident.

Microsoft outage timeline: Thursday, 12 November

Microsoft's own log puts the start of the Exchange Online incident at 11:17 a.m. ET, according to WOM Technology's reading of the incident record. Around noon ET, reports on Downdetector began surging, and by 12:09 p.m. CT the tracker had logged 128,874 Outlook reports, Techaeris reported.

Microsoft's first public acknowledgment came at 12:54 p.m. ET, when the Microsoft 365 Status account on X said it was investigating reports of users having trouble accessing Exchange Online mailboxes in the Americas. Thirteen minutes later it widened the warning, saying the problem could affect Microsoft 365 service connectivity for users in any region. Between 1:09 and 1:27 p.m. ET, Outlook reports peaked — 128,874 at 1:09 p.m. ET, then more than 130,000 at 1:27 p.m. ET, according to Downdetector figures reported by Techaeris and Reuters. At 1:26 p.m. ET, Microsoft logged the wider Microsoft 365 incident, MO1550821.

Through the afternoon Microsoft kept updating its status page: it paused all deployments and configuration changes, redistributed connection traffic across its worldwide infrastructure, and began restarting affected servers. By 3:20 p.m. ET, about 69,000 users were still reporting Outlook problems and a further 31,000 were reporting problems with Microsoft 365, USA Today reported, and Microsoft said it was still working on returning service. By the evening the numbers were falling, but BleepingComputer reported that the Microsoft 365 outage had not yet been resolved.

What caused the Microsoft outage

Microsoft's explanation shifted as the day went on. At first it blamed elevated load on part of its infrastructure across multiple regions. Then it narrowed that down: "We determined the elevated load isn't driven by an increase in traffic, but by a number of servers being unexpectedly unavailable; straining the remaining infrastructure," Microsoft said in an update on X, quoted by BleepingComputer. In other words, the load was not caused by too many people using the service — it was caused by too few servers being available to carry them.

The mechanism, as far as Microsoft has described it, sits in the health checks that are supposed to protect the service. Microsoft's incident log said the affected servers were failing automated health checks, and that this may be related to a recent change to a component involved in processing those checks, WOM Technology reported. Microsoft has since confirmed the cause. In a statement on Friday, 13 November, the company said: "This was a technical issue not related to cyber or AI/agents. The incident was introduced by an issue during an earlier network capacity upgrade that surfaced following a recent network change." It said it had addressed the underlying issue and was restoring service to the remaining customers and regions gradually, and that it would publish a full post-incident report once its review is complete.

What the outage was not is clearer than what it was. Microsoft has not linked it to a cyberattack, and no group has claimed one, Techaeris reported. The company's own description is a capacity and infrastructure problem, and its response followed from that: pause deployments, spread the traffic, restart the servers, and test a configuration change intended to address the problem.

The separate Teams outage that morning

The Microsoft outage was the second Microsoft incident of the day. Hours earlier, a separate Teams incident, tracked as TM1550488, disrupted messaging in North and South America from 9:45 to 10:53 a.m. ET, BleepingComputer reported, causing delays or failures when sending messages, errors creating or updating conversations, and problems retrieving chat messages.

Microsoft attributed that earlier disruption to resource contention within its infrastructure, which led to elevated resource use and stopped the service processing messaging requests normally, and said it was fully resolved later that morning. Microsoft has not said whether the two incidents are related, so they should be treated as separate events until it does.

What to do if Microsoft 365 is still down for you

There is nothing to fix on your own computer — the fault is on Microsoft's side, and reinstalling Outlook or resetting a password will not bring a mailbox back. The fastest check is Microsoft's own status channel: the Microsoft 365 Status account on X, or the Service health page in the Microsoft 365 admin center, where administrators can follow the incident under EX1550543 for Exchange Online and MO1550821 for the wider Microsoft 365 outage.

If email sent during the outage has not arrived, it is probably delayed rather than lost. Delayed mail is usually queued and retried, so most of it should arrive late rather than not at all. Businesses that route invoices, approvals or customer mail through Outlook should watch for that delayed batch landing after service returns, and check the admin center rather than individual inboxes for the authoritative status.

Why the Microsoft outage matters

This is the second large Microsoft 365 outage of 2026. The first, on 22 January, lasted close to ten hours before access was restored, The Register reported. And it is not the first time a single configuration problem has taken down a whole stack of services: on 29 October 2025, a configuration change in Microsoft's Azure cloud knocked out Office 365 and Xbox Live, and Alaska Airlines said it disrupted check-in, the Associated Press reported. Cloud outages keep repeating the same lesson — Google Cloud went down in October 2026 and took UK banks offline with it, and a Starlink outage left Ukrainian forces exposed and drew calls for a US Senate probe — because so much of the working day now runs through a handful of providers.

The scale is what makes this one hard to shrug off. Outlook, Teams and Copilot are not side apps for most offices; they are the working day itself, and when they stop, meetings, approvals and invoices stop with them. Microsoft's own service health documentation lists worldwide Microsoft 365 uptime of 99.526% for the first quarter of 2026 and 99.994% for the second, which is why a day like this one stands out — and why Microsoft's cloud business, which drove its October earnings, is judged as much on reliability as on growth.

What happens next

Two things were on the clock. First, the fix: it is done — Microsoft confirmed on Saturday, 14 November that services have fully recovered and the email backlog has been processed, closing the incident with an end time of Friday, 13 November, 4:10 PM UTC. Second, the explanation: Microsoft's service health documentation commits to a preliminary post-incident review within 48 hours of the incident being resolved, and a final review within five business days, WOM Technology reported. That final review should carry the confirmed root cause and the corrective actions Microsoft is taking.

The root cause is no longer unknown: Microsoft has named it as a network capacity upgrade issue that surfaced after a recent network change, and has said the underlying problem is addressed. What is still open is the full post-incident report, which Microsoft said it would publish once its review is complete. Service restoration is finished: Microsoft said the remaining affected customers and regions have been restored and the delayed-email backlog processed. Anyone still locked out of a mailbox should check the Microsoft 365 Status account on X or the Service health page in the admin center, not their own settings — and expect delayed mail to arrive in a batch once the backlog clears.