Ex-Microsoft engineer blames Azure problems on talent exodus • The Register
Ex-Microsoft engineer blames Azure problems on talent exodus • The Register
https://www.theregister.com/2026/04/04/azure_talent_exodus/
Publish Date: 2026-04-04 06:00:00
Source Domain: www.theregister.com
In 2024, federal cybersecurity evaluators reportedly dismissed Microsoft 365 Government Community Cloud High (GCC High) as garbage, although they used a more colorful term. To understand why, it helps to consider the history of the underlying Azure infrastructure.
Axel Rietschin, who worked as an engineer on Azure Core Compute for a year and as a Windows Base Kernel engineer for eight years before that, has now written a less dismissive but more damning history of his experience with the Microsoft cloud service.
In a series of six essays (so far), he recounts how Microsoft rushed Azure to market in 2008 to compete with Amazon Web Services and squandered opportunities for stability while failing to support staff.
“Azure never operated as smoothly or independently as promised,” Rietschin wrote. “What Microsoft presented to the world, and to its most demanding customers, was a sophisticated system perpetually on life support.
“This foundational fragility, rooted in rushed decisions and wishful thinking about how fast the platform could grow and stabilize, led to small but ongoing disruptions. Over time, those disruptions built up.”
Rietschin argues that Microsoft’s rushed launch of Azure, the “post-launch talent exodus,” the lack of software quality and testing discipline, the lack of architectural vision, and persistently poor execution have left the cloud service fighting fires ever since.
The flames are only occasionally visible on the outside – for instance, in ProPublica’s report detailing the government’s dissatisfaction with Azure services, and in OpenAI’s $11.9 billion compute deal with CoreWeave on March 10, 2025, which Rietschin points to as a vote of no confidence in Azure.
“One can reasonably infer that Microsoft struggled to meet OpenAI’s demanding requirements on time and at scale,” he wrote, and…
