Skip to main content

Azure DevOps Locations

The Azure DevOps integration supports loading catalog entities from Azure DevOps. Entities can be added to static catalog configuration, or registered with the catalog-import plugin.

Using a service principal:

integrations:
  azure:
    - host: dev.azure.com
      credential:
        clientId: ${CLIENT_ID}
        clientSecret: ${CLIENT_SECRET}
        tenantId: ${TENANT_ID}

Using a managed identity:

integrations:
  azure:
    - host: dev.azure.com
      credential:
        clientId: ${CLIENT_ID}

Using a personal access token (PAT):

integrations:
  azure:
    - host: dev.azure.com
      token: ${AZURE_TOKEN}

Note: An Azure DevOps provider is added automatically at startup for convenience, so you only need to list it if you want to supply a token, a service principal, or a managed identity

The configuration is a structure with these elements:

  • host: The DevOps host; only dev.azure.com is supported.
  • token (optional): A personal access token as expected by Azure DevOps.
  • credential: (optional): A service principal or managed identity

Note:

  • token and credential are mutually exclusive.
  • You cannot use a service principal or managed identity for Azure DevOps Server (on-premises) organizations
  • You can only use a service principal or managed identity for Azure AD backed Azure DevOps organizations
  • The token should just be provided as the raw token generated by Azure DevOps using the format raw_token with no base64 encoding. Formatting and base64'ing is handled by dependent libraries handling the Azure DevOps API