Three small failures combined to take down Microsoft 365
A hidden defect in Microsoft's cloud gateway, dormant since July, was to blame for one of the largest outages in the company's history last week. A preliminary Post-Incident Report (PIR) released by the company outlines how the latent bug, changes in traffic, and reduced server capacity combined to knock much of Microsoft 365 and Exchange infrastructure offline at the end of last week. Microsoft's report lists the incident's final status as "a technical issue not related to cyber or AI/agents."
Microsoft's preliminary report places the outage between November 12 at 16:20 UTC and November 13 at 16:10 UTC, just under 24 hours total, and additional monitoring remained in place for any affected systems through November 14.
The outage started on November 12 and quickly rippled through businesses and public offices that depend on Microsoft's cloud and email exchange infrastructure. The outage is covered in Microsoft's incident IDs EX1550543 and MO1550821. You need Microsoft 365 admin credentials to see the full report on the company's status pages, but Office Watch has reproduced the preliminary report, and the University of Pennsylvania maintains an archive of Microsoft's service-health updates.


Β© Getty Images






I was flummoxed to read a report on how much memory Microsoftβs Weather app uses on Windows 11 β more than 1GB just to render what is, ostensibly, a fancy table of stats. Less surprising is that the GNOME Weather app does the same job for under a fifth of the reported Windows figure, while Mousam, my go-to weather app, uses around a third of Microsoftβs effort (and with a nicer design, too). Not everyone on Windows 11 is seeing memory usage as high as the 1.1GB figure given in Windows Latest viral post. But when I check on my [β¦]