{
  "id": 7431563,
  "title": "Where Copilot code review for Azure Repos actually runs: Services vs Server",
  "url": "https://urgent.news/2026/09/15/where-copilot-code-review-for-azure-repos-actually-runs-services-vs",
  "topic": "ai",
  "section": "AI",
  "published": "2026-09-15T00:15:10.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/emilreiter/where-copilot-code-review-for-azure-repos-actually-runs-services-vs-server-3ij5"
  },
  "original_language": "en",
  "account": "Microsoft's documentation for GitHub Copilot code review in Azure Repos clearly states that the feature is only supported in Azure DevOps Services, not Azure DevOps Server. The relevant pages, Get started with Copilot code review for pull requests, Configure Copilot code review instructions, and Troubleshoot Copilot code review, are all marked Azure DevOps Services. The Troubleshoot page even goes into detail on token billing and where customer content is processed and stored. There is no mention of Azure DevOps Server in the Azure Repos docs index, which sits under Azure DevOps Services in the version selector. This means that for teams using Azure DevOps Server, Copilot code review is not officially supported or verified. While Microsoft has likely tested Copilot features on Server in the past, the absence of documentation explicitly stating support means teams should treat it as unverified until a page is added to the docs. The version selector on the Copilot code review pages is the first thing teams should check to ensure they are looking at information relevant to their edition. GitLab's self-hosted AI Gateway and Duo are also not covered in this check due to blocked access to their docs. The verification was completed on September 14, 2026.",
  "summary": "A search you run often in this field: \"best self-hosted AI code review tool 2026.\" The surprising thing is how thin the verified answers are for the self-managed side of the big forges. Most of what gets repeated about GitLab, Azure DevOps Server and Bitbucket Data Center is borrowed from listicles, not from the vendor's own docs. This is a note and date check on the Azure DevOps side.…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}