Nadella warns some critical infrastructure cannot be patched as AI attacks accelerate
At DealBook, Microsoft’s CEO described shrinking time to test security fixes. His explanation for the recent Outlook outage, however, centered on a latent bug.
Loading page…
At DealBook, Microsoft’s CEO described shrinking time to test security fixes. His explanation for the recent Outlook outage, however, centered on a latent bug.
Listen to this story
At the November 18 DealBook Summit, Satya Nadella argued that defenders have less time to test security fixes before vulnerabilities are exploited, increasing the risk that rushed deployments disrupt live services. He also highlighted a harder limit: internet-connected equipment such as chillers and transport systems may contain firmware vulnerabilities that cannot be patched. For operators, his proposed response includes modernizing that infrastructure and strengthening real-time threat detection and defense, not just speeding up software updates.
Microsoft’s Outlook disruption lasted from 4:20 p.m. UTC on November 12 to 4:10 p.m. UTC on November 13, according to Startup Fortune’s account of a preliminary report.
That account cited a latent networking-gateway defect, redirected Teams traffic, and about 14% of gateway capacity being offline; it described these as non-AI causes.
Nadella said Microsoft would apply lessons from the outage to its architecture and operations; a final incident report was still pending.
Microsoft CEO Satya Nadella warned at The New York Times’ DealBook Summit that AI is compressing the time companies have to fix security flaws, while some internet-connected critical infrastructure cannot be patched at all. His remarks, reported by TechCrunch, describe two problems: rushing fixes into live systems can cause instability, and some equipment cannot receive those fixes.
The November 18 appearance followed Microsoft’s recent Outlook disruption. Nadella described that failure as a “latent bug” that produced a “perfect storm.” He said Microsoft had issued an incident response and would apply what it learned to both the underlying architecture and day-to-day operations.
Startup Fortune, citing MLQ.ai’s account of Microsoft’s preliminary incident report, placed the disruption between 4:20 p.m. UTC on November 12 and 4:10 p.m. UTC on November 13. It relayed three contributing factors:
The account identified those as non-AI causes.
At the summit, Nadella described AI as a powerful tool for discovering vulnerabilities. He contrasted that capability with the time companies previously had to understand a flaw, test a patch and then deploy it. The pressure now, in his telling, is to move a fix into production—the systems customers actually use—as soon as it becomes available.
The urgency comes from flaws already being exploited, rather than simply from having more bugs to investigate. Nadella’s concern was that the interval available for checking a fix is being squeezed by the need to stop an attack. He warned that this accelerated process would itself create instability.
His infrastructure warning went beyond the software services involved in the Outlook incident. Nadella pointed to firmware—the software embedded in equipment—and cited chillers and heating, ventilation and air-conditioning systems. He emphasized that such equipment is connected to the internet, putting physical infrastructure within the discussion of software vulnerabilities.
He also relayed a conversation about transportation systems containing firmware with discoverable vulnerabilities that could not be patched.
For those systems, Nadella’s proposed response extended beyond speeding up software updates. He called for modernization, followed by an assessment of the threats and the ability to detect and defend against them in real time.
For Microsoft’s own outage, a more concrete checkpoint remained: Startup Fortune said the final incident report was due within five business days of full resolution. The account said it had not yet been published.
Loading discussion...
Join the conversation
Explain when keeping it connected would—or would not—be justified.
Be the first to share a perspective or an experience.
Reader comments
Newest comments first. Replies stay oldest first.