It was just after lunch on the East Coast when the inboxes went quiet.
People clicked send and nothing happened. Refresh buttons spun. Outlook refused to load at all. For millions of workers in the middle of their Thursday, email simply stopped working, and nobody at Microsoft could yet say why.
By early afternoon, the problem had a name and a scale. This was not a glitch in one app. It was a Microsoft 365 outage that pulled down Outlook, Teams, SharePoint and Copilot, and it would take Microsoft the rest of the working day to start putting it back together.
What Happened During the Microsoft 365 Outage
The first signs appeared late on Thursday morning. Microsoft’s own service health notice puts the incident start at 11:17 a.m. Eastern Time, when users in the Americas began having trouble reaching their Exchange Online mailboxes.
At 12:54 p.m. ET, Microsoft’s official status account posted on X that it was investigating reports of people unable to access Exchange Online mailboxes “through multiple connection methods in the Americas”, and pointed administrators to incident EX1550543 in the Microsoft 365 admin center.
Within the hour, the scope widened. What had started as an email problem became a platform-wide one. Microsoft later confirmed the disruption reached Microsoft Teams, SharePoint Online, Microsoft 365 Copilot and Microsoft Defender XDR, with more services added to the list as the afternoon wore on.
Users described the same symptoms everywhere. Outlook would not load, messages would not send, Teams calls dropped, and Copilot refused to answer. Some could reach the apps but not their data. Others could not sign in at all.
How Big Was the Microsoft 365 Outage?
Outage tracker Downdetector recorded nearly 130,000 reports of Outlook problems shortly after 1 p.m. ET, with around 48,000 reports for Microsoft 365 itself and 10,000 more for the Microsoft Store.
The reports kept coming from far beyond the United States. Downdetector logged outages in 74 countries, and users in New Zealand reported problems from early Friday morning local time, hours after the trouble began in the Americas.
The numbers fell through the afternoon as Microsoft worked on the problem, but they stayed high. At 5:32 p.m. ET, Downdetector still showed 38,456 Outlook reports and nearly 17,000 for Microsoft 365, according to USA Today’s live coverage.
For a service that businesses treat as plumbing, invisible until it breaks, the scale was hard to ignore. Outlook is the default inbox for much of corporate America, and Copilot is Microsoft’s flagship AI assistant. When both go dark on the same afternoon, meetings, deals and deadlines all stall at once.
What Microsoft Says Caused the Outage
Microsoft has not named a root cause, and it has been careful about what it rules out. The company said the elevated load on its infrastructure was not caused by a surge in traffic. Instead, a large number of its own servers unexpectedly became unavailable, and the load shifted onto the machines that remained.
In a later update, Microsoft said it had found that “a core process on affected servers is becoming overwhelmed, causing capacity loss”. The servers were failing automated health checks and dropping out of service, which pushed more work onto the survivors and made the problem worse.
The company also said it was reviewing “a small number of configuration updates” as potential contributors, and that it had paused all deployments while the investigation continued. Nothing Microsoft has published points to a cyberattack, and the company has not linked the outage to anything external.
That last point matters because the timing invited speculation. The outage arrived two days after Microsoft’s November Patch Tuesday, which delivered more than 1,000 fixes including an actively exploited Outlook flaw, a story wasl.tech covered earlier this week.
Microsoft has not connected the two events, and the outage was a cloud connectivity problem in Exchange Online infrastructure, not a flaw in the software on users’ machines.
The Slow Road Back: Recovery Under Way
Microsoft’s first response was to move traffic. The company said it was redistributing connection traffic across its worldwide infrastructure, shifting load off the affected systems and restarting servers to return them to service.
By mid-afternoon, engineers had validated an alternative way of checking server health, which let a subset of the failed servers come back online. Microsoft said it was applying that change more broadly, and at 4:40 p.m. ET it reported that it was “actively restarting and validating the affected servers to return them to service”.
An hour later, the tone turned more sober. At around 5 p.m. ET, Microsoft said “our actions taken thus far have not provided the anticipated relief” and that it was “continuing to pursue all available pathways to restore service”.
The first real sign of progress came at 6 p.m. ET, when Microsoft reported it was “returning a portion of affected servers to the service, and they remain stable so far”. The company said it was shifting traffic to alternate routes wherever possible and observing “limited recovery” in some regions, with a gradual recovery expected as clients reconnected.
As of Thursday evening, Microsoft had not declared the incident over, and no time for full restoration had been given. Administrators were told to follow incident EX1550543 and advisory MO1550821 in the Microsoft 365 admin center, or the status page at status.cloud.microsoft if the admin center itself was unreachable.
What to Do If Your Outlook Is Still Down
If your mailbox is still unreachable, there is little to fix on your end. The problem sits in Microsoft’s infrastructure, not in your app or your connection, so reinstalling Outlook or resetting your password will not help.
The practical steps are simple. Check Microsoft’s status page before troubleshooting your own setup, and watch the Microsoft 365 Status account on X for the latest updates. If your mail has returned, expect some slowness while the remaining servers come back online. Microsoft warned of possible latency while traffic is being redistributed.
Businesses that rely on Exchange Online should also check whether queued messages are flowing again before resending anything, to avoid flooding colleagues with duplicates once the backlog clears.
Why This Microsoft 365 Outage Matters
This is the second major Microsoft 365 outage this year, and it lands at an awkward moment for the company. Microsoft has spent 2026 pushing Copilot into every corner of its productivity suite, and the outage took the AI assistant down with the email it is meant to enhance.
The incident also underlines how concentrated modern office work has become. One cloud platform now carries email, chat, file storage, security and AI assistance for millions of organisations, so a single infrastructure failure can idle whole companies at once.
Microsoft has spent the year deepening its enterprise AI push, including a joint platform with IBM that puts thousands of AI agents inside big businesses, which makes the reliability of the underlying cloud matter even more.
Researchers who study these failures will also be watching what Microsoft says next. The company has promised a post-incident report, and the question everyone will ask is how a core process could overwhelm enough servers to take down a service of this size, and what changes so it cannot happen again.
The episode is a reminder, too, of how much of the AI boom runs on the same plumbing. Microsoft’s own researchers recently showed how a handful of reprogrammed neurons could turn an AI agent rogue, a story wasl.tech covered earlier this week.
Thursday’s lesson was simpler: the most advanced AI assistant in the world is useless when the email beneath it stops working.
What Happens Next
Microsoft is still bringing servers back online, and the recovery is expected to be gradual rather than instant. Users should see service return in waves as capacity is restored, with some regions recovering before others.
The company has promised further updates as the work continues, and a full explanation once the investigation is complete. Until then, the outage stands as the biggest test of Microsoft’s cloud resilience this year, and a reminder that even the companies building the future still have to keep the lights on.
