Silent Configuration Drift: The Microsoft 365 Outage and the Missing Assertion

A Microsoft 365 bug went undetected from July 2026 and contributed to a worldwide disruption, with the apparent peak on 13 November 2026. Coverage published on 16 and 17 November reported Microsoft's apology and three underlying causes. It did not name the affected component, the mechanism, or whether the July change was code, configuration, or data. That four-month window is the interesting part. Liveness monitoring asks whether a process is answering. Conformance monitoring asks whether state still equals what you decided. They fail independently, so a system can be fully live and silently wrong, with every uptime check green. The detector in this video is constructed to illustrate the failure shape. It is not a claim about Microsoft's internal configuration, which the public record does not describe. Full write-up: https://hackyjs.com/posts/silent-configuration-drift-what-the-microsoft-365-outage-reveals-about-detection-gaps

microsoft-365cloud-reliabilityincident-responsemonitoringconfiguration-drift

Read the post →

 
Silent Configuration Drift: The Microsoft 365 Outage and the Missing Assertion - Hacky JS