Skip to main content

Azure DevOps

Plugin details
Created bykeyloop
TypeOpen-source plugin


Application configuration YAML

This plugin requires a backend proxy configuration to make calls to Azure Pipelines with authentication. The following configuration is set by default and you need to add the host, token and organization

organization: your_organization_name


Since the AZURE_PERSONAL_ACCESS_TOKEN variable is used in the application configuration, you must generate a Personal Access Token with read access to both Code and Build and set it as the value of AZURE_PERSONAL_ACCESS_TOKEN.

Delegate proxy

If the host is on a private network, ensure that you include the host URL in this section. If the host is accessible publicly, skip this section.

After adding the host, you can select one or more delegates that have access to the host. If you leave the delegate selectors field empty, it is assumed that all delegates in the account have access to the host/cluster.


When adding the host, include only the host name. Remove the protocol (HTTP/HTTPS) and any port number associated with it.


No Action Required

This plugin exports an overview page card, UI tab that you can use as a new CI/CD tab for a service or for any other layout page and a Git Tags page. Go to Admin > Layout, select Service in the dropdown menu, and you can view this YAML code in the CI/CD section:

- name: EntityAzurePipelinesContent
path: /azure-pipelines
title: CI/CD
- component: EntityAzurePipelinesContent
- name: EntityAzurePullRequestsContent
path: /pull-requests
title: Pull Requests
- component: EntitySwitch
- if: isAzureDevOpsAvailable
component: EntityAzurePullRequestsContent
- name: EntityAzureGitTagsContent
path: /git-tags
title: Git Tags
- component: EntitySwitch
- if: isAzureDevOpsAvailable
component: EntityAzureGitTagsContent

The isAzureDevOpsAvailable condition is met when the annotation is present in the software components's catalog-info.yaml definition file.


To configure the plugin for a service in the software catalog, set the following annotation in its catalog-info.yaml definition file:

annotations: <project-name>/<repo-name>

Let's break this down a little: <project-name> will be the name of your Team Project and <repo-name> will be the name of your repository which needs to be part of the Team Project you entered for <project-name>.

Mono repos

If you have multiple entities within a single repo, you will need to specify which pipelines belong to each entity. <my-project>/<my-repo> <build-definition-name>

Pipeline in different project to repo

If your pipeline is in a different project to the source code, you will need to specify this in the project annotation. <project-with-source-code>/<my-repo> <build-definition-name> <project-with-build-code>

Azure Pipelines Only

If you are only using Azure Pipelines along with a different SCM tool then you can use the following two annotations to see Builds: <project-name> <build-definition-name>

In this case <project-name> will be the name of your Team Project and <build-definition-name> will be the name of the Build Definition you would like to see Builds for, and it's possible to add more Builds separated by a comma. If the Build Definition name has spaces in it make sure to put quotes around it.


The plugin is owned by keyloop and managed in the Backstage repository as an open-source project. Create a GitHub issue to report bugs or suggest new features for the plugin.