Azure DevOps · Arazzo Workflow

Azure DevOps Provision a Build Definition and Run It

Version 1.0.0

Create a build definition, confirm it, and queue its first build.

1 workflow 1 source API 1 provider
View Spec View on GitHub AgileCI/CDDevOpsProject ManagementVersion ControlArazzoWorkflows

Provider

microsoft-azure-devops

Workflows

provision-build-definition
Create a build definition, confirm it, and queue its first build.
Creates a build definition, retrieves it to confirm creation, and queues an initial build.
3 steps inputs: accessToken, apiVersion, definition, sourceBranch outputs: buildId, definitionId
1
createDefinition
definitions_create
Create the build definition from the supplied definition body.
2
confirmDefinition
definitions_get
Fetch the build definition by ID to confirm it was created and capture its current revision.
3
queueFirstBuild
builds_queue
Queue an initial build against the newly created definition.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Azure DevOps Provision a Build Definition and Run It
  summary: Create a build definition, confirm it, and queue its first build.
  description: >-
    Stands up a new classic build definition and immediately exercises it. The
    workflow creates the build definition from a supplied definition body,
    fetches it by the returned ID to confirm the configuration, and then queues a
    first build against that definition. Every step spells out its request inline
    so the flow can be read and executed without opening the underlying OpenAPI
    description.
  version: 1.0.0
sourceDescriptions:
- name: buildsApi
  url: ../openapi/azure-devops-builds-api-openapi.yml
  type: openapi
workflows:
- workflowId: provision-build-definition
  summary: Create a build definition, confirm it, and queue its first build.
  description: >-
    Creates a build definition, retrieves it to confirm creation, and queues an
    initial build.
  inputs:
    type: object
    required:
    - apiVersion
    - definition
    properties:
      apiVersion:
        type: string
        description: Azure DevOps REST API version (e.g. 7.1).
      definition:
        type: object
        description: >-
          Build definition body matching BuildDefinitionCreateRequest (name,
          repository, process, queue, etc.).
      sourceBranch:
        type: string
        description: Optional source branch for the first queued build.
      accessToken:
        type: string
        description: Azure DevOps bearer (OAuth 2.0) access token.
  steps:
  - stepId: createDefinition
    description: >-
      Create the build definition from the supplied definition body.
    operationId: definitions_create
    parameters:
    - name: api-version
      in: query
      value: $inputs.apiVersion
    requestBody:
      contentType: application/json
      payload: $inputs.definition
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      definitionId: $response.body#/id
      definitionName: $response.body#/name
  - stepId: confirmDefinition
    description: >-
      Fetch the build definition by ID to confirm it was created and capture its
      current revision.
    operationId: definitions_get
    parameters:
    - name: api-version
      in: query
      value: $inputs.apiVersion
    - name: definitionId
      in: path
      value: $steps.createDefinition.outputs.definitionId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      revision: $response.body#/revision
  - stepId: queueFirstBuild
    description: >-
      Queue an initial build against the newly created definition.
    operationId: builds_queue
    parameters:
    - name: api-version
      in: query
      value: $inputs.apiVersion
    requestBody:
      contentType: application/json
      payload:
        definition:
          id: $steps.createDefinition.outputs.definitionId
        sourceBranch: $inputs.sourceBranch
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      buildId: $response.body#/id
      buildNumber: $response.body#/buildNumber
  outputs:
    definitionId: $steps.createDefinition.outputs.definitionId
    buildId: $steps.queueFirstBuild.outputs.buildId

Work with this as data

Every workflow here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/microsoft-azure-devops-build-definition-provision-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.