Your inbox is not ignoring you. Microsoft’s cloud is. The Microsoft 365 outage that knocked out Outlook, Teams and Copilot on Thursday is still not fully fixed this morning, a rare modern failure that outlasts a full workday and then some.
If your email has been acting up since lunchtime yesterday, it was not your Wi-Fi, and it was not you. Our earlier report on the first hours of the failure has the opening timeline.

What happened in the Microsoft 365 outage
Microsoft first said it was investigating mailbox access problems shortly before 1 p.m. ET on Thursday, Nov. 12, according to ABC News. The trouble then spread well beyond email (email, it turns out, was just the opening act). Coverage names Outlook, Teams, Copilot, Exchange Online, SharePoint Online, Defender XDR, Planner, To Do, Intune, OneDrive, Windows 365 and cloud printing.
Azure, Microsoft’s cloud platform, stayed online, per NBC News. Downdetector logged more than 130,000 Outlook problem reports at the peak. New reports have since fallen, the AP reports.
The scale is hard to overstate. Microsoft says more than 430 million people use its 365 apps, according to CBS News.
Nobody has measured how many of them were actually hit, so treat “hundreds of millions affected” as a ceiling, not a count.
What Microsoft says caused the Microsoft outage
Microsoft’s explanation so far is technical and short on detail. The company said a portion of its infrastructure is “experiencing elevated load across multiple regions,” with other servers “unexpectedly unavailable,” per Deadline. Microsoft also pointed to a component that processes server health.
One early fix did not work. Microsoft’s phrasing was that the attempt was “not taking as expected.” It also says there is “no indication this is the result of malicious or cyber activity.”
Recovery is coming in pieces. Actions have finished across parts of the infrastructure in Asia Pacific. As of about 7 a.m. ET, Microsoft saw “encouraging recovery progress” in Europe, and its status account reported “early stabilization.”
Microsoft had not declared the incident over in any source we reviewed.
Here’s the thing: this Microsoft email outage was not just an email problem
Email is the quiet plumbing of the working world. When it stops, a lot more stops with it.
Japan’s government said the outage hit its IT infrastructure. Chief Cabinet Secretary Minoru Kihara said multiple services, including Outlook, became unavailable. The Philippine Supreme Court said some operations were affected. A California sheriff’s department and other California agencies reported communications problems, per NBC Los Angeles.
Businesses felt it too. Workhorse Group delayed an earnings call. Even OpenAI and Anthropic reported trouble connecting to Microsoft 365 tools, the AP reports. That is a spicy detail, since Anthropic is already taking on Microsoft and Google with its own office tools.
Wall Street noticed as well. Microsoft shares were about 2% lower in premarket trading Friday, according to CNBC.
So who gets burned? The small business whose customer replies went nowhere. The parent waiting on a school email. The employee whose calendar invite vanished into the void. For all of them, Microsoft 365 down meant a stalled day.
Why this Outlook outage stands out
Big outages are not new. Microsoft’s Azure outage in late October 2025 ran more than eight hours, and the July 2024 CrowdStrike update triggered a global Windows meltdown. But that one was a third-party software update, not a failure inside Microsoft’s own cloud.
This one is different in length. Bloomberg notes that earlier disruptions rarely lasted more than several hours, and calls this one of Microsoft’s longest outages. No source has put a total hour count on it yet.
What to do and what happens next
If you manage a company’s Microsoft setup, check the Microsoft 365 admin center under Health, then Service health, for tenant-specific updates. Everyone else: expect delayed messages and a pile of catch-up email once service settles. This Microsoft 365 outage is not over until Microsoft says so.
Three things to watch. First, whether Microsoft declares full recovery. Second, whether it publishes a root-cause report, since the cause is still not final. Third, whether any mail backlog or customer pushback shows up; no sourced reporting on either exists yet.
Microsoft says it will treat the incident “with urgency until full mitigation.” For a company that sells reliability as a feature, the real question is how long customers keep taking that on faith.






