Microsoft adds – Microsoft is adding extra computing capacity for GitHub via Amazon Web Services after AI-driven demand and a run of 2026 outages strained the platform. The shift comes as Microsoft accelerates its move to Azure and tries to manage surging code activity—commits
For GitHub engineers, the problem isn’t just speed—it’s whether the platform holds when demand spikes.
Microsoft is now turning to its biggest cloud rival. Amazon. to help address capacity issues on GitHub following a series of AI-driven outages in 2026. according to two people familiar with the plans. GitHub—acquired by Microsoft in 2018—has long relied mostly on its own data centers as an independent company. but Microsoft had planned to move the coding platform entirely to its Azure cloud service by 2027.
That timeline is colliding with a new reality. A boom in AI demand is pushing developers to write more software through AI coding tools. flooding GitHub with more activity and straining its compute resources. Microsoft’s chief operating officer Kyle Daigle wrote on X in April that GitHub commits—records of code changes that serve as a proxy for development activity—were on pace to reach 14 billion in 2026. up from 1 billion in 2025.
To handle this surge, Microsoft is adding extra computing capacity through Amazon Web Services, the people familiar said.
The decision lands awkwardly in the middle of a cloud market fight. Microsoft and Amazon have been battling for market share. and sending an arch rival extra business instead of relying fully on Azure for GitHub is likely not the move Microsoft would choose in calmer times. But the pressure from AI demand is so intense that other major tech companies have been forced into similar compute deals.
Earlier this month, SpaceX and Google disclosed a deal in which Google will pay SpaceX $920 million a month for AI compute capacity from October 2026 to June 2029. That emerged just two months after Google’s own cloud business agreed to sell AI compute capacity to Anthropic.
Microsoft insists it is not abandoning Azure. A Microsoft spokesperson confirmed GitHub is tapping multiple cloud providers but declined to comment on any Amazon involvement. “The incredible spike in agentic development that began late last year has tested our infrastructure’s limits,” the spokesperson said. To meet this demand. Microsoft 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.”.
Amazon, for its part, said it doesn’t comment on individual clients. It added: “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.”
This is, at its core, a battle over uptime. Keeping services running matters more than who supplies the underlying capacity.
GitHub’s latest strain has been visible to users. The platform has suffered dozens of major outages in 2026. Mitchell Hashimoto, a cofounder of startup HashiCorp, wrote in April that GitHub was “no longer a place for serious work if it just blocks you out for hours per day, every day.”
Competition is also tightening in the AI coding era. GitHub had an early lead among engineers, but lately it has faced more competition from AI tools such as Cursor and Anthropic’s Claude Code.
Microsoft has been preparing to spend heavily on capacity. projecting capital expenditures for the 2026 calendar year to reach $190 billion. largely to expand data center capacity. But many data center projects are delayed. At the same time, Microsoft has other important AI projects and businesses that also need compute capacity.
Inside Microsoft, the stakes around GitHub’s AI-driven future have been clear. An internal meeting late last year featured a Microsoft executive talking about needing to overhaul GitHub to compete with Cursor and Claude Code, according to audio reviewed by Business Insider.
When GitHub goes down, the cost isn’t theoretical. For developers who build on it day after day. capacity isn’t an abstract cloud metric—it’s whether they can keep shipping. And right now. Microsoft appears willing to trade ideal procurement strategy for the practical goal of keeping GitHub’s AI-powered surge from breaking the system.
Microsoft GitHub Amazon Web Services AWS Azure AI coding outages data center capacity commits Kyle Daigle multi-cloud
So Microsoft is paying Amazon now? That’s wild.
I knew the AI stuff would overload everything. GitHub outages were like constant for a minute. If Microsoft can’t handle it on Azure then… just admit it’s not ready.
Wait, they said GitHub was moving to Azure by 2027 but now they’re using AWS because of outages in 2026, right? Sounds like they planned it wrong or the AI commits number is made up. 14 billion commits?? That seems like spam bot math.
This is why I don’t trust cloud anything. One company says “we’re moving” then suddenly they’re “partnering” with Amazon because AI demand is too much. Next thing you know they’ll blame the developers like it’s our fault their servers can’t keep up with automation. Also, doesn’t Microsoft own GitHub so why are they outsourcing computing to their rival? Makes no sense to me but whatever.