Microsoft Azure Azure DevOps
Browse all Azure APIs★ Only Publicly Available OpenAPI DocumentDeveloper ToolsCi Cdoauth28 EndpointsREST
For Agents
Provision and manage ARM-modelled Azure DevOps Pipelines that connect source repos to Azure resources via templates. Supports eight endpoints across pipelines, templates, and operations.
Use for: I need to create an Azure DevOps pipeline that deploys to App Service, List all Microsoft.DevOps pipelines in subscription 1111-2222, Retrieve the template parameters of an existing pipeline, Find the available pipeline template definitions
Not supported: Does not run builds, manage work items, manage repos, or expose Azure DevOps Services data-plane operations — use for ARM-modelled Microsoft.DevOps pipeline resources only.
This API is the Microsoft.DevOps ARM resource provider that manages Azure DevOps Pipelines as ARM resources, distinct from the data-plane Azure DevOps Services REST API. It exposes eight endpoints for listing, retrieving, creating, updating, and deleting pipeline resources scoped to subscriptions or resource groups, plus pipeline template definitions and operations discovery. Pipeline resources connect a source repository, an organisation profile, and a target Azure resource through a chosen pipeline template.
Install Jentic One Beta
Connect the Azure DevOps to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Azure DevOps, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Azure DevOps API.
Provision a pipeline resource that wires a Git repository to an Azure target via a template
List pipelines across a subscription or scope queries to a single resource group
Retrieve a single pipeline to inspect its repository, organisation, and template configuration
Patch an existing pipeline to update tags or template parameters
Delete a pipeline resource that is no longer required
Browse pipelineTemplateDefinitions to find supported templates and their parameter schemas
List Microsoft.DevOps resource provider operations available to a tenant
Use Cases
Patterns agents use Azure DevOps API for, with concrete tasks.
★ Wire a Repo to an Azure App Service via Template
Provision a Microsoft.DevOps pipeline that links a GitHub repository to an Azure App Service through a template such as a Node.js or Python deployment. The Resource Provider API takes a single PUT with the source repo, organisation profile, and template ID plus parameters, and the pipeline appears in both Azure Resource Manager and the linked Azure DevOps organisation. This removes the need to script the equivalent steps in the data-plane Azure DevOps API.
PUT /subscriptions/{subscriptionId}/resourceGroups/rg-builds/providers/Microsoft.DevOps/pipelines/web-deploy with the chosen template ID, source repo URL, branch=main, and the App Service target resource ID.
Discover Available Pipeline Templates
Before creating a pipeline, list the available templates so the right one can be picked for the target workload. PipelineTemplateDefinitions_List returns each template with its required parameters, languages, and target resource types, which lets a generation agent or wizard build a parameter form deterministically. The same call backs the template chooser surfaced in the Azure portal.
Call GET /providers/Microsoft.DevOps/pipelineTemplateDefinitions and return every template whose parameters list includes 'appServiceName'.
Cross-Subscription Pipeline Inventory
Build a portfolio inventory of pipelines created via the Microsoft.DevOps resource provider across multiple subscriptions. Pipelines_ListBySubscription returns every pipeline along with its repository, organisation, and template ID, which is enough to feed governance and ownership reports. Resource-group scoped variants exist for finer slicing.
List Microsoft.DevOps pipelines in every subscription accessible to the agent and emit one row per pipeline with subscriptionId, resourceGroupName, name, and template ID.
Agent-Driven Pipeline Cleanup
A Jentic agent reconciles ARM-modelled pipelines with a list of active services. Pipelines whose target resource has been deleted or whose source repo is archived are removed via the Pipelines_Delete operation. The agent uses the same eight endpoints in this spec to enumerate, inspect, and delete pipelines without portal access.
List pipelines in subscription 1111-2222, cross-reference each pipeline's target resource ID against the list of live resources, and DELETE every pipeline whose target no longer exists.
Key Endpoints
8 endpoints — this api is the microsoft.
METHOD
PATH
DESCRIPTION
GET
/providers/Microsoft.DevOps/operations
List Microsoft.DevOps operations
GET
/providers/Microsoft.DevOps/pipelineTemplateDefinitions
List available pipeline templates
GET
/subscriptions/{subscriptionId}/providers/Microsoft.DevOps/pipelines
List pipelines in a subscription
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DevOps/pipelines
List pipelines in a resource group
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DevOps/pipelines/{pipelineName}
Get a single pipeline
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DevOps/pipelines/{pipelineName}
Create or update a pipeline
PATCH
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DevOps/pipelines/{pipelineName}
Patch tags or template parameters
DELETE
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DevOps/pipelines/{pipelineName}
Delete a pipeline resource
GET
/providers/Microsoft.DevOps/operations
List Microsoft.DevOps operations
GET
/providers/Microsoft.DevOps/pipelineTemplateDefinitions
List available pipeline templates
GET
/subscriptions/{subscriptionId}/providers/Microsoft.DevOps/pipelines
List pipelines in a subscription
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DevOps/pipelines
List pipelines in a resource group
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DevOps/pipelines/{pipelineName}
Get a single pipeline
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DevOps/pipelines/{pipelineName}
Create or update a pipeline
PATCH
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DevOps/pipelines/{pipelineName}
Patch tags or template parameters
DELETE
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DevOps/pipelines/{pipelineName}
Delete a pipeline resource
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Azure AD service principal credentials are stored encrypted in the Jentic MAXsystem vault. The agent calls Microsoft.DevOps endpoints with a scoped bearer token issued at runtime, and any source-repo OAuth tokens (e.g. GitHub) are vaulted separately so neither set of secrets enters the prompt.
Intent-based discovery
Agents search Jentic by intent (e.g. "create azure devops pipeline for app service") and Jentic returns the matching Pipelines operation along with the parameter schema for the chosen pipeline template, removing the need to read ARM docs.
Time to first call
Direct integration: about a day for AAD setup, ARM long-running operation polling, and template parameter discovery. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Complementary
GitHub REST API
Manages the source repositories that Microsoft.DevOps pipelines connect to.
Use when the agent must create or configure the source repo a pipeline will connect to.
FAQs
Specific to using Azure DevOps API through Jentic.
What authentication does this Azure DevOps resource provider API use?
Azure Active Directory OAuth 2.0 via the azure_auth scheme (user_impersonation scope) on https://management.azure.com/. With Jentic, AAD client credentials live in the MAXsystem vault and the agent receives a runtime bearer token, never the secret.
Is this the same as the Azure DevOps Services REST API?
No. This is the Microsoft.DevOps ARM resource provider for managing pipelines as Azure resources. The Azure DevOps Services REST API at dev.azure.com is a separate data-plane API for boards, repos, builds, and releases inside an Azure DevOps organisation.
What are the rate limits for this API?
It shares Azure Resource Manager subscription throttling, typically 12,000 reads and 1,200 writes per hour per subscription. Honour 429 responses and the Retry-After header; the spec does not declare per-endpoint quotas.
How do I list available pipeline templates through Jentic?
Search Jentic for "list azure devops pipeline templates", load the schema for PipelineTemplateDefinitions_List, then execute. The response includes each template's ID, parameters, and supported target types. Sign up at https://app.jentic.com/sign-up.
Can I update template parameters on an existing pipeline?
Yes. PATCH /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DevOps/pipelines/{pipelineName} with an updated pipelineTemplateParameters block. Tags can be patched the same way.
Where do builds and releases run?
Pipeline execution still runs inside the linked Azure DevOps organisation. This API only models the pipeline as an ARM resource for provisioning and inventory; build logs, artifacts, and run history are read through the Azure DevOps Services data-plane API.
GET STARTED