MICROSOFT TURNS TO AWS FOR GITHUB CAPACITY AFTER AI SURGE

Microsoft is adding extra computing capacity to GitHub through Amazon Web Services, its arch rival in the cloud market, after a boom in AI coding tools overwhelmed the platform. The move marks a striking concession: a company that owns Azure, the second-largest cloud, is paying its biggest competitor to keep a flagship product running.

GitHub, which Microsoft acquired in 2018, used to run its own data centers. Microsoft had planned to migrate the platform entirely to Azure by 2027. Microsoft is accelerating that migration while also adding capacity from other clouds to handle the surge. The surge in AI-generated code has been so explosive that Azure alone could not handle the load in time.

THE CRISIS

GitHub commits were on pace to reach 14 billion in 2026, up from 1 billion in 2025. That is a 14x jump in one year, driven by tools like GitHub Copilot, Cursor, and Claude Code. The same tools that made developers more productive also swamped the infrastructure that hosts their work.

This year, GitHub suffered dozens of major outages. Mitchell Hashimoto, a prominent developer, wrote that the platform was "no longer a place for serious work if it just blocks you out for hours per day, every day." The frustration is real and shared. Outages that once were rare became routine, and the platform's reputation as a reliable home for open source and enterprise code began to fray.

WHAT ARE THEY DOING ABOUT IT

A Microsoft spokesperson confirmed the company is "both accelerating our move to Azure and continuing to explore a multi-cloud strategy to ensure we have the future capacity, compute elasticity and horizontal scale required to support continued growth." That is corporate language for

The spokesperson declined to confirm any Amazon involvement directly, but multiple reports place AWS as the provider. An Amazon spokesperson would not comment on individual clients, saying: "customers choose AWS because they need global infrastructure that performs reliably, securely, and efficiently at scale, and we're committed to providing the best performance no matter the workload."

SUPER AWKWARD FOR MICROSOFT

Giving Amazon more business, rather than addressing GitHub's needs via its own cloud, is not ideal. Microsoft and AWS compete aggressively for cloud market share. Every dollar Microsoft spends with AWS is a dollar that could have gone toward Azure's expansion. The fact that Microsoft is making this deal anyway tells you how severe the capacity crunch really is.

Microsoft recently projected its capital expenditures for the 2026 calendar year would reach $190 billion. Despite that massive spending, many data center projects have faced delays. The AI boom created a mismatch between the speed of demand and the speed of construction. Even with unlimited budget, you cannot build a data center in a month.

BIGGER INDUSTRY TREND

Microsoft is not alone in turning to a rival for help. AI demand is so strong that other big tech companies are making similar uncomfortable deals. Google, which runs its own cloud, agreed to sell AI compute capacity to Anthropic two months ago. And SpaceX and Google disclosed a new deal in which Google will pay SpaceX $920 million a month for AI compute capacity from October 2026 to June 2029. These cross-company, cross-cloud arrangements are becoming a feature of the industry.

The main goal is to keep popular services running for customers. When a platform like GitHub goes down for hours, trust erodes quickly. And GitHub has more competition than ever: AI coding tools like Cursor and Anthropic's Claude Code are directly challenging its position. In an internal meeting late last year, a Microsoft executive spoke about needing to overhaul GitHub to compete with those tools.

WHAT THE MULTI-PIVOT MEANS

The multi-cloud strategy is not a retreat from Azure. Microsoft is still pouring money into its own cloud. But the GitHub situation demonstrates that no single provider can guarantee infinite elasticity at the pace AI demands. Companies that once aimed for single-cloud lock-in are now forced to mix providers, often with their direct competitors.

For GitHub users, the immediate upside is that the platform should become more stable. AWS brings well-established global capacity that can be spun up faster than new Azure regions. The downside is that the complexity of managing multiple clouds increases, and the security boundary between Microsoft's code and Amazon's infrastructure must be carefully maintained.

GROWTH VS INFRA

This is a story of growth outpacing infrastructure. AI coding tools made developers dramatically more productive, and the resulting flood of code broke the system that was supposed to hold it. Microsoft's response, eating crow and paying Amazon, is pragmatic but revealing. The cloud market is no longer about who wins and loses. It is about who can keep the lights on while everyone rushes to build more servers.

GitHub will survive this. But the days of a single company's cloud being enough for the AI era are over.