Skip to main content

Azure DevOps



Azure DevOps is a Microsoft-owned VCS. You can use Azure DevOps to drive insights into values such as:

  • Repository details in the Catalog
  • Scorecard rules


In order to connect Cortex to your Azure DevOps instance, you’ll need to add a Azure DevOps personal access token with at least read scopes enabled.


If you do not see the settings page you're looking for, you likely don't have the proper permissions and need to contact your admin.


If you're using a self-hosted instance of Azure DevOps, you'll need to verify that your Cortex instance is able to reach the Azure DevOps instance.

We route our requests through a static IP address. Reach out to support at to receive details about our static IP. If you're unable to directly allowlist our static IP, you can route requests through a secondary proxy in your network that has this IP allowlisted and have that proxy route traffic to your Azure DevOps instance.


Entity descriptor


By specifying the x-cortex-git field in your Cortex entity descriptor, you'll be able to see Git information in the entity page, including the top language, recent commits, and top contributors.

project: <project-name>
repository: <repository-name>
basepath: myService # optional
projectThe name of the project as listed under the "Projects" tab when you are logged into Azure DevOps (on the{your-organization}/ screen)true
repositoryThe repo name you see when you navigate to the "Repos" section of Azure DevOpstrue
basepathIf the entity is in a monorepo (e.g. in a subdirectory), use this field to define the subdirfalse