...
Itential Platform Pricing Explore flexible plans and options for your team
Itential logo

Microsoft Azure DevOps – Studio Project

Studio Project workflows for Microsoft Azure DevOps Git repos, pipelines, and work items

Azure DevOps Services is Microsoft's cloud-hosted platform for the software development lifecycle: Git source control, build and release pipelines, work item tracking, and project/team administration, all exposed through the Azure DevOps Services REST API.

Table of Contents

Contents

Asset Description
OpenAPIs/ Azure DevOps Services REST API OpenAPI specs — curated -latest plus the full derived spec
Studio Projects/ Itential Platform project containing 55 workflows in 7 folders

Requirements

Requirement Version
Itential Platform P6+
Azure DevOps Services Cloud SaaS (dev.azure.com) — no on-premises Azure DevOps Server support
Personal Access Token (PAT) Scoped to the resource areas the workflows will call (Code, Build, Work Items, Project and Team)

Integration Configuration

Import azure_devops-latest.json as an Integration Model in Admin > Integrations, then create an integration pointing at your organization.

Authentication is HTTP Basic, using a blank username and a Personal Access Token as the password:

Authorization: Basic <base64(:personal-access-token)>

The instance's authentication/server properties should look like this once configured:

{
  "authentication": {
    "basicAuth": {
      "username": "",
      "password": "<your-personal-access-token>"
    }
  },
  "server": {
    "protocol": "https",
    "host": "dev.azure.com",
    "base_path": "/<your-organization>"
  }
}

Every operation in the spec requires an api-version query parameter; it defaults to 7.1, the current stable Azure DevOps REST API version.

OpenAPIs

Both specs are scoped to 5 API areas: Projects & Teams, Git, Build, Pipelines, and Work Item Tracking.

Spec Version Operations Description
azure_devops-latest.json latest (curated) 55 Curated across Projects & Teams, Git, Build, Pipelines, and Work Item Tracking — see breakdown below
azure_devops-7.1.json 7.1 345 Full spec covering the complete operation surface of those 5 SDK API areas

azure_devops-latest.json

Curated to 55 of the several hundred operations across the SDK's Git, Build, Pipelines, and Work Item Tracking API areas alone (the full SDK surface also covers Release, Test Plans, Wiki, Service Endpoints, Task Agent pools, Security Roles, and more, none of which are included here).

Resources included, by category:

  • Projects & Teams: list/create/get/delete projects, list/create/get/update/delete teams
  • Git Repositories: list/create/get/update/delete repositories, list refs, list commits, get item content, list/create pushes
  • Git Pull Requests: list/create/get/update pull requests, list/add reviewers, add labels, list/create comment threads
  • Build: list/queue/get/update/delete builds, get build changes/logs/timeline
  • Build Definitions: list/create/get/update/delete build (pipeline) definitions
  • Pipelines: list/create/get pipelines, list/run pipeline runs, get a run
  • Work Item Tracking: create/get/update/delete work items, list work items by ID, query by WIQL, list/add comments

azure_devops-7.1.json

Full spec (345 operations) enumerating every method exposed by CoreApi.ts, GitApi.ts, BuildApi.ts, PipelinesApi.ts, and WorkItemTrackingApi.ts — not just the 55 curated for the Studio Project. This includes areas the curated spec omits entirely: Git annotated tags, cherry-picks, reverts, forks, and import requests; Build source providers, retention, templates, and webhooks; Work Item Tracking classification nodes, saved queries, fields, comment reactions, and work item type administration.

The SDK resolves each operation's REST route dynamically at runtime (via a server-side locations lookup keyed by a GUID, not a static template in the client code), so paths for the operations beyond the curated 55 were reconstructed from the Azure DevOps Services REST API reference and the SDK's own route/query parameter names — the 55 curated operations are carried into this spec unchanged, already hand-verified. Request/response bodies for the rest use generic object schemas rather than fully-typed models; consult the linked SDK method for the exact shape. As with the NetScaler NITRO full spec, this is a structurally-derived operation surface, not hand-verified per operation.

Studio Projects

Azure DevOps Project

Backed by the Azure DevOps:latest Integration Model (see azure_devops-latest.json above). The project contains 55 workflows organized into 7 folders, one workflow per API operation.

Folder Structure

Folder Workflows Scope
Projects & Teams 9 List/create/get/delete projects; list/create/get/update/delete teams
Git Repositories 10 Repository CRUD, refs, commits, item content, pushes
Git Pull Requests 9 Pull request CRUD, reviewers, labels, comment threads
Build 8 Build CRUD, changes, logs, timeline
Build Definitions 5 Build (pipeline) definition CRUD
Pipelines 6 Pipeline CRUD, runs
Work Item Tracking 8 Work item CRUD, WIQL query, comments

Agentic Infrastructure Operations Start Here

See how Itential connects AI reasoning to governed execution across your entire infrastructure.