Note: This post was written by Claude Fable 5. The following is a synthesis of Microsoft’s incident communications, live outage-tracker data, and industry reporting, plus firsthand observation from this site’s editor.
At 11:08 AM Eastern this morning, something went wrong inside the authentication plumbing of Exchange Online — and it hasn’t come back. As of publication, more than six hours later, Microsoft is still testing fixes for what it calls “an issue within a core authentication configuration used by multiple Microsoft 365 services,” with no estimated time to resolution and a next update promised for 6:00 PM EDT.
The word “degraded” in Microsoft’s advisories is carrying a lot of weight. For plenty of organizations, email simply stopped. “Degraded? Nothing works for our entire company,” one user replied to Microsoft’s status account on X.
What Broke
Microsoft is tracking the incident under two IDs in the Microsoft 365 Admin Center: EX1464935 for Exchange Online, the hardest-hit service, and MO1465074 for the wider suite. The Exchange advisory lists delays or failures sending and receiving mail, authentication errors, broken mailbox search, and trouble reaching its admin tools — and notes that “all connection methods are affected,” so switching from Outlook to the web client or a phone doesn’t route around it.
The suite-level advisory reads like a blast-radius diagram of what one shared authentication component touches: OneDrive and SharePoint failing to load files, search, and lists; Teams losing calendar functions, search, and presence; intermittent authorization failures across Microsoft Purview and Defender XDR; and Purview admins locked out of their portal entirely. Even the admin center itself is listed as impaired.
Notably, Microsoft Entra ID is not the named culprit. As of late afternoon, Azure’s public status page still listed Entra as healthy; Microsoft’s language points at an authentication configuration inside Microsoft 365’s own service infrastructure. Consumer services — Outlook.com, personal OneDrive — are listed as operational. This one belongs to the business and enterprise side.
The Numbers
Downdetector’s curves tell the story compactly. US reports for Outlook jumped from a baseline of a few dozen to 1,789 at 11:42 AM EDT, peaked at 6,027 half an hour later, and plateaued near 5,800 through the lunch hour. The separate Microsoft 365 page peaked at 2,043 reports at 1:42 PM, with 78% of complaints filed under Exchange. Both curves were declining slowly — not collapsing — through late afternoon, still running near 3,500 and 900 at 5:07 PM. Tom’s Guide’s live blog logged reports from across the US plus Guatemala, Uruguay, and Argentina.
Five hours in, one Downdetector commenter had moved to contingency planning: “Now distributing stamps & envelopes to our team. Printer is working overtime.”
A Fix That Won’t Deploy
Microsoft’s remediation narrative has wobbled as the afternoon wore on. At 1:23 PM it had “identified a potential corrective action” and was evaluating deployment. By 2:25 PM it was testing “a potential remediation.” By 3:43 PM it was still running “comprehensive tests” while exploring alternatives. The 4:36 PM update went somewhere more revealing: engineers are “reexamining recent changes made to the service to determine why the authentication components aren’t being deployed as expected,” and are weighing “reverting an update the affected infrastructure recently received.”
Read plainly: more than five hours in, Microsoft was still working out why its own fix wasn’t landing, with a rollback on the table. Community threads have floated a more specific theory — an administrator in the comments at Born’s Tech and Windows World captured a Partner Center error naming an expired certificate by thumbprint. Microsoft has not confirmed any certificate connection, and the official root cause remains the generic “core authentication configuration.”
The Quiet Channel Problem
Microsoft’s public communication today consisted of two posts on X — 12:01 PM (“We’re investigating reports of Exchange Online issues”) and 12:43 PM — each pointing users to EX1464935 in the admin center. Nothing since. Tom’s Guide checked Microsoft’s public health dashboard at 2:28 PM and found every product listed as operational; the incident text didn’t surface publicly until later in the afternoon. When status.cloud.microsoft finally flipped to “service degradation,” it carried a candid admission: the information was being posted there “because Microsoft 365 administrators may be unable to access the admin center to get Service health information.”
That’s the structural problem in one sentence. When the thing that breaks is authentication, the incident report lives behind a sign-in.
The View From One Inbox
This site’s editor, R.A.Parks, watched the incident the way most people did — as an inbox that went silent. He has received no work email since 12:17 PM EDT, a drought still running at publication. It’s the second time this year his employer has lost email to a Microsoft 365 incident: a January 22 outage stopped inbound mail for a few hours the same way.
An afternoon without email is not a catastrophe in any single office. Multiplied across every organization that has consolidated mail, files, chat, compliance, and security tooling onto one vendor’s authentication stack, it’s a reminder of what that convenience costs on the wrong Monday. The suite is the single point of failure now — and today’s is the fifth incident on Microsoft’s public status feed in under three weeks, following Exchange Online trouble on August 14, a South America network issue on the 19th, license-activation failures on the 24th, and Teams degradation in Asia-Pacific on the 26th.
As of publication, six hours in, nothing had changed: the advisories still said “service degradation,” Downdetector still showed thousands of active reports, and no new mail had arrived.
Sources
- Microsoft service health status — status.cloud.microsoft
- Microsoft 365 Status on X — 12:43 PM acknowledgment
- BleepingComputer — Microsoft Exchange Online outage causes email failures, auth issues
- TechCrunch — Microsoft tests fix for latest hours-long Outlook outage
- Tom’s Guide — Is Microsoft Outlook down? Live tracking email outage
- Downdetector — Microsoft 365 and Downdetector — Outlook
- Born’s Tech and Windows World — EX1464935: M365 outage and the certificate question