Azure DevOps
Konductro integrates with Azure DevOps as a git provider — repositories live in your ADO organisation, and Konductro drives branches, pull requests, and ticket-spec files against them via the ADO REST API. Konductro owns the delivery workflow itself; ADO is not used as a work-item tracker.
What Syncs
| Data | Direction | Detail |
|---|---|---|
| Branches | Konductro to ADO | Feature branches created via the ADO Git API when a developer starts work |
| Ticket specs | Konductro to ADO | .tickets/TICKET-KEY.md files pushed to the branch via the ADO Git push API |
| Pull requests | Konductro to ADO | PRs created with title, description, and acceptance criteria checklist |
| Reviewers | Konductro to ADO | Auto-assigned reviewer added to the PR on ADO |
| PR status | ADO to Konductro | Pull-request created / updated / merged events update the linked ticket in real time via webhook (see below); also polled on view load as a fallback |
How It Works
Konductro uses the Azure DevOps REST API with a Personal Access Token (PAT) for authentication. The PAT requires the following scopes:
- Code — Read & Write (for branch creation, PR creation, and ticket-spec push)
- Graph — Read (for user identity resolution)
Work Items scope is not required — Konductro does not read or write ADO Boards.
Setup
Generate a PAT in Azure DevOps
In ADO, navigate to User Settings and then Personal Access Tokens. Create a token with the scopes listed above. Set an appropriate expiration.
Configure in Konductro
In Konductro, go to the project's Settings and then Integrations. Enter the ADO organisation name, project name, and PAT.
Link repositories
Add repositories from your ADO project. Konductro discovers available repos and lets you link them to the project.
Webhooks — PR status sync
By default, a ticket's PR status only updates when someone presses Sync PR Status on the dev board. Configure an ADO Web Hook and Konductro updates tickets automatically, within seconds of pull-request events.
Azure DevOps Web Hooks don't sign the payload — they authenticate with HTTP Basic auth — so the project's webhook secret is supplied as the Basic-auth password.
Generate the webhook secret in Konductro
In the project's Settings → Webhooks, click Generate webhook secret and copy the value. It is shown only once.
Create the service hooks in Azure DevOps
In ADO, go to Project settings → Service hooks → + Create subscription and choose Web Hooks. Create one subscription each for Pull request created, Pull request merged, and Pull request updated.
Point each subscription at Konductro
For every subscription, set:
- URL:
https://<tenant>.konductro.com/api/webhooks/ado/<project-id>— the exact URL is shown on the Webhooks card. - Basic authentication password: the webhook secret from step 1 (the username can be anything).
- Resource details to send: All.