If your Outlook has been spinning since lunchtime, you weren’t imagining it, and no, it wasn’t your Wi-Fi. The Microsoft 365 outage hit Thursday afternoon and, as of late evening, it still wasn’t fully fixed.
It was not a one-app hiccup, either. Microsoft’s own status posts list Exchange Online, Teams, SharePoint, Copilot and Defender XDR as potentially affected, and the list kept growing as the day went on. For anyone who runs a business, a school or a hospital on this stuff, that is the whole workday.

What we know about the Microsoft 365 outage
Microsoft says the incident began at 1:26 PM ET, though it had started looking into Exchange Online mailbox problems in the Americas earlier. In its first post, reported by Variety, the company said it was investigating reports of users “experiencing issues accessing Exchange Online mailboxes through multiple connection methods in the Americas.”
It did not stay in the Americas. Microsoft later warned that 365 connectivity could be hit for users in any region. Downdetector logged roughly 130,000 Outlook problem reports shortly after 1 p.m. ET, according to CNBC. Keep in mind those are user reports, not an official headcount.
By about 5 p.m., Planner, To Do, Intune, Defender for Office 365 and Purview had joined the list, Engadget reported. Microsoft is tracking the problem in its admin center under incident ID EX1550543.
Why the Microsoft outage explanation keeps changing
Here’s where it gets interesting. Microsoft first blamed “elevated load across multiple regions.” Sounds like too much traffic, right? Not so fast. Microsoft then said the load “isn’t driven by an increase in traffic, but by a number of servers being unexpectedly unavailable; straining the remaining infrastructure.”
In plain English, some servers fell over, and the ones still standing got crushed trying to pick up the slack. Think of a restaurant where half the waiters walk out mid-dinner rush. Microsoft told CNBC some of the affected servers were failing automated health checks. It later said a core process on those servers was becoming overwhelmed.
The fix attempts have been a bit of a whack-a-mole game. At 4 p.m., Microsoft said it had validated an alternative service health check method that brought some servers back online. BleepingComputer reported limited recovery by 6:57 p.m. ET. After 7 p.m., Microsoft acknowledged that some servers were not coming back correctly, so it temporarily limited which traffic types could reach the affected infrastructure in some locations.
As of Gizmodo’s 10:10 p.m. ET update, the outage was still ongoing and most Exchange-linked services were still flagged on the status page.
Was this Microsoft 365 outage a cyberattack?
The question is out there, and it’s a fair one to ask. But here’s the honest answer: nothing so far points that way. I found no reporting and no Microsoft statement suggesting an attack. The company’s explanation points to an internal server and health-check failure. Treat any talk of hackers or AI gone rogue as speculation until Microsoft says otherwise.
The real root cause of this Microsoft 365 disruption is also still unknown. Microsoft has not published a post-incident review, and accounts differ on whether a recent change to the health-check component played a part.
Here’s the thing: this is a dependency problem
Fox Business, which covered the outage, cites roughly 321 million Microsoft 365 users worldwide. When a platform that big stumbles, the damage isn’t a few annoyed office workers. Datafloq reports that Michigan Medicine had trouble reaching Outlook, and that Henry Ford Health lost Outlook and Teams, citing The Detroit News.
Email is plumbing now, and plumbing breaks at the worst times.
It’s also not the first time this year. A January 22 outage ran nearly 10 hours and hit Outlook, Defender and Purview, and The Register reported Microsoft blamed North American infrastructure “not processing traffic as expected.” Twice in one year is a pattern worth noticing.
The timing is awkward for Microsoft, too. It is also a partner and rival in the AI race, as we covered when Anthropic took on Microsoft and Google, and a day like this hands competitors a talking point. Across the tech industry, reliability is suddenly the story.
What happens next? Microsoft hasn’t declared this Microsoft 365 outage over. Watch the 365 status page and the @MSFT365Status account for updates, and keep an eye out for that post-incident review. If the answer to “what broke?” turns out to be a health check that couldn’t tell healthy servers from sick ones, that’s a pretty humbling way to ruin a Thursday for 321 million people.






