Microsoft Turns to AWS to Manage GitHub's AI-Driven Capacity Strain

Microsoft is adding Amazon Web Services capacity to maintain GitHub operations following an AI-driven surge in coding activity that triggered reliability issues. [1][2] Business Insider reported that Microsoft had initially planned to migrate GitHub completely to Azure by 2027. [1] However, the platform has faced outages and higher usage rates, prompting the infrastructure adjustment. [1]

A Microsoft spokesperson confirmed the company is accelerating its Azure transition while also exploring a multi-cloud strategy to ensure elasticity and scale. [1] The spokesperson noted that an "incredible spike in agentic development" since late 2025 has tested the limits of GitHub's infrastructure. [1] Amazon stated that it does not comment on individual clients. [1]

The infrastructure pressure is visible in GitHub's own numbers. [1] According to a report by Business Insider, GitHub Chief Operating Officer Kyle Daigle stated in April that commits are on pace to hit 14 billion in 2026. [1] This is an increase from the 1 billion commits recorded in 2025. [1]

The decision to run a strategic developer platform on a rival's infrastructure highlights how the computational demands of AI coding tools are overriding standard corporate cloud synergies. Microsoft's willingness to use AWS rather than relying exclusively on Azure indicates the severity of the load curve generated by the documented spike in agentic development. The projected jump from 1 billion to 14 billion commits in a single year demonstrates that infrastructure scaling for AI tooling is outpacing traditional software planning. What the sources don't address: Whether Microsoft intends to continue utilizing AWS for GitHub after the planned Azure migration is supposed to conclude in 2027.