Ever since Microsoft acquired GitHub for $7.5 billion, they have been sending mixed stories to customers on the roadmap. One thing is clear: Microsoft is making GitHub the strategic destination for many Azure Repos customers. That message has been more consistent. The migration path, less so. For anything beyond a handful of repositories, the traditional approach meant locking the source, freezing development, and absorbing a downtime window that could stretch into days. For a team running a critical workload, that is not a maintenance window. That is a business decision nobody wants to sign off on.

Enterprise Live Migrations (ELM), now in limited public preview, is Microsoft’s answer to that problem.

What the live part actually means

The headline is that ELM starts the migration without locking your Azure Repos. Development keeps going while changes synchronise to GitHub in the background. When you are ready, you schedule a cutover, run a final sync, and GitHub becomes the system of record.

The downtime window for that cutover is typically under 30 minutes, rather than the days a freeze and copy approach can demand. For most of the process, Azure DevOps stays fully writable, so your engineers and developers are not sitting idle waiting for a migration to finish.

The workflow itself is deliberately staged. You start and validate to confirm the repository is migration-ready. You run continuous sync to keep GitHub current while work continues. Then you cut over on your own schedule. Teams move at their own pace instead of coordinating one high-risk event across the whole estate at once.

Read the small print

This is still a public preview, and the constraints do matter. ELM currently targets GitHub Enterprise Cloud with data residency. If your destination is GitHub Enterprise Server, or standard GitHub Enterprise Cloud without data residency, this is not your tool today.

The experience is script based right now. A UI is coming, but the streamlined end-to-end workflow Microsoft is describing is not what you get on day one. Expect to work from scripts, and expect the feature set to keep shifting. Microsoft has said it will stay in public preview for the next couple of months while it refines the experience and folds in feedback.

For European teams, the data residency requirement is less of a limitation and more of a reason to look. GitHub Enterprise Cloud with data residency lets you pin your data to a specific region, which is exactly the conversation many European companies are already having about where their code and metadata physically live.

Reading the room

Worth stepping back. This is not the only piece Microsoft has published lately about getting off Azure Repos. There has been a steady run of them, including a post on how Microsoft is migrating its own repositories to GitHub. When a vendor invests this much in making the exit smooth, it is telling you something about where it expects you to end up.

That sits awkwardly next to the reassurances Azure DevOps customers have had recently. Azure DevOps Server is back on the Modern Lifecycle, which reads as a real commitment to the on-premises product. Both things can be true at once. Microsoft can keep Azure DevOps Server supported for the teams that need it while quietly making GitHub the obvious destination for everyone else. The customers asking, in the comments on Microsoft’s own post, when Azure DevOps will be retired are not being paranoid. They are reading the room.

Should you move to GitHub now?

If you are already committed to GitHub Enterprise Cloud and the data residency tier fits, ELM is genuinely useful and worth joining the preview to test against a non-critical repository. The continuous sync model removes the single biggest objection to migrating at scale, which was always the downtime.

If you are still weighing whether GitHub is the right destination at all, an easier migration does not change that decision. Cost, your developers’ appetite for the GitHub and Copilot experience, and your existing Azure DevOps pipelines all belong in that conversation first. A smoother move is not a reason to make a move you were not otherwise going to make.

And if you are on Azure DevOps Server on-premises, note that ELM is aimed at Azure Repos in the cloud. Microsoft has not confirmed an on-premises source path.

If you are weighing a move from Azure Repos to GitHub, or trying to work out where Azure DevOps fits in your roadmap? Get in touch and we will walk through it.