Azure DevOps integration

Overview

Azure DevOps is Microsoft's DevOps platform – Git repos (Azure Repos), CI/CD (Pipelines), boards (Work Items), test plans, artifacts. The Automize Azure DevOps connector covers projects, repos, pipelines, builds, work items, and pull requests.

• Regions: Each Azure DevOps organization has a URL (dev.azure.com/yourorg or yourorg.visualstudio.com legacy).
• Plans: Free for 5 users + unlimited private repos. Basic (paid) for >5 users. Test Plans + Artifacts are separate paid features.

Setting up the connection

Auth type: HTTP Basic.

1. Sign in to dev.azure.com → click your avatar → Personal Access Tokens → New Token.
2. Set scopes: Code (read+write), Build (read+execute), Work Items (read+write), Project & Team (read).
3. Set expiration (max 1 year).
4. Copy the token.
5. In Automize, open Settings → Connectors → Azure DevOps → Add connection. Enter org name, username (any non-empty), password (the PAT).

Find your credentials at https://dev.azure.com/yourorg/_usersSettings/tokens.

Rate limits

Azure DevOps enforces per-user + per-org limits – generally generous for normal automation. Heavy reads should use ?$top + continuation tokens.

Data model

Hierarchy:

    Organization ─┬─ Projects ─┬─ Repositories (Git) ─── Branches ─── Commits
                  │            ├─ Pipelines ─── Builds ─── Jobs
                  │            ├─ Pull Requests ─── Reviews
                  │            └─ Work Items (Bug, Task, User Story, Feature, Epic)
                  └─ Service Connections (artifact feeds, etc.)

Available operations

9 operations available. Click any row to jump to its detail.

Operations

Create Work Item

Create a work item (bug, task, etc.)

Tips

• project + type (Bug, Task, User Story, etc.).
• Body: JSON-Patch document – [{op:'add', path:'/fields/System.Title', value:'Title'}, ...].

Get Work Item

Get work item details

Tips

• Returns fields + relations + history. expand=relations to include linked items.

List Builds

List recent builds

Tips

• Recent builds. Filter by definitionId, statusFilter, resultFilter.

List Pipelines

List build pipelines

Tips

• Returns pipeline definitions in the project.

List Projects

List all projects

No input parameters.

Tips

• Returns projects in your org. Pages via continuationToken.

List Pull Requests

List pull requests

Tips

• project required. Filter by repositoryId, sourceRefName, targetRefName, status (active, abandoned, completed).

List Repos

List Git repositories

Tips

• project: name or ID. Returns Git repos in that project.

Query Work Items

Query work items by WIQL

Tips

• query: WIQL (Work Item Query Language) – SQL-like. e.g. 'SELECT [System.Id] FROM WorkItems WHERE [System.State] = "Active"'.
• Returns work item IDs. Fetch full data via Get Work Item.

Run Pipeline

Trigger a pipeline run

Tips

• pipeline_id from List Pipelines.
• resources: branch/commit/repository overrides. Common: resources.repositories.self.refName='refs/heads/main'.
• templateParameters for parameterised pipelines.

FAQ

Server / on-prem TFS – supported?

Azure DevOps Server (formerly TFS) has the same REST API but at a self-hosted URL. Configure the base URL on the connection.

PAT expiry – what happens?

Calls start returning 401. Generate a new PAT in user settings + update the connection. PATs can be auto-rotated via Microsoft Identity, not exposed in this connector.

Why does Create Work Item need JSON Patch?

Azure DevOps uses RFC 6902 JSON Patch for write ops on work items. Less intuitive than plain JSON; connector expects you to pre-build the patch document.

Multi-project / multi-org?

One connection per org. Multiple projects within an org work with the same connection – just pass different project params.

Related connectors

• Github
• Gitlab
• Bitbucket
• Jira