Copilot Code Review Reaches Azure Repos, Billed Per Review with Reporting Two Days Behind

Microsoft has expanded the availability of GitHub Copilot's code review feature to all Azure DevOps customers, eliminating the sign-up requirement that existed since June. The feature now posts review comments on pull requests within Azure Repos and bills for each review through the linked Azure subscription, with the corresponding expenses appearing two days after the review is completed.

Microsoft's decision to bring GitHub's AI and agentic development capabilities to organizations that haven't yet migrated their repositories from Azure Repos to GitHub is aimed at catering to those who find the migration process too complex. This approach is designed to support teams seeking AI-assisted tooling within Azure DevOps without needing to transfer their code to GitHub.

The release also introduces new onboarding controls at various organizational levels, support for Managed DevOps Pools, custom instructions, and automatic reviews governed by branch policies. The pricing model for the reviews is based on input, output, and cached tokens, with each completed review being converted into GitHub AI credits at a rate of one credit per cent. The billing details are available in Azure Cost Management, 48 hours post-review completion.

While the feature aims to provide advisory code reviews without altering the repository's state, it currently lacks the ability to stop reviews or alter resources, only notifying teams through email within an hour of the next cost evaluation. This two-day reporting delay could result in a two-day window for cost monitoring and budget adjustments.

Concurrency limits are set at five concurrent reviews per organization, two per user, and one per pull request. An organization with numerous teams reviewing every new pull request may experience queueing. The review process, designed to be advisory, leaves a comment on the pull request but does not approve or request changes. The feature's availability is regionally phased, with Microsoft estimating a two to three week rollout period.