ToolsSeptember 4, 2026via InfoQ AI/ML
Copilot Code Review Reaches Azure Repos, Billed Per Review with Reporting Two Days Behind
Why it matters
A major productivity tool expands beyond GitHub to Azure DevOps, with practical implications for cost control and adoption workflows. Practitioners using Azure need to understand the billing model, reporting lag, and concurrency limits before rolling out.
Key signals
- Copilot code review now available in Azure Repos for all Azure DevOps customers
- Billing: per-review, charged to linked Azure subscription
- Cost reporting appears 48 hours after use (delayed visibility)
- Budget alerts notify but do not enforce (cannot block reviews)
- Concurrency limit: 5 reviews per organization
- Launched in response to customer reluctance to migrate to GitHub
- GitHub Copilot code review now available in Azure Repos for all Azure DevOps customers
- Billing model: per-review charges through Azure subscription
- Cost visibility delayed 48 hours in Cost Management
- Budget alerts enabled but do not block reviews
- Concurrency capped at 5 reviews per organization
- Addresses customer retention concern: many orgs not ready to migrate from Azure Repos to GitHub
The hook
Microsoft brings Copilot code review to Azure Repos—but billing lags 48 hours and won't stop you from overspending.
Microsoft opened GitHub Copilot code review for Azure Repos to all Azure DevOps customers, after acknowledging that many are not ready to migrate to GitHub. Reviews bill per use through the linked Azure subscription and appear in Cost Management 48 hours later. Budgets notify but do not stop reviews…