Azure DevOps

Uses: Catalog Kong Gateway

Prerequisites

You need to configure the following:

An Azure DevOps account.
An Azure DevOps personal access token (PAT) with Code:Read permission.

Authenticate the Azure DevOps integration

In the Konnect sidebar, click Catalog.
In the Catalog sidebar, click Integrations.
Click Azure DevOps.
Click Add Azure DevOps instance.
In the Azure DevOps organization name field, enter your organization name exactly as it appears in Azure DevOps.
In the Azure DevOps personal access token (PAT) field, enter your Azure DevOps token.
In the Display name field, enter azure-devops-repository-service.
In the Instance name field, enter azure-devops-repository-service.
(Optional) In the Description field, enter a description for this instance.
Click Save.

Before you can discover Azure DevOps repositories in Catalog Classic, export your Azure organization name exactly as it appears in Azure DevOps:

export AZURE_DEVOPS_ORG_NAME="YOUR-ORG-NAME"

Copied!

Now, configure the integration:

AZUREDEVOPS_INTEGRATION_ID=$(curl -X POST "https://us.api.konghq.com/v1/integration-instances" \
     --no-progress-meter --fail-with-body  \
     -H "Authorization: Bearer $KONNECT_TOKEN" \
     --json '{
       "integration_name": "azure-devops",
       "name": "azure-devops",
       "display_name": "Azure DevOps",
       "config": {
         "organization": "'$AZURE_DEVOPS_ORG_NAME'"
       }
     }' | jq -r ".id"
)

Copied!

Next, authorize the integration with your Azure DevOps PAT:

curl -X POST "https://us.api.konghq.com/v1/integration-instances/$AZUREDEVOPS_INTEGRATION_ID/auth-credential" \
     --no-progress-meter --fail-with-body  \
     -H "Authorization: Bearer $KONNECT_TOKEN" \
     --json '{
       "type": "multi_key_auth",
       "config": {
         "headers": [
           {
             "name": "authorization",
             "key": "'$AZUREDEVOPS_PAT'"
           }
         ]
       }
     }'

Copied!

For additional Azure DevOps resources, use the following table:

Entity	Description
OAuth 2.0 Scopes	Define and control the specific resources an OAuth application can access in Azure DevOps by requesting granular scopes.
Personal Access Tokens (PATs)	Authenticate with Azure DevOps by generating a time-limited token that grants scoped access, follow least-privilege practices by selecting only required permissions, and store the token securely to prevent misuse.

Discovery information

Automatic resource discovery is supported by this integration
Resource types: Repositories

Azure DevOps

Prerequisites

Authenticate the Azure DevOps integration

Discovery information

Help us make these docs great!

Still need help?