GitHub Copilot Code Review for Azure DevOps Now Generally Available
GitHub made Copilot code review for Azure Repos generally available after a public preview. Teams that host code in Azure DevOps can get Copilot reviews on pull requests, with comments and suggested changes on the lines that need attention. Setup uses branch policies, Lite or Balanced effort levels, and usage is billed in GitHub AI credits to the linked Azure subscription.
Key Takeaways
- Copilot code review for Azure Repos is now generally available, moving out of public preview for teams hosted in Azure DevOps.
- Reviews arrive as comments and suggested changes on the lines that need attention in each pull request.
- A branch policy can request a Copilot review automatically on pull requests that target a branch, or reviewers can request one manually.
- Default effort can be set to Lite or Balanced per project or repository, with per-review overrides.
- Custom instructions and agent skills let teams tailor feedback, and suggestions can be applied and committed while resolving comments in one step.
- Usage is billed in GitHub AI credits to the linked Azure subscription, so it shows up in Azure Cost Management with budget alerts.
Copilot Reviews Come to Azure Repos
GitHub announced that Copilot code review for Azure Repos, previously in public preview, is now generally available. Teams that keep their code in Azure DevOps can now request Copilot reviews on their pull requests and receive comments and suggested changes on the lines that need attention, without moving repositories to GitHub.
The announcement was part of a wider Copilot code review release on November 17, 2026 that also covered adaptive effort, cross-repository context, secret detection and repository insights. The Azure DevOps availability change is a separate capability aimed at a different audience: teams whose pull requests live in Azure Repos.
Setup and Review Controls
Administrators turn on Copilot code review at the organization, project and repository level. A branch policy can request a Copilot review automatically on any pull request that targets a given branch, and reviewers can also request one manually from the Reviewers list.
Review effort can be set per project or repository. The default can be Lite or Balanced, and a different effort level can be chosen for a single review when a particular pull request needs more or less scrutiny.
Customization and Follow-Up
Teams can shape Copilot's feedback with custom instructions and agent skills so that reviews reflect their own standards. Once Copilot leaves suggestions, authors can apply and commit them and resolve the related comments in the same step, which shortens the loop between review and merge.
Visibility and Billing
Audit log events record when Copilot code review is turned on or off and when its settings change, giving administrators a trail of configuration changes. Usage is billed in GitHub AI credits to the Azure subscription linked to the Azure DevOps organization, so teams can track costs and set budget alerts in Azure Cost Management.
To get started, GitHub points teams to its Azure DevOps documentation for Copilot code review of pull requests.