Enterprise Live Migrations: Smooth move, shaky destination
Microsoft’s Enterprise Live Migrations GitHub migration tool is a service that keeps Azure Repos and GitHub repositories in sync so enterprises can move their code with minimal downtime, promising a short final cutover window instead of multi-day development freezes that stall production work and delay deliveries. ELM syncs full Git history, branches, tags, pull request metadata, and maps Azure DevOps branch policies into GitHub rulesets, aiming to make Azure Repos migration a near “no extended freeze periods, no multi-day outages” event. For enterprises, this seems to solve the most obvious downtime migration risk: developers can keep working until the last 30-minute switchover. Yet this pitch focuses on the journey, not the destination. It says little about what happens when teams land on a platform that has spent months battling availability problems and infrastructure strain.
GitHub reliability issues in the age of AI-driven traffic
While Microsoft promises a smooth move, GitHub’s own reliability record is far less reassuring for any enterprise code repository strategy. A surge in AI-assisted coding and agentic workflows has pushed GitHub from handling roughly 1 billion commits in an entire year to about 1.4 billion commits every month, with AI agents creating more than 17 million pull requests in the same period. According to GitHub’s May 2026 Availability Report, the service logged nine incidents that degraded performance, only slightly better than April’s 10. An unofficial Missing GitHub Status Page project paints a starker picture, estimating uptime at 78.33 percent in April and 93.86 percent in May. GitHub is shifting more workloads to Azure and restructuring its architecture, but the ongoing incidents show that migrating infrastructure and adding capacity have not yet translated into predictable day-to-day reliability.
Azure Repos migration meets unresolved platform risk
Microsoft’s message to enterprises is clear: GitHub is the strategic home for AI-native development, and Azure Repos is no longer where the future lies. Internal proof points, like the Copilot, Agents and Platforms organization moving over 1,600 repositories and 3,100 developers in six months, are meant to show that large-scale Azure Repos migration is feasible using the GitHub migration tool. But customers see a different tension. Rumors of Azure Repos deprecation persist, while GitHub reliability issues remain in recent memory. Commenters responding to Microsoft’s own migration blog questioned why AI capabilities could not be brought to Azure Repos instead, and pointed out the higher per-user cost of GitHub Enterprise compared with Azure DevOps Basic. For many teams, the question is not whether migration can avoid downtime, but whether consolidating on GitHub increases long-term operational risk.
Security incidents add a supply chain twist to migration decisions
Reliability is not the only concern shaping enterprise due diligence. A recent supply chain attack disabled 73 Microsoft-owned GitHub repositories, including Actions used to deploy Azure Functions, breaking CI/CD pipelines worldwide. That incident shows how a compromise on a shared platform can ripple through thousands of automated workflows at once, amplifying the stakes of any enterprise code repository choice. For organizations weighing Azure Repos migration, this adds another layer of risk on top of availability problems: code hosting, automation definitions, and build pipelines become concentrated on a single platform that has already been a high-profile target. The GitHub migration tool helps copy history and metadata, but it does not explain how Microsoft will reduce exposure to similar attacks. Enterprises must factor both operational outages and supply chain threats into their GitHub reliability calculus.
The reliability gap Microsoft won’t address directly
Enterprise Live Migrations is engineered to make the act of moving to GitHub predictable, yet it does not answer the question that matters most: what level of reliability will enterprises get after migration. Microsoft highlights AI gains and reduced downtime during the move, but is largely silent about how GitHub will avoid repeating months of incidents once more Azure Repos workloads arrive. GitHub leaders say they are “making structural changes that permanently remove failure modes” and aim to reach far higher capacity, including a 30x expansion target, but the incident counts and unofficial uptime figures show that the work is unfinished. For risk-aware organizations, the gap between migration promises and current platform stability is the core issue. Until GitHub can display consistent, boring reliability, the smart question is not how fast to migrate, but whether to rely on it as the single source of truth.
