Share with your CIO
Microsoft is spending $190 billion this year on AI infrastructure and still running out of compute, forcing a triage decision that defines the company’s near-term strategy: first-party products like Microsoft 365 Copilot and GitHub Copilot get the GPUs, Azure customers get what’s left. CFO Amy Hood confirmed this priority order publicly in January. Meanwhile GitHub, which had an early lead in AI coding tools, is hemorrhaging developer mindshare to Cursor and Claude Code, and has experienced dozens of major outages this year. Nadella’s Microsoft is also reportedly shopping for capacity from Amazon and Google to cover the gap.
What this means for your business
If your organization treats Azure as a strategic platform and Microsoft 365 as a given, this story is directly about you. The capacity triage Hood described isn’t a quarterly blip: it’s a structural sequencing choice where Microsoft’s own products are the first-class tenants and your cloud workloads are second-priority riders on whatever capacity remains. That’s a vendor relationship assumption worth stress-testing at your next enterprise agreement renewal, not as a reason to flee, but as leverage you didn’t know you had.
The GitHub situation deserves separate attention from the Azure conversation. GitHub’s dominant position with developers rested on network effects, the accumulated pull-requests, integrations, and identity that made it the default home for software teams. AI-native tools like Cursor have broken that moat faster than most CIOs anticipated, not by being marginally better but by redefining what the developer environment is. The recurring failure mode here is assuming that incumbency in the workflow layer survives a shift in where the actual work happens. Microsoft owned where developers built software; that ownership is now contested.
Microsoft’s internal move toward something executives are privately calling a return to “stack ranking,” sharper performance differentiation and fewer senior engineering roles, matters because it signals where Nadella thinks the execution gaps are. The last time Microsoft ran hard performance pressure was the Ballmer era, which preceded a decade of product stagnation. That’s not a prediction of the same outcome, but it is a leading indicator of internal friction arriving exactly when Microsoft needs its engineering organization to ship faster than it ever has. Watch whether GitHub Copilot’s product velocity catches Cursor’s in the next two quarters. If it doesn’t, the capacity crisis and the talent pressure together explain why.
Based on reporting from Inside Microsoft’s AI Strategy As Pressure Mounts on Satya Nadella, originally published 2026-07-26 04:07:00.
