Microsoft is preparing to migrate GitHub’s core infrastructure to Azure over the next two years, according to internal communications first reported by The Verge. While the move may seem like a natural consolidation under Microsoft’s cloud ecosystem, the urgency behind it reveals deeper challenges, and a strategic pivot that could reshape how GitHub scales in the age of AI.
The migration is not just a technical upgrade. GitHub’s Chief Technology Officer, Vladimir Fedorov, described the shift as “existential” in an internal memo, citing severe capacity constraints in GitHub’s current data centers, particularly in the North Virginia region. With limited ability to expand its server footprint, GitHub is reportedly struggling to meet the demands of its rapidly growing user base and the compute-intensive workflows driven by AI tools like Copilot.
Fedorov’s note emphasized that GitHub’s infrastructure must evolve to support real-time inference, telemetry processing, and high-concurrency workloads, all of which are becoming standard in modern developer environments. “CoreAI and Azure are mobilizing to get us the capacity and anything else we need to unlock us,” he wrote, signaling full support from Microsoft’s senior leadership.
The migration coincides with a broader organizational shift. Following the departure of GitHub CEO Thomas Dohmke, Microsoft opted not to appoint a direct successor. Instead, GitHub is being folded into Microsoft’s CoreAI division, aligning its roadmap more closely with the company’s AI strategy. This includes increased use of Microsoft Teams for internal communication, replacing Slack, and deeper integration with Azure’s monitoring, identity, and deployment pipelines.
GitHub COO Kyle Daigle confirmed the migration to The Verge, stating, “We need to scale faster to meet the explosive growth in developer activity and AI-powered workflows, and our current infrastructure is hitting its limits.” The transition will prioritize infrastructure work over new feature development, with the bulk of engineering expected to be completed within a year and full migration targeted within 24 months.
For developers, the move raises questions about GitHub’s independence and reliability. While Azure offers global scalability and elastic compute resources, migrating GitHub’s multi-tenant architecture and latency-sensitive Git operations is a complex undertaking. Past attempts to shift portions of GitHub’s services to Azure have faced delays and technical hurdles, and this full-scale migration will require careful orchestration to avoid service disruptions.
At the same time, the shift could unlock new capabilities. With direct access to Azure’s GPU pools and AI infrastructure, GitHub may be better positioned to support Copilot’s evolution, host larger repositories, and deliver faster CI/CD pipelines. If successful, the migration could redefine GitHub as not just a code hosting platform, but a cloud-native hub for AI-enhanced development.
This move reflects Microsoft’s broader strategy to unify its developer tools under a cloud-first model. By bringing GitHub into Azure, Microsoft is consolidating its infrastructure, streamlining operations, and reinforcing its commitment to AI-driven workflows. It also signals a shift away from siloed services toward a more integrated ecosystem, one that spans GitHub, Azure DevOps, Copilot, and beyond.
For GitHub users, the next two years will be a test of trust and transparency. Microsoft must balance its cloud ambitions with GitHub’s legacy as an open, developer-first platform. The stakes are high, but so is the potential if AI proves to be more than money suck.
