· Systems · 28 min read
A Post-Incident Report Is Not a Weather Report
A Microsoft 365 outage, a wave of infrastructure failures, and the uncomfortable question of what happens when software delivery accelerates faster than engineering discipline.

On October 26, 2026, Microsoft made an announcement that attracted quite a bit of attention. It was offering voluntary separation packages to roughly 60,000 employees — more than a quarter of its workforce. Not firing 60,000 people, of course. Inviting eligible employees to consider a generously supported change of scenery. Corporate language is a remarkable technology.
The stated context was cost control and organizational change, while Microsoft continued pouring extraordinary amounts of money into AI infrastructure. The obvious implication, at least in the public conversation, was that increasingly capable AI would allow the company to do more with fewer humans. Whether that assumption proves correct remains to be seen. So does the number of people who will actually accept the offer.
Seventeen days later, on November 12, a substantial part of Microsoft 365 stopped working.
Exchange Online took the worst of it. Mailboxes became inaccessible, messages were delayed, and numerous services relying on Exchange functionality suffered collateral damage. Microsoft 365’s rather extensive collection of product names suddenly became an equally extensive list of things that might not work as expected.
I had a suspicion about what would happen next. In fact, I told a few friends that the incident report would probably appear remarkably quickly — and that, whatever else it contained, it would most definitely not identify AI as the culprit.
The denial came first. On Friday, November 13, Microsoft publicly declared that the problem was not related to cyber or AI / agents. The fascinating part is the timing. In the very same service-health update, the company said it was still restoring service to remaining customers and regions. Its final incident update would not arrive until 04:17 UTC on Saturday, more than ten hours later. The preliminary post-incident report was dated November 15 and surfaced shortly afterward.
In other words, while the recovery operation was still underway, Microsoft had already established one very important part of the public narrative: AI wasn’t responsible. Getting everyone’s email working again would take a little longer, but at least that particular question had been settled. And that little slash in AI / agents deserves attention. It folds a broad category of technology and a much more specific mode of operation into one reassuring denial.
To be clear, I have no evidence that AI directly caused this incident, and the technical explanation offers no reason to believe it did. There is also nothing inherently suspicious about ruling out one cause before finishing recovery; incident responders do that all the time. But consider the asymmetry. The company could give the public an unequivocal answer about AI during the incident, while much less convenient questions about testing, isolation, capacity, rollback, and organizational choices would have to wait for a report — if they were addressed at all.
Maybe that was sensible rumor control. It was certainly convenient rumor control. AI is a centerpiece of Microsoft’s executive strategy, and publicly questioning a centerpiece is rather different from acknowledging a broken code path. I cannot establish the intent behind the statement, but I can read what it prioritized. An AI agent need not be anywhere near the failing servers for AI adoption to influence the engineering organization responsible for those servers.
I briefly considered translating the report from corporate English into something recognizable to engineers. Fortunately, somebody on Reddit already did precisely that, with enough technical accuracy and dry cruelty that I see little point in producing a worse imitation. I strongly recommend reading it.
Instead, I want to examine the things that the report says — and, more importantly, the questions it leaves hanging.
A Rather Familiar Kind of Disaster
Microsoft has been here before.
On March 15–16, 2021, a botched Azure Active Directory signing-key rotation disrupted authentication across a broad range of Microsoft and third-party services. The official impact window ran for roughly fourteen hours and twenty-five minutes. The immediate technical mistake was addressed much earlier; recovering the ecosystem that depended on those keys took considerably longer.
On October 29, 2025, Azure Front Door suffered a widespread disruption lasting about eight hours and twenty-four minutes. A configuration made it through deployment protections, then triggered a delayed failure in the data plane. The supposedly safe last-known-good state had also absorbed the bad configuration. The system designed to help recover from a bad change had, rather thoughtfully, preserved it.
I covered both incidents in The Fuckup Almanac, Volume I: Foundations of the Digital World. Anyone interested in their technical anatomy can find the original references in the book’s freely available bibliography. I won’t reproduce those chapters here.
Then came November 2026. Microsoft defines the active customer-impact window as 23 hours and 50 minutes, from Thursday afternoon to Friday afternoon UTC. But the recovery story didn’t stop there. The company continued monitoring stability and clearing the consequences of queued work before issuing its final incident update at 04:15 UTC on Saturday — almost 36 hours after the stated start.
Those are not 36 hours of uninterrupted global downtime. Some services and regions recovered earlier, and Microsoft’s report distinguishes active impact from the subsequent monitoring and backlog-recovery phase. Still, a 36-hour recovery operation for business-critical infrastructure is hardly a routine maintenance window. The final assurances also arrived as Europe entered Saturday morning, when many enterprise workloads would ordinarily have lighter traffic. That may have helped; without traffic data, it would be irresponsible to claim it did. It is, however, a perfectly reasonable question for a recovery assessment.
Different years, different systems, different failure modes. Three incidents do not establish a statistical trend, and comparing their durations alone would be lazy. But the recurrence of a more interesting pattern deserves attention: safeguards failed, the damage spread beyond its intended boundaries, and recovery proved more complicated than the design apparently anticipated.
In 2026, that pattern returned with considerable enthusiasm.
Apparently, Even the Recycle Bin Was Having a Difficult Year
Nor are reliability concerns confined to globally distributed cloud services, where one can at least invoke the extraordinary complexity of the machinery.
In January, a Microsoft Store-side problem prevented some users from launching such exotic applications as Notepad, Paint, and Snipping Tool. In March, Microsoft paused distribution of a Windows 11 preview update after discovering installation failures. The June Windows updates managed to confuse the Recycle Bin’s permanent-deletion dialog, displaying an internal filename rather than the name of the file a user was deleting. And a September update broke File History backups on some machines — a particularly unfortunate achievement for a feature intended to protect people from losing their files.
These were distinct incidents, with different causes, scopes, and severities. They are not proof of a single underlying defect or a measured, company-wide decline in quality. In fairness, the Notepad problem wasn’t even caused by an operating-system update. But taken together, they are enough to raise questions about release validation and operational discipline.
There is something almost endearing about watching a modern software company struggle with Notepad and the Recycle Bin. Neither product has been waiting for humanity to invent a viable use case.
But a comprehensive essay about Microsoft’s strategy, products, acquisitions, and business decisions would be a different article. Quite possibly a different blog.
This one isn’t really about Microsoft.
It’s about what happens when an engineering organization gets very good at describing failure without necessarily explaining the decisions that made failure possible. And lately, that question has become rather difficult to confine to a single company.
A Coincidence Worth Investigating
The period stretching from 2025 into early 2026 was not exactly a peaceful one for the world’s critical digital infrastructure.
In June, a Google Cloud disruption affected services across
multiple regions and spilled into Google Workspace. In October, a latent DNS automation defect in
AWS disrupted DynamoDB in us-east-1, then cascaded into EC2 instance launches and
load-balancer health checks. Later that month came Microsoft’s Azure Front Door incident. In November, Cloudflare suffered a
major outage after a permissions change unexpectedly altered the
contents of a configuration file distributed across its network. Less than three weeks later, Cloudflare had
another, this time while rolling out changes related to a security
vulnerability. In February 2026, a separate change to Cloudflare’s IP-address
management unintentionally withdrew routes for some
customers. That last incident had a much narrower scope, but illustrates how many different ways critical infrastructure can
misbehave.
(Several of these incidents also appear in Fuckup Almanac, Volume I. For the longer stories — or just the source material — see the book and its public bibliography.)
Different companies. Different systems. Different defects. Yet an uncomfortable number of failures in infrastructure on which other people’s businesses depend, with the sort of cascading consequences that redundancy and containment mechanisms are supposed to prevent.
Does that prove the industry’s outage rate is increasing? No. A selection of high-profile incidents is not a longitudinal reliability study. We would need consistent historical data, comparable definitions of impact, and some way to account for growing infrastructure complexity and dependency concentration. An especially memorable bad quarter is not, by itself, a statistically significant trend.
The Hidden Cost of Moving Faster
But something else has been changing across the industry at the same time.
AI-assisted software development has moved from an experiment to an ordinary part of the delivery pipeline. And the 2025 DORA research offers an interesting warning: greater AI adoption was associated with higher software-delivery throughput and lower delivery stability. AI can amplify existing engineering practices, certainly. But that is only half the problem. It can also put those practices under pressure in the first place.
Once someone demonstrates that a working-looking feature can be produced in an afternoon, the afternoon becomes the new benchmark. Design reviews, threat modeling, test environments, documentation, and the awkward business of understanding what the code actually does can start looking like unnecessary delays. The technology doesn’t have to tell anyone to skip those steps. A delivery target and a spreadsheet can do that perfectly well.
I’ve seen people in a legal department discover, with some excitement, that they no longer needed engineers to automate certain workflows. And in the narrowest possible sense, they were right: they could produce something that appeared to work. Whether anybody had thought through the failure modes, access permissions, edge cases, or who would maintain the result was a rather different question. I might have gone grey watching the consequences, if I hadn’t already been bald.
AI doesn’t merely amplify the engineering culture you have. By changing what management thinks delivery should cost and how quickly it should happen, it can help reshape that culture — and not necessarily for the better.
This is where second-order effects matter. There is a meaningful technical difference between AI-assisted coding and autonomous agents making decisions or changes. An agent independently triggering the outage could, in principle, be ruled out from incident evidence. A human engineer using AI assistance to produce a change months earlier is a different question. And whether an AI-driven delivery strategy has weakened review, testing, or operational understanding is a different question again. Microsoft’s public statement bundled “AI / agents” into a single denial. Perhaps its narrow technical conclusion was entirely sound. The broader reassurance that wording conveyed was considerably more ambitious.
And let’s remember something else — particularly when it happened. In April 2025, Satya Nadella said that roughly 20–30% of code in some Microsoft repositories was already being written by AI. April 2025. More than eighteen months before this outage. And Microsoft hardly spent that time easing off the AI accelerator. In its October 2026 earnings call, it was celebrating a sixfold increase in agent-generated pull requests across GitHub over six months. That’s a platform-wide figure, not a new measurement of Microsoft’s internal code, so we cannot turn it into an updated percentage. But assuming Nadella’s 20–30% had simply stood still for a year and a half would be a rather optimistic starting point.
None of that tells us whether AI had any involvement in the July gateway change. Still, it makes the November reassurance rather entertaining. Were we supposed to imagine that, while engineers were trying to restore service, somebody had already audited the relevant code and verified that this particular defect belonged to whatever portion of the codebase remained untouched by AI? Perhaps it came with a certificate: Guaranteed neural-network-free.
Of course not. That isn’t what the incident evidence establishes. And it isn’t necessary to accuse Microsoft of lying to notice the rhetorical trick: a narrow answer about direct causation can be heard as a sweeping answer about AI’s involvement, particularly when assisted development and autonomous agents are blurred together. Meanwhile, incentives, staffing, review capacity, and engineering priorities remain outside the frame. Those influences rarely appear in a stack trace. They are precisely the second-order effects worth investigating.
If assisted development increases the amount of code and the frequency of changes, do test coverage, review capacity, and operational understanding increase at the same rate? If management celebrates the shorter time from idea to deployment, who is measuring the time needed to understand, validate, maintain, and eventually repair what was deployed? If efficiency gains are used to justify smaller teams, does the reduced headcount come out of work that AI can genuinely replace — or out of the slack that made careful engineering possible in the first place?
None of this requires AI to be inherently bad at writing code. The problem is what organizations decide its apparent speed entitles them to cut: review time, staffing, training, testing, or all four. Speed is visible on a dashboard. The engineering work that prevents tomorrow’s incident is considerably harder to photograph for a quarterly presentation. And the highest-paid person’s opinion — the old HiPPO problem — becomes especially hard to challenge when it arrives with a C in the job title and a strategic commitment measured in billions.
And an organization can experience these effects without a single AI-generated line appearing in the eventual root-cause analysis. The incident report may accurately identify lock contention, failed isolation, or inadequate test hardware. It still won’t tell us whether the company has been rewarding delivery speed over validation, reducing the time allocated to design review, or treating the people who understand its failure modes as an inconvenient expense. Those would require a different kind of investigation. I am not claiming that Microsoft made any particular one of those trade-offs; I’m arguing that excluding direct AI involvement does not exclude the possibility of organizational consequences from the AI push.
Meanwhile, a different pipeline may be shrinking. In an August 2026 update to its labor-market research, Stanford’s Digital Economy Lab found that employment among 22-to-25-year-olds in occupations heavily exposed to AI was 19% below the level implied by the trend among less-exposed peers. The gap was driven largely by reduced hiring, not mass dismissals. That is not a measurement of engineering competence, and it does not prove that AI caused a particular outage. But it does raise a rather long-term question: where will tomorrow’s experienced engineers come from if we keep removing the entry-level work through which today’s experienced engineers learned their trade?
And we haven’t even addressed the enthusiasm for treating senior expertise as an expensive substitute for code generation. The person who knows why a rollback is dangerous, which dependency only exists on Tuesdays, or what the monitoring dashboard has quietly stopped measuring is not interchangeable with a machine that can produce a plausible implementation in thirty seconds. That knowledge is not necessarily documented. Sometimes it lives in someone’s memory because the last incident happened before the current management structure existed.
Put those things next to each other: a cluster of very visible infrastructure failures, rapid adoption of AI in the software development lifecycle, pressure to reduce staffing costs, and evidence that entry-level hiring is weakening in AI-exposed work. That is a worrying temporal correlation, not a demonstrated chain of causation. We cannot conclude that an AI-generated change broke AWS, Google, Cloudflare, or Microsoft merely because the dates fit an attractive narrative. Equally, declaring the changes unrelated without investigating their organizational effects would be an impressive exercise in selective curiosity.
When Software Becomes Critical Infrastructure
Imagine the power industry announcing that safety margins had become a little inefficient, that fewer apprentices were needed, and that faster reactor modifications more than compensated for the loss of experienced people. Nobody would regard a promise that most plants would remain operational as a particularly reassuring engineering strategy. There would be questions. Quite loud ones, probably asked at parliamentary hearings rather than sprint reviews.
And why should we find the same reasoning reassuring when the machinery happens to process packets instead of uranium? Our homes, hospitals, public services, emergency communications, and transportation increasingly depend on software infrastructure. In June 2019, a Google Cloud outage reportedly left some Nest users unable to unlock their smart locks remotely, control air conditioning, or access cameras. An internet outage managed to turn the front door into a customer-support problem. That particular episode of progress also made it into Fuckup Almanac, Volume I — with the sources available online.
During the November 2026 Microsoft outage, Cumberland County, North Carolina, asked residents to call or visit government offices because email was unavailable — and warned that some telephone and voicemail workflows depended on it too. Emergency services remained operational, thankfully.
But Cumberland was hardly alone. As The Guardian reported, the Los Angeles County Sheriff’s Department reported disrupted email and communications; emergency-management offices in Texas asked people to call rather than email; a Maryland water-and-sewer utility warned of delays and payment problems; and schools around Richmond, Virginia, directed parents to other ways of contacting them. Officials in Miami also reported services affected. Even a Colorado detention facility temporarily had to require in-person bond payments.
That’s a fairly impressive blast radius for what might otherwise be dismissed as an email outage. Not every emergency system went down, and the consequences differed from place to place. But when a single provider’s trouble simultaneously interferes with local government, law enforcement, schools, water utilities, and the release of detainees, we are well beyond someone being mildly inconvenienced by an unavailable inbox.
Then, on Friday, November 13, the FAA ordered a nationwide ground stop after a separate technical problem destabilized air-traffic communications and radar feeds. Departures resumed roughly five hours later. This was the second such nationwide halt since September 11, 2001, following another in 2023. It was not caused by Microsoft’s outage. That’s precisely why it belongs here: two unrelated failures, in the same week, reminding us how much of ordinary life depends on systems whose failure modes most people never get to see.
Let that sink in. In September 2001, it took a meticulously planned terrorist attack to halt departures across the United States. In January 2023, an accidentally damaged aviation-notice database was enough. In November 2026, a routine router replacement, a flood of network traffic, and some deeply unhappy legacy equipment produced another nationwide ground stop. The events and their human consequences were obviously worlds apart. But the same extraordinary operational measure that once followed a historic terrorist attack can now be triggered by a mundane technical failure. If that doesn’t illustrate how profoundly our dependence on interconnected systems has changed, I’m not sure what would. And unlike an attack, this one didn’t even need an adversary.
We’re not talking about a website refusing to load cat pictures. We’re talking about infrastructure people organize their lives around, and sometimes entrust their safety to. The responsibility to maintain safety margins, competent engineering teams, realistic tests, and credible recovery plans doesn’t evaporate because a system is called cloud rather than critical infrastructure.
Perhaps all these developments are unrelated. That possibility deserves a fair hearing. What doesn’t deserve a free pass is the assumption that speeding up production while thinning the layers of expertise and verification cannot possibly have a reliability cost. The distinction between direct technical causes and second-order organizational effects is not pedantry. It is the difference between investigating a broken component and investigating the system that allowed it to break so much.
And that brings us back to the incident reports — because if the industry is paying such a cost, the documents meant to help us understand it ought to ask questions considerably larger than which line of code failed.
When Incidents Become Weather Events
The preliminary PIR is detailed. It identifies a latent lock-contention defect introduced by a change first deployed in July. It describes a Teams traffic failover that shifted load onto gateway infrastructure also supporting Exchange Online. It explains how failures cascaded until more than 80% of the gateway servers became unresponsive. It describes why automated recovery struggled and why conventional rollback mechanisms could not quickly undo a change that had been in production for months.
These are useful facts. There is real engineering information in the document, and pretending otherwise would be unfair.
But read the grammar of the explanations.
A defect was present. Test conditions did not expose it. An unrelated issue removed capacity. A separate issue defeated isolation boundaries. The automatic recovery mechanisms were not designed for an outage of this scale.
Everything just sort of happened. Like rain. Or unusually ambitious fog.
Consider the load tests. Microsoft explains that the defect became more severe on newer, higher-core-count machines, while its test environments tended to use weaker hardware with fewer cores. The production conditions most likely to expose the defect were therefore poorly represented in the tests intended to uncover problems before production.
That’s a useful technical explanation. But who decided that those environments were representative enough? Was the mismatch known? Was there a conscious trade-off involving test cost, capacity, schedule, or some other constraint? If it wasn’t known, what process was supposed to ensure that production architecture and test coverage evolved together?
Those questions matter more than finding the developer responsible for the original lock contention. A developer can introduce a bug on a perfectly ordinary Tuesday. The organization is supposed to have multiple reasons why that bug does not subsequently disable half the planet’s email.
And then there is my favorite line in the report, in which Microsoft mentions that nearly 14% of the networking gateway’s server capacity was already out of service, thanks to an issue from the previous day. The report calls that issue unrelated and explains that the remaining capacity was sufficient on its own.
Fair enough. The 14% refers to this gateway fleet, not Microsoft’s entire worldwide infrastructure. And capacity degradation is not, by itself, a service outage; operating with spare capacity is precisely what redundancy is for.
But fourteen percent is not a rounding error. It represents a significant loss of headroom in infrastructure serving some of the world’s most widely used business services. The report treats it as one of three technical ingredients that combined to produce the catastrophe, then largely moves on.
What caused that earlier capacity loss? How was the operational risk assessed? What thresholds governed whether the system could safely absorb additional traffic? Did anyone have a consolidated view of the reduced headroom and the impending failover? Were the assumptions about simultaneous failures ever exercised?
Calling two incidents unrelated may be correct in the narrow sense that they originated from different defects. Unfortunately, distributed systems are remarkably uninterested in whether their failures have been introduced to each other formally. They interact anyway.
The same problem appears with the isolation boundaries that were supposed to prevent cascading failures between partitions. According to the PIR, a separate issue prevented those boundaries from doing their job. The report acknowledges the failure. It does not yet explain the organizational history that allowed such a critical protective mechanism to remain ineffective.
At that point, we are no longer examining three unlucky technical defects. We are examining the engineering decisions and risk assumptions under which three defects were allowed to combine.
Carefully Patching Half a Region
The recovery description is almost as fascinating as the root cause.
Microsoft says its normal automated procedures weren’t designed to recover from a fleet in such a broadly unresponsive state. Restored servers could be overwhelmed again as soon as waiting traffic returned. The original defect was too old for ordinary rollback, flighting, and feature flags to provide a quick escape.
So engineers developed an update to return the affected code path to a previously working state. They then removed groups of servers from service, applied the change, restarted them, and brought them back online. Microsoft says the operation was performed carefully, sometimes in batches covering more than half a region.
I have no doubt the engineers were careful. I also suspect that careful is doing an impressive amount of public-relations work in that sentence.
Here’s another concern: restoring an old code path is not the same thing as rolling the entire system back to July. Three months of other changes had happened in the meantime. Unless all of those changes were reverted too — which is not what the PIR describes — the restored behavior had to operate within the current system. Old and new code can each be correct in isolation and still find fascinating ways to disagree at their interfaces.
Perhaps the emergency update is flawless. I sincerely hope it is. The report records validation on subsets of the fleet and a staged recovery, so it would be wrong to call the deployment wholly untested.
But the July defect also passed testing and a gradual global rollout. It then spent over three months sitting quietly in production, waiting for the right combination of conditions.
Which raises an uncomfortable question: how many new dormant defects — or security weaknesses — might have been introduced while engineers were repairing a critical global service under extraordinary time pressure?
At the risk of becoming repetitive, let me revisit one more story from Fuckup Almanac, Volume I: the Y2K bug. The frantic remediation effort of the late 1990s helped avert a global catastrophe, but some of the quicker fixes merely moved the deadline. Then came the sequels: Y2K10, when millions of German bank cards stopped recognizing the year, and Y2K20, when some systems decided that 2020 was actually 1920. Not every later date bug was caused by a 1999 patch, but the broader pattern is familiar: an urgent workaround can solve today’s crisis and leave tomorrow’s problem patiently ticking away. Perhaps we’ll meet Y2K30 too. Backlogs have a remarkable tendency to prioritize issues according to how loudly the media is screaming now, while dormant defects are perfectly happy to wait decades for their next performance. The details — and the sources — are in Volume I.
This doesn’t establish that Microsoft’s emergency update introduced a new bug. It establishes something more useful: a repair that works today isn’t proof that the system is safe tomorrow. Particularly when the testing and recovery mechanisms meant to provide that confidence have just demonstrably failed.
And it is emphatically not an accusation against the engineers doing the repair. Their job at that moment was to get the world back online with the least additional damage possible. The more interesting question is why the organization left them in a position where emergency code changes and enormous, manually orchestrated rollouts were among the remaining options.
Heroes are useful during an incident. A culture that routinely needs heroes may have a more expensive problem.
The Difference Between Ending an Incident and Ending Its Consequences
Public incident communication has an unavoidable tension. A provider needs to keep customers informed without speculating, overpromising, or accidentally turning every early estimate into an admission with contractual consequences. I understand why lawyers and communications teams prefer carefully defined terms. Service-level agreements and possible compensation give those definitions real financial importance.
But there is a difference between precise language and language that makes the experience of affected users disappear.
Microsoft’s formal impact window ended after 23 hours and 50 minutes. At that point, the company says active customer impact had ceased. Yet the same chronology describes a further period of extended monitoring and backlog recovery, followed by the final communication almost twelve hours later.
A mailbox becoming accessible again is not the same thing as delayed messages having arrived, queued work having completed, or users having finished dealing with the disruption. From a customer’s perspective, recovery is a sequence of outcomes, not a status flag that changes when the incident bridge decides it has had enough.
None of this means Microsoft is obliged to count every minute of monitoring as downtime. It means the boundaries should be explicit — and we should be wary whenever a neat headline number is allowed to stand in for a much messier operational reality.
Blameless Is Not an Exemption From Accountability
I’ve written about this distinction before in my two-part Blameless Tragedy series: When Blameless Became Meaningless and Meet Reckless — Because Meaningless Isn’t Enough.
The central point is simple. A blameless post-mortem is supposed to make it safe to tell the truth. It was never supposed to make the truth irrelevant, or to remove every uncomfortable decision from the analysis.
Nobody needs a public list of engineers to blame for this outage. Singling out whoever wrote the July change would be easy, satisfying to some observers, and almost certainly useless. The original defect is only one part of the story. The tests, capacity policies, isolation mechanisms, recovery strategy, and acceptance of residual risk are parts of it too.
Those things don’t materialize spontaneously. They result from choices about budgets, staffing, architectural priorities, delivery schedules, and acceptable levels of risk. Some of those choices are made several layers above the people who eventually have to repair the consequences.
To be fair, this is a preliminary report. Microsoft lists completed immediate mitigations, including extra capacity, monitoring, and traffic-distribution guardrails, and promises a more comprehensive set of repair items in the final PIR, expected November 20. It may address some of the questions raised here. Public documents also cannot reveal everything discussed internally, and the absence of an explanation in a public report does not prove that nobody inside Microsoft is asking the right questions.
But that is precisely why the distinction matters: fixing the failure mode is not the same as addressing the decisions that allowed it to become a global incident.
More monitoring is useful. Additional capacity is useful. Better guardrails are useful. So is answering why the previous monitoring, capacity assumptions, and guardrails failed — and who is empowered to change the conditions that produced those failures.
The worst version of a post-mortem doesn’t necessarily contain falsehoods. Sometimes it contains perfectly accurate technical statements arranged so that no organizational decision ever has to be examined. The same trick works in incident communication: answer the question that protects the official strategy with absolute confidence, then reserve the complicated questions about the conditions that made the disaster possible for another day.
Everything is explained. Nothing is accountable.
What the Forecast Doesn’t Tell Us
Which brings us back to October 26 and the offer of voluntary exits to roughly 60,000 Microsoft employees.
I cannot connect that announcement causally to an outage triggered by code deployed in July. I don’t know who will leave, which teams will lose people, or how much expertise Microsoft will replace with AI rather than reorganize. Claiming otherwise would be replacing one kind of corporate storytelling with another.
But the juxtaposition still raises a serious question. If mature engineering teams, established deployment practices, multiple layers of redundancy, and automated recovery mechanisms could not prevent this failure or contain its consequences quickly, what makes the organization confident it can reduce its human expertise without weakening those systems further?
Saying AI didn’t cause the outage answers an important question about a specific incident. It does not answer whether AI-driven changes to priorities, staffing, training, and the software delivery process are making the next incident more or less likely — or more or less difficult to recover from. That is not an accusation. It is a risk-management question, and a rather obvious one for an engineering organization to ask.
And that question is not exclusive to Microsoft. It belongs to every company that mistakes faster code generation for a stronger engineering organization, or sees junior hiring and senior experience as two separate costs rather than different stages of the same investment. It belongs to every leadership team that treats operational resilience as a line item right up until the day it needs somebody to rebuild a critical service while the rest of the business waits.
Software defects happen. Hardware fails. Tests miss things. Occasionally, several improbable failures arrive together, each carrying a document explaining why it was somebody else’s problem.
That’s why we build layered protections. And that’s why we need engineering organizations willing to challenge the assumptions behind them — including the assumptions approved by management.
When the code fails, investigate the code. When the safeguards fail, investigate the safeguards.
When all of them fail together, investigate the decisions that made the catastrophe possible.
A post-incident report is not a weather report. The storm didn’t simply roll in. Somebody designed the drainage, approved the flood barriers, and decided how much rain the city should be prepared to survive.
And unlike the weather, those decisions can actually be changed.
If this article felt a little too much like a doomsday forecast, the Fuckup Almanac series offers more engineering disasters, more stories, and considerably more humor — with rather less impending-apocalypse energy. The questionable decisions, unfortunately, are just as real.
The November 2026 Microsoft 365 outage
The preliminary incident report, the contemporaneous service-health updates, and the announcement about voluntary departures.
6 sources
The November 2026 Microsoft 365 outage
The preliminary incident report, the contemporaneous service-health updates, and the announcement about voluntary departures.
- Microsoft (PDF mirror hosted by 365fanatic) Microsoft Corporation 2026Accessed: 2026-11-17
Preliminary report dated November 15, 2026. Covers the latent lock-contention defect, the failover, the unavailable gateway capacity, recovery actions, and initial repair items. A final report is promised for November 20.
- Reddit — r/sysadmin 2026Accessed: 2026-11-17
A satirical, engineer-oriented commentary on the preliminary PIR. Referenced as commentary, not as a primary source for incident facts.
- University of Pennsylvania 2026Accessed: 2026-11-17
Contemporaneous Microsoft 365 status messages, including the recovery updates through November 14.
- Reuters 2026Accessed: 2026-11-17
The October 26 announcement concerns employees eligible for voluntary separation, not 60,000 confirmed departures.
- The Guardian Mark Sweney, Josh Taylor, Aisha Down, Emma Elsworthy, Lauren Aratani 2026Accessed: 2026-11-17
Contemporaneous reporting on the outage and Microsoft’s statement that it was unrelated to AI agents or cyberattacks.
- BleepingComputer Lawrence Abrams 2026Accessed: 2026-11-17
Microsoft’s November 13 statement rules out cyber or AI / agents while acknowledging that restoration to remaining customers and regions was still underway.
Historical incidents covered in The Fuckup Almanac, Volume I
A chapter-organized collection of original reports, technical documents, and articles about incidents covered in Volume I and revisited in this essay, including Azure AD (2021), Azure Front Door (2025), AWS US-East-1 (October 2025), Cloudflare (November 2025), and Y2K-related failures.
1 sources
Historical incidents covered in The Fuckup Almanac, Volume I
A chapter-organized collection of original reports, technical documents, and articles about incidents covered in Volume I and revisited in this essay, including Azure AD (2021), Azure Front Door (2025), AWS US-East-1 (October 2025), Cloudflare (November 2025), and Y2K-related failures.
- Adam Korga Adam Korga 2026Accessed: 2026-11-17
Contains reports, primary documents, and articles describing the earlier failures covered in Volume I and referenced again in this blog post. More recent incidents not documented in the book have separate references here or direct links in the article.
Other major cloud incidents, AI-assisted development, and the engineering workforce
Reports about recent incidents not covered in Volume I, alongside research on AI-assisted development and the engineering workforce. Earlier case-study sources are consolidated under the book bibliography above.
7 sources
Other major cloud incidents, AI-assisted development, and the engineering workforce
Reports about recent incidents not covered in Volume I, alongside research on AI-assisted development and the engineering workforce. Earlier case-study sources are consolidated under the book bibliography above.
- Google Cloud Service Health Google Cloud 2025Accessed: 2026-11-17
- Cloudflare Blog Dane Knecht 2025Accessed: 2026-11-17
- Cloudflare Blog David Tuber, Dzevad Trumic 2026Accessed: 2026-11-17
A limited BYOIP routing incident caused by an IP-address management change; not comparable in scope to Cloudflare’s November 2025 network outage.
- TechCrunch Maxwell Zeff 2025Accessed: 2026-11-17
At LlamaCon on April 29, 2025, Nadella estimated 20–30% of code in Microsoft repositories was being written by AI. The estimate does not establish the provenance of the July 2026 gateway change or any particular production defect.
- Microsoft Investor Relations Satya Nadella 2026Accessed: 2026-11-17
Microsoft reported that agent-generated pull requests across GitHub had increased sixfold over six months. This is a platform-wide figure, not the share of code produced by AI within Microsoft itself.
- Google Cloud Blog Nathen Harvey, Derek DeBellis 2025Accessed: 2026-11-17
The 2025 research reports a positive association between AI use and delivery throughput, but a negative association with delivery stability. These are aggregate associations, not attribution of specific incidents.
- Stanford Digital Economy Lab Erik Brynjolfsson, Bharat Chandar, Ruyu Chen 2026Accessed: 2026-11-17
August 2026 revision: a 19% relative employment gap for workers aged 22–25 in AI-exposed occupations, compared with a less-exposed reference trend, driven primarily by reduced hiring rather than increased departures. Not a causal measure of infrastructure reliability.
When online infrastructure becomes essential infrastructure
Contemporary reports documenting real-world dependencies and the separate November 2026 FAA incident.
5 sources
When online infrastructure becomes essential infrastructure
Contemporary reports documenting real-world dependencies and the separate November 2026 FAA incident.
- Fast Company Michael Grothaus 2019Accessed: 2026-11-17
Reports of smart-home failures during the June 2019 Google Cloud outage. The smart-lock claim refers to remote or app-based operation, not evidence that every physical entry method failed.
- Cumberland County, North Carolina 2026Accessed: 2026-11-17
November 12 notice urging phone or in-person contact; warns that email-dependent voicemail and incoming-call workflows were affected.
- The Guardian Gaya Gupta 2026Accessed: 2026-11-17
November 13 reporting on disruptions to local government and essential services in Los Angeles County, Maryland, Texas, Virginia, Miami, and Colorado, with different impacts in different locations.
- Federal Aviation Administration FAA 2026Accessed: 2026-11-17
The November 13, 2026, nationwide ground stop was caused by a separate FAA telecommunications/network problem. Do not imply any causal link to Microsoft 365.
- Los Angeles Times Terry Castleman, Hannah Fry, Clara Harter, Iris Kwok, Richard Winton 2026Accessed: 2026-11-17
Windows quality and servicing incidents
Documented, distinct Windows and Microsoft Store incidents illustrating the difference between isolated bugs and a broader quality concern.
4 sources
Windows quality and servicing incidents
Documented, distinct Windows and Microsoft Store incidents illustrating the difference between isolated bugs and a broader quality concern.
- Windows Latest Mayank Parmar 2026Accessed: 2026-11-17
A Microsoft Store-side issue, not a Windows OS patch regression.
- Microsoft Support Microsoft 2026Accessed: 2026-11-17
Microsoft stopped offering the update to new devices after identifying an installation error.
- BleepingComputer Sergiu Gatlan 2026Accessed: 2026-11-17
- Microsoft Support Microsoft 2026Accessed: 2026-11-17
Microsoft documents a File History backup regression caused by the September update and resolved by a later update.



