Microsoft Explains Last Week's 365 Outage
Microsoft has now explained the recent Microsoft 365 outage in a preliminary post-incident report.
Why am I seeing this Single-sourced — only TechPowerUp has this
Only TechPowerUp has this. It is here on that single source, so read it as one outlet's reporting until somebody else confirms it.
Single-sourced. No second organisation has confirmed it yet.
Link-outLink-out, because only one organisation carries it and no first-party source is on it. Link-out means we point at the publisher and say nothing of our own.
| Factor | Weight | Score | Contribution | Where it came from |
|---|---|---|---|---|
| Corroborationleads | 0.35 | 0.39 | +0.135 40% | 1 independent org on the story. Tier-3 aggregators never corroborate — they can show something is circulating, never that it is true. |
| Source trust | 0.25 | 0.44 | +0.110 33% | TechPowerUp is the highest-trust source on this story. Trust is taken from the best source, not averaged. |
| Pickup rate | 0.20 | 0.00 | +0.000 0% | One counted organisation, so there is no spread to measure — nothing has picked this up to set a rate. |
| Freshness | 0.20 | 0.45 | +0.089 27% | Halves every 10 hours from the newest item on the story. This is the only factor that rewards a story for nothing more than being recent. |
Corroboration counts distinct organisations, once each, and only from tiers 1 and 2. Freshness halves every 10 hours, so this ranking is a snapshot and will differ at the next build.

What happened
Microsoft has now explained the recent Microsoft 365 outage in a preliminary post-incident report. According to Microsoft, customers were impacted for just under 24 hours, from 4:20 PM UTC on November 12 to 4:10 PM UTC on November 13. The outage prevented many users from accessing their mailboxes in Outlook and delayed email delivery. Moreover, Microsoft Teams, Copilot, SharePoint, and OneDrive were all affected in some way, which is expected since these services all have features that rely on Exchange Online. The company has traced the outage to three problems that hit Microsoft at the same time. The main culprit is said to be a fix that had been prepared specifically for Microsoft 365 gateway servers.
How this story arrived
Ordered by when each source was first observed, which is what the velocity figure is computed from. Publishers backdate; observed order does not.
- 01 Techpowerup first seen Microsoft Explains Last Week's 365 Outage
Overclock clusters coverage from independent sources and grades it automatically. The figures above are computed, not editorial. This page summarises and links to reporting by the outlets named — follow the links for the original work.