Everyone covered the outage. Almost nobody explained what broke.
Microsoft's Outlook and Teams went down for roughly 130,000 users on Thursday afternoon, peaking just before 1:30 p.m. ET. Microsoft blamed servers that "unexpectedly went unavailable," which strained remaining infrastructure and cascaded across 365 services. Nineteen outlets covered the disruption. Quartz was the only outlet that ran explainers on what Exchange Online actually is, why cloud outages recur, and how businesses file SLA claims afterward. The rest reported the number and moved on. When the same infrastructure fails again, the coverage will look identical.
Microsoft Outlook and 365 services hit by widespread outage affecting 120,000+ users
16 sources · hover a dot to see coverage
What happened
On Thursday, November 12, Microsoft's Outlook, Teams, Copilot, and other Microsoft 365 services went offline across multiple regions. Reports peaked at nearly 130,000 users on Downdetector just before 1:30 p.m. ET. Microsoft acknowledged the issue on its service status page, attributing it to servers that "unexpectedly went unavailable," which placed elevated load on remaining infrastructure. The Guardian reported Microsoft said it was "aggressively pursuing all pathways to reduce impact" and had begun restarting servers. Fox Business specified the disruption was a "multi-region" event. Services began returning, though no single outlet published a confirmed restoration time. The Atlantic piece in this group covers a French writer and is unrelated to the outage. That is the wire version. Twenty outlets have it. What separates the coverage is almost nothing.
Quartz ran three explainers while everyone else filed one brief
Quartz published three separate pieces alongside the breaking news: a primer on what Exchange Online is and why its failures reach so many users, a breakdown of seven common causes of cloud outages (configuration changes, DNS failures, sign-in failures among them), and a guide to how businesses claim SLA service credits after a Microsoft 365 disruption. No other outlet in this group ran any of that. The practical consequence is that Quartz readers finished the outage knowing whether their company could file for a credit and through which channel. Everyone else's readers knew the number was 130,000.
Fast Company treated the social media reaction as the story
Fast Company's piece led not with the outage mechanics but with workers joking on social media that Microsoft should "take its time" bringing Outlook back. The framing is accurate as a cultural observation and the piece does note the scale of the disruption, but the lede buries the technical event under the vibe. It is the only outlet in this group that treated exhausted-worker Twitter as the primary news hook rather than a color paragraph.
Fox Business was the only outlet to specify multi-region scope explicitly in its headline
Fox Business headlined "multi-region connectivity issues" and named "elevated infrastructure load" as the mechanism, matching Microsoft's own language more precisely than most. CNBC and The Verge covered the same facts but kept geographic scope vague. The distinction matters for enterprise readers trying to assess whether a regional failover was possible. Reuters and Al Jazeera both cited Downdetector figures without adding regional detail.
What one side told you that the other didn't
Nobody asked why this keeps happening. Quartz answered anyway.
Microsoft has had multiple high-profile outages in recent years, and the seven causes Quartz listed (bad configuration changes, DNS failures, capacity miscalculation, cascading load) are the same mechanisms that appeared in the July 2024 CrowdStrike-adjacent Azure incident. Every other outlet treated Thursday's event as discrete and novel. None cited prior outage history or asked whether Microsoft's infrastructure investment has kept pace with 365 adoption. The story that recurs every six months got covered as if it had never happened before.
SLA credits exist. Nineteen outlets didn't mention them.
Businesses running on Microsoft 365 are entitled to service credits under Microsoft's SLA when uptime falls below 99.9 percent, but the claim process runs through Cloud Solution Providers, not directly through Microsoft, and covers only the affected service prorated by outage length. Quartz explained all of this. The other nineteen outlets reported an outage that cost businesses real money and left readers with no information about recourse. The gap is not a framing choice; it is a beat gap. Enterprise tech coverage requires knowing what an SLA is.
The outage cause stayed vague across fifteen outlets.
Microsoft's own status page said servers "unexpectedly went unavailable" and created elevated load on remaining infrastructure. That is a description of what happened, not an explanation of why. The NYT reported it straight. The Guardian added that Microsoft was "restarting" servers. Nobody pressed further on whether this was a capacity failure, a bad deployment, or a dependency issue. For an event affecting 130,000 users at peak, "unexpectedly unavailable" is the kind of non-answer that should generate a follow-up question. It generated seventeen paraphrases instead.
What to watch
Microsoft typically posts a Post-Incident Review to its Azure status history page within 72 hours of a major outage. If that review publishes before Monday, November 17, watch whether tech outlets pick it up and whether the root cause named there matches the vague "elevated load" language from Thursday. If the PIR names a specific failure type (configuration change, dependency, capacity), any outlet that covered the outage without that detail will have a second chance to explain what actually broke. Most will not take it.
See how outlets across the political spectrum framed this differently — and what each side left out.