LIVE
SpaceX Catches Starship From Orbit  •  Microsoft 365 Outage Fully Restored  •  Ramayana Crosses 1,200 Crore Worldwide
Tech

Microsoft 365 Fully Restored After 38-Hour Outage

By Toijam Bimoljit Singh • 15 November 2026 • 4 min read

A tree-lined plaza between office buildings on the Microsoft campus in Redmond, Washington

Photo: Jonathan Schilling, CC BY-SA 4.0, via Wikimedia Commons — a plaza between buildings and walkways on the Microsoft campus in Redmond, Washington.

TL;DR — the direct answer: Microsoft confirmed on Saturday, 14 November, that Microsoft 365 is fully restored after a global outage that disrupted Outlook, Teams, Copilot and other services for about 38 hours. The company's final incident updates, posted in the early hours of Saturday, said the services across the previously affected environments had fully recovered and the backlog of delayed email had been processed. Microsoft blamed an issue during an earlier network capacity upgrade that surfaced after a recent network change, and said it was not a cyberattack and not related to artificial intelligence. One preliminary estimate put the global productivity cost at close to $7 billion.

What happened: The outage began at 16:17 UTC on Thursday, 12 November, when users in the Americas lost access to their Exchange Online mailboxes. Microsoft then opened a wider incident, tracked as EX1550543 for Exchange Online and MO1550821 for Microsoft 365. It hit Outlook, Teams, SharePoint, Copilot and other services that depend on Exchange Online. Downdetector logged problem reports from more than 70 countries, with the peak for Outlook put at more than 120,000 reports. Microsoft extended the email timeout window to 48 hours so delayed messages would not bounce. Microsoft recorded the end of the impact at 4:10 p.m. UTC on Friday, 13 November, but kept the incident open overnight while the email backlog drained, and only gave the all-clear on Saturday morning — about 38 hours after the outage began. Its final updates, at 4:15 a.m. GMT for Exchange Online and 4:17 a.m. GMT for Microsoft 365, said the issue was remediated.

Why it's trending: Microsoft 365 is the plumbing of the modern office, with more than 430 million people using its apps, so a failure that lasts more than a day hits businesses, schools, government agencies and hospitals all at once. Some businesses fell back on telephones and fax machines, and one US company delayed an earnings call because of the outage. Government systems in Singapore and Japan were disrupted, as were communications at the Supreme Court of the Philippines. The near-38-hour outage was one of Microsoft's longest in years, and a preliminary estimate of a productivity cost approaching $7 billion made it one of the week's biggest business stories.

Background / context: Microsoft's preliminary explanation is short: the incident was introduced by an issue during an earlier network capacity upgrade, which surfaced after a subsequent network change. The central problem during the recovery, Microsoft explained, was that restored servers 'can become unresponsive again once they receive traffic', so each wave of recovery collapsed under the weight of users reconnecting. Microsoft confirmed there is no evidence of malicious activity, and the final update called it 'a technical issue not related to cyber or AI / agents'. Microsoft Threat Intelligence separately warned of a phishing campaign impersonating legitimate Microsoft 365 service health alerts and referencing the genuine Exchange Online incident, EX1550543.

What we know / what's unconfirmed: Confirmed: the start time of 16:17 UTC on Thursday, 12 November, the two incident IDs, the services affected, the scale of Downdetector reports across more than 70 countries, the end of impact at 4:10 p.m. UTC on Friday, the final all-clear on Saturday morning, and the email backlog being processed. Unconfirmed: the full root cause. Microsoft has named the network capacity upgrade in one sentence but has not explained what exactly went wrong, why the recovery kept collapsing, or what it will change to stop it happening again — all of that waits for the promised post-incident report. The $7 billion figure is a preliminary outside estimate, not Microsoft's own number.

What happens next: For users, the outage is over: mailboxes are reachable, delayed email has been delivered, and the status page shows every product as operational. Administrators and compliance teams now wait for Microsoft's formal post-incident report, which should explain how a fault introduced during a capacity upgrade slipped through and knocked out so many servers at once. Users should also be wary of phishing emails about the outage: scammers are already sending fake service health alerts citing the real incident number.

Frequently asked questions

Q: Is Microsoft 365 back to normal now?
A: Yes. Microsoft confirmed on Saturday, 14 November, that the services across the previously affected environments have fully recovered, the backlog of delayed email has been processed, and its status page reads 'All products are operational.'

Q: When did the outage start and end?
A: It began at 16:17 UTC on Thursday, 12 November. Microsoft recorded the end of impact at 4:10 p.m. UTC on Friday, 13 November, and gave the final all-clear on Saturday morning, about 38 hours after the start.

Q: What caused the Microsoft 365 outage?
A: Microsoft blames an issue introduced during an earlier network capacity upgrade, which surfaced after a recent network change. The full post-incident report has not been published yet, so the detailed root cause is still to come.

Q: Was it a cyberattack?
A: No. Microsoft says there is no evidence of malicious activity, and its final update described the cause as a technical issue not related to cyber activity or AI systems.

Q: Which services were affected?
A: Outlook, Teams, SharePoint, Copilot and other services that depend on Exchange Online. The outage was reported in more than 70 countries.

Sources: NewsDrum — Microsoft services back after 38-hour outage; $7 billion productivity hit estimated, KeyXplore — Microsoft 365 Outage (12-14 Nov 2026): Fully Restored. Cause, Timeline and What to Check Now, and EpiFive — Microsoft 365 Outage Nov 2026: Resolved, Cause, Next Steps.

← Back home