Microsoft Taps AWS for GitHub Capacity as AI Coding Boom Strains Azure

Microsoft is using Amazon Web Services to add computing capacity for GitHub, following significant capacity issues on the coding platform. The decision comes after AI-powered coding tools triggered unprecedented development activity on GitHub, which Microsoft acquired in 2018.

Business Insider reported on June 16 that Microsoft is turning to Amazon to help address capacity challenges at GitHub. The report cited two people familiar with the plans, noting that Amazon remains Microsoft’s largest cloud rival in the infrastructure market.

Microsoft had planned to move the platform entirely to Azure by 2027. However, the recent surge in AI-assisted development has forced the company to adopt a more flexible approach. The platform’s recent capacity challenges stem from AI-powered coding assistants that make it dramatically easier for developers to generate software at scale.

Explosive Growth in Development Activity

GitHub serves as the primary platform where developers store code, manage software projects, and collaborate on development tasks. Before Microsoft acquired the company, GitHub mostly operated its own data centers rather than relying on third-party cloud providers.

The reported use of AWS follows higher development activity tied to AI coding tools. GitHub Chief Operating Officer Kyle Daigle wrote on X in April that commits were on pace to reach 14 billion in 2026, compared with just 1 billion in 2025. A commit represents a recorded code change and serves as a common measure of development activity across the platform.

This flood of new code has strained GitHub’s compute resources substantially. The platform has suffered dozens of major outages in 2026, disrupting work for developers worldwide. GitHub’s own May availability report documented nine incidents that caused degraded performance across GitHub services that month.

Microsoft Confirms Multi-Cloud Strategy

According to Business Insider, Microsoft is adding extra compute capacity through AWS to handle the increase in GitHub activity. A Microsoft spokesperson confirmed that GitHub is using multiple cloud providers but declined to comment specifically on Amazon’s involvement in the arrangement.

“The incredible spike in agentic development that began late last year has tested our infrastructure’s limits,” the spokesperson said.

Microsoft emphasized that it is accelerating GitHub’s move to Azure while continuing to use a multi-cloud strategy to ensure elasticity and scale. The company’s approach reflects the practical reality that migration timelines drawn before the AI coding boom may no longer match current infrastructure demands.

An Amazon spokesperson told Business Insider that the company does not comment on individual customers. The spokesperson did not address Microsoft or GitHub directly, maintaining Amazon’s typical stance on client relationships.

Competitive Cloud Market Dynamics

Microsoft and AWS compete fiercely in the cloud infrastructure market, where Azure and AWS both serve enterprise cloud workloads. The fact that Microsoft owns both GitHub and Azure makes the turn to AWS particularly notable. This shows that practical infrastructure needs can override competitive considerations when platform reliability stands at stake.

Microsoft projected $190 billion in capital expenditures, largely to expand data center capacity for AI workloads. Despite this massive investment, delays in building out infrastructure have left GitHub vulnerable during the AI-driven surge in coding activity.

Similar multi-cloud arrangements are emerging across the technology sector. Google recently agreed to pay SpaceX $920 million for AI compute capacity, while also selling compute resources to Anthropic. These deals reflect the intense demand for computing power driven by AI development.

Agentic Development Creates New Pressure

The shift from simple code autocomplete to full coding agents represents the real pressure point for GitHub’s infrastructure. A simple Copilot suggestion in an editor creates a bounded request with predictable resource needs. In contrast, a coding agent can read an entire repository, plan complex tasks, make changes, run tests, revise its work, and open pull requests automatically.

GitHub’s product has moved rapidly in this direction. Microsoft’s migration plan for GitHub was drawn up before the agentic coding boom fundamentally changed the platform’s resource requirements. That plan suddenly looked inadequate when AI-assisted development exploded across the developer community.

When GitHub slows down or blocks work, repositories, pull requests, CI pipelines, code reviews, and AI agents all stack up behind the same infrastructure bottleneck. For developers, these are not abstract infrastructure problems but real disruptions to daily workflows and project timelines.

GitHub Faces Rising Competition

For Microsoft, the priority remains keeping GitHub operational amid rising competition from AI-native platforms like Cursor and Anthropic’s Claude Code. Critics, including HashiCorp cofounder Mitchell Hashimoto, have warned that GitHub risks losing credibility if outages persist at current levels.

Microsoft executives have acknowledged internally that GitHub needs a significant overhaul to remain competitive in the AI era. The platform must handle not just traditional developer workflows but also the exponentially larger computational demands created by AI coding assistants and autonomous development agents.

The arrangement with AWS represents more than a temporary fix. AI-driven development activity has outpaced even the most aggressive cloud infrastructure expansion plans from major technology companies. The numbers tell the story: moving from 1 billion to 14 billion commits in a single year represents a fundamental transformation in how software gets produced.

Microsoft’s willingness to engage its biggest cloud competitor highlights the stakes involved. GitHub serves as critical infrastructure for millions of developers worldwide, and any extended downtime carries significant consequences for software development across industries. Maintaining platform reliability has become more important than maintaining a pure Azure-first strategy, at least until Microsoft can bring sufficient capacity online to handle the new AI-driven workload patterns independently.