The big Microsoft outage, AI and a comprehension debt

A global outage affecting Microsoft’s enterprise and consumer services stretched into several hours on Friday. The company described the impact on apps including Outlook, Teams, OneDrive and Office on the web as a “service degradation”, while engineers tried implementing fix after fix.

Fourteen hours later, Microsoft finally said it had started noticing “positive results for service stability and increased capacity”, but the disruption was far from over. The cause officially cited was that something in the system caused otherwise perfectly fine servers to start failing automated health checks, which meant the load was shifted to other servers."We’re seeing encouraging recovery progress, with service availability and email delivery performance improving across a growing portion of affected infrastructure.

We know our customers rely on our services to get important work done every day, and regret the impact these outages had on those who depend on us. Our teams are reviewing what happened and how we can prevent similar issues going forward,” says Charles Lamanna, EVP, Copilot, Agents and Platform at Microsoft, in a statement shared with HT.

The cause officially cited was that something in the system caused otherwise perfectly fine servers to start failing automated health checks, which meant the load was shifted to other servers. They also began to struggle as a result, leading to instability.

While Microsoft hasn’t yet attributed the outage to any code written by artificial intelligence (AI), it comes against the backdrop of the tech giant’s aggressive AI deployment. Two pressing questions have emerged: are companies relying too much on AI to write code, and are they quietly losing the institutional understanding needed to fix their own systems in times of crisis?

Govind Rammurthy, CEO and managing director of eScan, an enterprise security company, says this raises legitimate structural questions, which must nevertheless be contemplated despite Microsoft not attributing the failed automated health checks that triggered the cascading effect to AI-generated code.

“Speed and scale are not the problem; irreversibility is, as has been seen in this specific case of outage,” he says. In April last year, CEO Satya Nadella claimed that as much as 30% of the code within the company was being written by AI already, and that share was increasing steadily.

In June this year, Microsoft wound down and cancelled internal direct licences for Anthropic’s Claude Code for internal use, due to massive token consumption and compute costs. Microsoft nudged engineers to use its own GitHub Copilot CLI, an autonomous, terminal-native AI coding agent.

Compared with Claude, it is a bit more cost-effective. It isn’t clear what level of human oversight remained for the code being written by AI. Microsoft reiterated throughout the hours of the outage that no malicious activity or cyberattacks were behind it.

Nevertheless, the impact has been global and widespread — affecting schools, government services, banks and even airline communication and support services in some countries. As AI agents write and commit millions of lines of code, with enterprises believing the process is faster, more accurate and cost-effective compared with human coding, that pace is often faster than humans can review the code, if they review it at all.

Even without a smoking gun having been discovered in the Microsoft outage, enterprises and hyperscalers are adopting the concept of ‘comprehension debt’, where no single human engineer fully understands the system architecture when a novel failure needs to be resolved.

Engineers may have to read through thousands of lines of code to understand what went wrong. “Since AI-assisted development and agentic coding have become commonplace, organisations find themselves in a stage of producing code at an unprecedented rate.

The rate at which code is created outpaces any kind of testing or validation techniques available today,” says Padma Reddy Sama, CTO and co-founder of BharathCloud, an enterprise cloud platform. Sama insists that when systems and components develop and evolve rapidly, engineering teams lose their ability to understand the interactions between those components and potential risks.

“In today’s daily software development routine, AI agents write, save and commit code at a very rapid pace. And, when AI agents commit code faster than human engineers can meaningfully review it, organisations accumulate what you correctly call comprehension debt: systems that work until an edge case hits, at which point no single engineer holds a complete enough mental model to diagnose quickly,” Rammurthy explains.

“Comprehension debt builds when understanding of a system lags behind how quickly it changes. Organisations adopting AI at enterprise scale generally find the answer lies in better process design. The priority is to structure AI workflows around clear ownership: someone accountable for each agent-generated change, architectural choices on record, and closer review where the potential impact is greater,” says Shailesh Dhuri, CEO and co-founder of Decimal Point Analytics, a research firm.

An illustration of why comprehension debt is a problem is provided by instances of false positives that Microsoft’s 365 Status account on X shared in the early hours of the outage. “Our mitigative actions have successfully restored service health and functionality.

Customer impact is now fully resolved,” the account posted, with a sense of achievement. But that was not the case, as users around the world discovered in the hours that followed. Taran Srivastava, co-founder of ML.ai, an AI infrastructure company, says, “Writing code used to be the slow part of software.

Now the slow part is understanding it, and when agents commit changes faster than people can review them, the gap between what’s been shipped and what anyone can explain keeps widening.” By estimates, Microsoft has let go of around 8,000 employees...