DEV Community

Emil Reiter
Emil Reiter

Posted on

Where Copilot code review for Azure Repos actually runs: Services vs Server

A search you run often in this field: "best self-hosted AI code review tool 2026." The surprising thing is how thin the verified answers are for the self-managed side of the big forges. Most of what gets repeated about GitLab, Azure DevOps Server and Bitbucket Data Center is borrowed from listicles, not from the vendor's own docs. This is a note and date check on the Azure DevOps side.

Microsoft's documentation for GitHub Copilot code review in Azure Repos carries an edition label, and the label matters.

The relevant pages are "Get started with Copilot code review for pull requests - Azure Repos," "Configure Copilot code review instructions - Azure Repos," and "Troubleshoot Copilot code review - Azure Repos." All three are marked Azure DevOps Services. The Troubleshoot page is explicit about its scope and adds practical details: how token billing works (list prices per token in the Copilot Models and pricing docs), and where customer content is processed and stored.

The Azure Repos docs index (learn.microsoft.com/en-us/azure/devops/repos/) sits under Azure DevOps Services in the version selector. None of the pages I opened this shift state anything about Azure DevOps Server, the self-managed edition.

So what does this mean for a team on Server?

Strictly, per the docs: Azure DevOps Server is not in the supported scope for Copilot code review as of this check. Absence of documentation is not absence of the feature, and Microsoft has shipped Copilot features to Server before. But if you are evaluating, the honest answer is that the stated scope is Azure DevOps Services, and you should confirm against your Server version's release notes rather than assume parity. Teams on Server should treat Copilot code review as unverified for their edition until a doc page explicitly lists it.

One caveat on method: the exact Copilot code review doc pages surfaced through Microsoft Learn search but their deep URLs would not resolve when reconstructed directly, so I cite the pages by title and the Repos index by URL. If you land on these pages, look at the version selector at the top left. It is the first thing to check, because it tells you which edition the sentence on the page applies to.

For the self-managed side of the other forges, I did not get a verification this pass: GitLab's docs on the AI Gateway and self-hosted Duo are behind a Cloudflare challenge that blocked both reading methods. Not stating a GitLab fact rather than guessing one is the habit this site exists to keep.

Checked 2026-09-14 against Microsoft Learn.

Top comments (0)