Microsoft 365 Goes Dark: Outlook, Teams and Copilot Down

Human Verified 0

Share to: , and

A dark office at dusk with rows of blank computer monitors

Microsoft’s cloud went down for millions of people on Thursday, taking Outlook email, Teams calls and its Copilot assistant offline in the middle of the workday. The company says the trouble started with its Exchange Online mailboxes in the Americas and widened into a Microsoft 365 service incident by early afternoon, with users in any region potentially affected. More than 130,000 people reported Outlook problems at the peak, and Microsoft has not said when full service will return.

What went down

The incident is tracked as EX1550543 for Exchange Online and MO1550821 for the wider Microsoft 365 suite. The advisory lists Exchange Online, Teams, SharePoint Online, Microsoft 365 Copilot and Microsoft Defender XDR among the services customers may be unable to reach.

Outage tracker Downdetector recorded more than 130,000 Outlook reports at 1:27 p.m. Eastern, plus over 46,000 for Microsoft 365 and around 3,000 for Teams. Reports also spiked for OneDrive, Azure and the Microsoft Store. The figures count reports filed, not users, so the true number affected is unknown.

Microsoft first blamed elevated load, then corrected itself: the load was not driven by extra traffic, but by servers becoming unexpectedly unavailable and failing automated health checks. The surviving servers took on the extra strain, which made the problem worse. The company has paused deployments, redistributed traffic and is restarting affected servers to restore capacity.

A technician checking a server rack in a dark data centre corridor

A second incident the same morning

The outage followed a separate Teams incident earlier on Thursday that hit users in North and South America from 9:45 to 10:53 a.m. Eastern, delaying messages and blocking chat updates. Microsoft blamed resource contention inside its infrastructure and said that incident was fully resolved around noon. The company has not said whether the two incidents share a cause.

The disruption also reached the AI services built on Microsoft’s cloud. OpenAI reported problems with its Microsoft 365 connectors, warning that new connections might fail and tools might not work properly. Anthropic reported the same problem with its own Microsoft 365 connector. Copilot and its rivals were left unable to reach users’ inboxes while the underlying services stayed down.

Our Read

Read plainly, this is the second large Microsoft 365 outage of 2026, and the repeat is the story. The first, on 22 January, lasted close to ten hours. This one began as a morning Teams fault and widened into a suite-wide failure by the afternoon. Microsoft’s own servers failed the health checks meant to catch exactly this.

The caveat is that Microsoft has not published a root cause, and its 5:09 p.m. update said the steps taken so far had not brought the relief expected. A core process on the affected servers was becoming overwhelmed, costing capacity. Until the post-incident review lands, the lesson is narrower: one overload can interrupt email, meetings and AI assistants at once.

Why It Matters

It matters because Microsoft 365 is the working day for millions of workers, and this outage hit email, meetings and AI help at once. When Outlook, Teams and Copilot fall together, there is no fallback inside the same suite. The outage also exposed how deeply AI assistants depend on the same plumbing, as Copilot’s rivals were cut off too.

For businesses, the question is what Microsoft’s review will say about the health checks that failed. The company owes a preliminary review within 48 hours of resolution and a final one within five business days. Until then, the outage is a reminder that the cloud’s points of failure now include the AI layer, as Microsoft’s own agent research keeps showing.

Background

Microsoft 365 serves businesses, schools and government offices worldwide, and its last large outage, on 22 January, lasted close to ten hours. Microsoft tracks incidents in its admin centre and posts updates on its Microsoft 365 Status account, where administrators can follow EX1550543 and MO1550821.

Source: Reuters’ report on the outage and BleepingComputer’s coverage.

Share to: , and

Faheem R. Khattak

Senior automation engineer and AI marketing journo covering LLMs, algorithms, analytics, core updates, Bing search, and technical SEO.

0 Comments

Leave a Reply

Optional Take Tag:

🛡️ Spam protection: Honeypot + Time-Trap Active

This site uses Akismet to reduce spam. Learn how your comment data is processed.