GitHub Copilot code review is open to all Azure Repos customers

Microsoft published a post on the Azure DevOps blog on 26 August 2026 that opened GitHub Copilot code review to every Azure DevOps customer using Azure Repos, ending the sign-up requirement the feature had during technical preview. Coverage by InfoQ today added the pricing details Microsoft has since published in its documentation.

What Azure Repos customers can turn on

The feature posts review comments on pull requests automatically. It can be enabled at the organization, project, or repository level, and it can be attached to branch policies so that opening a pull request triggers a review. Reviewers can be scoped with custom instructions written at any of those levels, including for particular paths inside a repository. Draft pull requests are supported. The tagging Microsoft added means each project's cost can be attributed separately in Azure Cost Management.

How it is billed

Billing runs through the Azure subscription linked to the Azure DevOps organization. According to InfoQ's reading of Microsoft's documentation, each completed review consumes input, output, and cached tokens that are converted to GitHub AI credits, and larger pull requests or longer custom instructions raise the token count and therefore the cost. Charges show up in Azure Cost Management under a meter labelled "GitHub Copilot for AzDO", but the report reaches the meter 48 hours after the review completes.

The limits to know before switching it on

InfoQ reports the concurrency limits as five reviews per organization, two per user, and one per pull request, all running in parallel. Budgets in Azure can be attached and will send an email when a threshold is crossed. Microsoft's own language, quoted by InfoQ, is that budgets "only notify you. They don't stop reviews or change any resources." Azure Cost Anomaly detection can raise an alert on a spike, but does not stop the reviews either.

Why this needed a separate release

Microsoft acknowledged in the announcement that the code review feature had been GitHub-first, and that many Azure DevOps customers are not migrating. The post's own framing: "While many customers are actively planning and executing migrations to GitHub, many others are not yet ready to move and continue to rely on Azure Repos for day-to-day development." Copilot code review is one of a small set of features Microsoft has now made available on Azure DevOps rather than keeping behind that migration.

The technical question, whether an AI review adds value on top of a human review, is one each engineering team decides for itself. What changed with this rollout is that an Azure Repos team can enable it without leaving Azure DevOps, and can see the cost in the same place it sees the rest of its Azure bill. The two operational details that will decide how teams work with it are the 48-hour delay before the meter updates, and the fact that a budget will tell you about sudden high spending but not stop it. A team that intends to leave it running on every pull request should set a low limit first, watch two full days of actual spend, and only then set the real budget.

Source

Primary source: Microsoft's Azure DevOps blog announcement. Reported by: InfoQ, 4 September 2026.