This page is also inEN
iTeam
API guide · Development and cloud With your company’s credentials

Azure DevOps API: work items, repositories and pipelines with AI

Azure DevOps exposes Boards, Repos, Pipelines, Test Plans and Artifacts through a versioned REST API. Engineering and IT teams use it to automate workflows and connect to other systems. Access is through a personal access token (PAT) or a Microsoft Entra ID identity.

Nina
API guide

What the Azure DevOps API offers

Work items and WIQL

Create, update and query work items with the WIQL language.

Repositories and pull requests

Read code, branches and commits, and comment on pull requests.

Pipelines

Trigger runs and read the logs and status of builds and releases.

Test Plans

Look up test plans, cases and results.

Service hooks

Send events to external systems.

Projects and teams

Look up projects, areas, iterations and members.

How to access the Azure DevOps API

  • With your company’s credentialsA personal access token (PAT) with limited scopes, or OAuth or a managed identity from Microsoft Entra ID, which is recommended for integrations.
  • PATs expire and give broad access, so prefer minimum scopes and Entra ID.
  • Triggering production pipelines only with approval.
  • Usage limits apply per user, so the agent avoids large scans.

Official documentation: learn.microsoft.com/rest/api/azure/devops

What an iTeam agent does with the Azure DevOps API

Pull request review

The agent reads the diff, points out risks and leaves comments for the human reviewer to decide.

Broken build explained

When the pipeline fails, the agent reads the log and posts the likely cause in Teams.

Sprint status

The agent queries the iteration and summarizes what was delivered and what is blocked.

A well-documented bug

User reports become work items with steps, environment and priority.

From the credential to the agent at work, with approval

01

Create the access

Create a service identity or a PAT with minimum scopes (for example, read access to work items and code) in the organization.

02

Store the access and limit what each agent does

The Azure DevOps access is registered in the iTeam vault. You choose which agents use it and what they can do (query work items, comment on a PR, read pipelines), with a cost ceiling and a record of every call.

03

Run the pilot with approval

In the pilot, ask the agent for a comment on a test PR. The team approves sensitive actions and follows the call history in iTeam.

Questions

Questions about the Azure DevOps API

Is the Azure DevOps API free?

The API comes with Azure DevOps; the cost is that of the users and plan resources, such as pipeline parallelism.

Do I need to write code to use the Azure DevOps API with iTeam?

Not necessarily. The iTeam deployment team sets up the Azure DevOps access and each agent's actions from the documentation; IT only releases the credential and reviews the permissions.

Is there an MCP server for Azure DevOps?

Yes, Microsoft provides an MCP server for Azure DevOps. iTeam can use it or call the REST API directly.

Next step

Put an AI team to work this week.

Start free with a pre-built team, or talk to us and our squad puts AI in production with your people.

300+integrations
4languages
Agents working right now