Introduction
When Microsoft acquired GitHub for $7.5 billion in 2018, Satya Nadella promised to maintain its developer-first ethos while gradually shifting its infrastructure to Azure. Today, an unexpected pivot is taking place: Microsoft is turning to Amazon Web Services (AWS) to support GitHub, underscoring the pressure from the AI-driven coding surge.
The Rise of Agentic Development
Since late 2025, GitHub has experienced an "incredible spike in agentic development," according to a Microsoft spokesperson. With commits projected to reach 14 billion in 2026, up from 1 billion the previous year, GitHub's infrastructure is under immense strain.
Why AWS?
Although Microsoft owns Azure, a cloud market leader, the urgency imposed by GitHub's growth necessitated a multi-cloud approach. AWS, with its elasticity and scale, was chosen to prevent critical outages. This decision highlights the challenges of hyperscale infrastructure where reliability outweighs rivalries.
Implications for Microsoft and GitHub
Multi-Cloud Strategy
Turning to AWS isn't just a stopgap measure. It marks a strategic shift towards a multi-cloud approach, enabling GitHub to leverage the flexibility and resilience required at such a scale of growth. This could also influence other major companies to consider similar strategies to avoid single-vendor lock-in.
Pressure on Azure
This decision highlights Azure's current limitations. While Microsoft planned to fully migrate GitHub to Azure by 2027, reality has caught up with planning. The pressure is now on Azure to quickly evolve and meet the increasing demands of its services.
Conclusion
Microsoft's use of its main competitor's cloud capacity for GitHub is a significant turn in the hyperscale infrastructure race. It demonstrates how the rise of AI is transforming not only developer tools but also the underlying infrastructure strategies. For tech decision-makers, this raises essential questions about managing growth and infrastructure resilience.
Let's discuss your project in 15 minutes.