Poonam Gupta wrote this on the Azure DevOps Blog on 3 June 2026. She is Partner Director of PM for 1ES and Azure DevOps. The example is Microsoft’s own Copilot, Agents, and Platforms group, which the post calls CAP.
CAP runs about 4,000 active repositories across 53 Azure DevOps organizations. Two engineering leads and a small bench did the move. The post says that was enough, and that a large central team was the thing people would have assumed.
The Azure DevOps → GitHub playbook splits repos from Boards, Pipelines, and Artifacts. CAP’s cut is the same split. Repos moved. Boards and Pipelines stayed.
Two percentages, one page
In the body, Gupta says CAP has moved more than 80% of its in-scope repositories and 45% of its developers. She turns that into over 1,600 repositories and 3,100 developers in six months. Large repos for Dynamics CRM and omnichannel CRM are in that set.
Further down, the lessons say CAP has migrated more than 70% of its active, in-scope repositories, and that many of the largest ones are still on Azure DevOps. I would quote the sentence you mean. “In-scope” and “active, in-scope” are not the same phrase, and 80 and 70 are both printed.
The complex repos, including mono repos, are the leftover. She expects Enterprise Live Migrator to speed that next phase. Expects, not finished.
Why the repos moved
The reason on the page is where AI features show up. Copilot Coding Agent, code review, Copilot chat, and other agent workflows are the list. CAP engineers already run some of those on the migrated repos, including scans that open GitHub Issues and hand a fix to the coding agent. Windows runners are part of that setup.
A second gain is search. One GitHub organization replaces work that was spread across 53 Azure DevOps organizations.
What they refused to move
Azure Boards and Azure Pipelines still do the planning and the CI. CAP connects pipelines with the Azure Pipelines GitHub app. Pull requests link to work items with AB# syntax.
Day to day, GitHub asks for a different kind of customization. The post says the shift is away from UI extensions and toward APIs, Actions, and integrations. People who already knew GitHub passed habits along. The hybrid setup is how they kept the old boards while that happened.
If you copy this, write down which repos are in scope before anyone publishes a percent. CAP’s own page uses two. Move an ordinary repo with GitHub Enterprise Importer before you bet a mono repo on Enterprise Live Migrator. And decide, on the same list, which Boards and Pipelines stay. The playbook treats those as a separate job from the git history.