Microsoft is securing extra cloud capacity from Amazon Web Services to relieve mounting infrastructure pressure at its GitHub development platform, according to people with knowledge of the plans. The move is intended to address capacity constraints that emerged as AI-driven coding activity substantially increased demand on GitHub's systems.
Company officials have not positioned the use of AWS as a replacement for Microsoft’s long-standing plan to migrate GitHub entirely onto Azure by 2027. Instead, the additional capacity from a rival cloud provider is being used to meet near-term demand while the company pursues its longer-term Azure migration goal.
GitHub has seen a rapid uptick in activity as developers employ AI-powered tools to generate code more quickly. That escalation in usage has strained the platform’s infrastructure. In April, GitHub Chief Operating Officer Kyle Daigle said that commits - a metric representing changes to code repositories - were on track to reach 14 billion in 2026, up from 1 billion in 2025.
A Microsoft spokesperson confirmed that GitHub uses multiple cloud providers to support its operations, but declined to address Amazon's specific role. The spokesperson noted that an increase in so-called "agentic development" had pushed GitHub's infrastructure toward its limits. As a consequence, the company is accelerating its Azure migration timetable while maintaining a multi-cloud strategy.
The platform’s surge in demand has coincided with reliability issues. The sources said GitHub experienced dozens of major outages this year amid rising usage. Those outages underscore the operational stress the platform has faced and help explain the decision to supplement capacity from AWS.
Market indicators reflected movement in the equities tied to the companies mentioned; MSFT +2.31% and AMZN +3.19% were shown alongside the reporting. Beyond the immediate operational effects, the developments highlight the interaction between rapid adoption of AI-enabled development tools and the cloud infrastructures that support modern software workflows.
Context and implications
The step to procure additional capacity from a third-party cloud provider illustrates a short-term capacity management response to sudden, tech-driven demand spikes. While Microsoft continues toward a single-cloud target for GitHub by 2027, the company is balancing that objective with operational resiliency through a multi-cloud posture.