HLD Pulse · Outage · 13 November 2026Recovering

Microsoft 365 goes down worldwide. Outlook was out for more than a day in places.

From early afternoon US Eastern time on Thursday 12 November, Outlook, Exchange Online, Teams, SharePoint, Copilot and Defender XDR failed for organisations across at least 74 countries. Microsoft says the cause was a fault in its own network, not an attack. Mail was still catching up on Friday, and Microsoft has not yet declared the incident fully resolved.

What happened

Microsoft first described the problem as “elevated load across multiple regions”. By Thursday evening it had narrowed that down: “the elevated load isn’t driven by an increase in traffic, but by a number of servers being unexpectedly unavailable; straining the remaining infrastructure.” Servers were failing automated health checks and dropping out of service, which pushed more work onto the ones still running.

Microsoft paused all deployments, restarted servers and switched to an alternative health check to bring capacity back. Recovery was slow and uneven. On Friday morning Al Jazeera reported servers that had come back were failing again in Europe.

On Friday Microsoft told ABC News: “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 has said there is “no indication” of malicious activity and has promised a full post-incident review.

Services affected

  • Exchange Online and Outlook

    Hit hardest. Mailboxes would not connect or load, and mail delivery was delayed for many hours.

  • Microsoft Teams

    Partly disrupted. Chat and calls kept working for many users, according to Al Jazeera.

  • SharePoint Online and OneDrive

    Named in Microsoft’s advisory. CNBC reported SharePoint still largely down on Friday morning US time.

  • Microsoft 365 Copilot

    Named in Microsoft’s advisory and still disrupted into Friday.

  • Microsoft Defender XDR

    Named in Microsoft’s advisory. A gap in security tooling during an outage deserves its own check.

Consumer users of Outlook.com, OneDrive and Teams were also affected. Downdetector complaints also named Azure and the Microsoft Store.

Who was hit

  • In Australia, Al Jazeera reports an intelligence agency and the Australian Federal Police were among the organisations hit. Home Affairs Minister Tony Burke said Microsoft told him it did not believe it was facing a cyberattack.
  • Government systems in Singapore and Japan were disrupted, as were communications at the Supreme Court of the Philippines.
  • The UK NHS said some services were affected and told patients to attend appointments as normal. New York City Emergency Management warned email to city agencies could be delayed and told residents to call 311 or 911.
  • Air India rerouted email to keep receiving customer messages. Richemont’s earnings release slipped, and Workhorse Group moved its quarterly results by four days, citing the outage.

While the outage is running

  1. 1Tell staff early through a channel that does not depend on Microsoft 365: SMS, a status page, or a phone tree. Say which systems are down and how to reach the service desk.
  2. 2Warn staff that phishing often follows a big outage. Treat emails offering a “fix”, asking you to re-enter Microsoft credentials or to install a tool as hostile until verified.
  3. 3Do not change MX records or start forwarding mail to personal accounts to get around the outage. Microsoft is retrying delivery for 48 hours, and ad-hoc forwarding leaks data.
  4. 4Check whether Defender XDR alerts and other Microsoft-hosted security tooling kept working. If they did not, treat the outage window as a monitoring gap and review it afterwards.

Once service is back

  1. 1Once mail flows, check for delayed or missing inbound mail from customers, regulators and courts, and for anything that bounced back to senders.
  2. 2Record the outage in your incident register with its start and end times and business impact. Contracts, service levels and regulatory deadlines may turn on it.
  3. 3Read Microsoft’s post-incident review when it is published and compare its timeline with your own logs.
  4. 4Write down which critical processes stopped because email or Teams stopped, and decide which ones need a fallback that does not depend on the same provider.

A single point of failure

Minister Burke compared the disruption to the 2024 CrowdStrike outage. The causes are different: CrowdStrike pushed a faulty update to customers’ own machines, while this fault sat inside Microsoft’s cloud. What they share is that one provider’s mistake stopped work at thousands of unrelated organisations at once.

For most organisations email, chat, file storage and parts of the security stack now come from the same provider. When that provider fails, the tools used to coordinate a response fail too. A plan for this does not need a second email system. It needs an agreed way to reach staff, customers and suppliers that does not run through Microsoft 365, and a list of which processes can wait a day and which cannot.