The facts are confirmed by the publication, but not by the primary source.

InfoQ reported that GitHub Copilot code review is available in Azure Repos to all Azure DevOps customers. The article says the feature leaves review comments on a pull request and charges for each review.

Copilot leaves the Comment review type and does not approve changes. Its review therefore does not meet the required reviewer policy and does not block merging.

The repository for the feature must be no larger than 10 GB. The pull request must contain no more than 100 changed files and have no merge conflicts.

Review charges appear in Azure Cost Management 48 hours after a review is completed. Budgets only notify users about spending and do not stop reviews.

Claim check:

  • InfoQ published a news article about the availability of GitHub Copilot code review for Azure Repos and its terms of use. (confirmed by the publication itself: evidence; «Microsoft has opened GitHub Copilot code review for Azure Repos to all Azure DevOps customers, removing the sign-up that gated it since June.»)
  • Microsoft made GitHub Copilot code review for Azure Repos available to all Azure DevOps customers, ending the previous sign-up for preview access. (confirmed only by the carrying publication: evidence; «Microsoft has opened GitHub Copilot code review for Azure Repos to all Azure DevOps customers, removing the sign-up that gated it since June.»)
  • The feature leaves review comments on a pull request and charges for each review through the linked Azure subscription. (confirmed only by the carrying publication: evidence; «The feature posts review comments on pull requests, bills per review through the linked Azure subscription, and reports spending two days after it happens.»)
  • Review charges appear in Azure Cost Management in the GitHub Copilot for AzDO product 48 hours after a review is completed. (confirmed only by the carrying publication: evidence; «Charges appear in Azure Cost Management under the product GitHub Copilot for AzDO, 48 hours after a review completes.»)
  • Budgets for this feature only notify users about spending and do not stop reviews or other resources. (confirmed only by the carrying publication: evidence; «Budgets only notify you. They don’t stop reviews or change any resources.»)
  • Concurrency limits are five reviews per organization, two per user, and one per pull request. (confirmed only by the carrying publication: evidence; «five concurrent reviews per organization, two per user, one per pull request.»)
  • The August update added settings at the organization, project, and repository levels, support for Managed DevOps Pools, custom instructions, and automatic reviews through branch policies. (confirmed only by the carrying publication: evidence; «The August release adds onboarding controls at organization, project, and repository level, support for Managed DevOps Pools, custom instructions, and automatic reviews driven by branch policies.»)
  • Managed DevOps Pools require a current Ubuntu Server image. Windows images and self-hosted agents are not supported. (confirmed only by the carrying publication: evidence; «Managed DevOps Pools are supported and must run the latest Ubuntu Server image; Windows images are not supported, and Microsoft advises against mixing Ubuntu and Windows agents in one pool. Self-hosted agents are not supported.»)
  • Copilot always leaves the Comment review type, does not approve changes, and does not request them. Its review therefore does not meet the required reviewer policy and does not block merging. (confirmed only by the carrying publication: evidence; «Copilot always leaves a Comment review, never approves or requests changes, so its feedback does not satisfy required-reviewer policies and does not block a merge.»)
  • For the feature to work, the repository must be no larger than 10 GB, and the pull request must contain no more than 100 changed files and have no merge conflicts. TFVC is not supported. (confirmed only by the carrying publication: evidence; «Repositories must be 10 GB or less, pull requests must contain 100 changed files or fewer with no merge conflicts, and TFVC is not supported.»)
  • The feature is rolling out gradually by region and, according to Microsoft, may take two to three weeks or longer. (confirmed only by the carrying publication: evidence; «Rollout is gradual by region, and Microsoft expects two to three weeks or longer to reach all organizations.»)

Publications:

score 64.0 · kind announcement · revision 1 · stories st-1w9tgt3