Microsoft Azure AzureDeploymentManager
Browse all Azure APIs★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeoauth227 EndpointsREST
For Agents
Orchestrate staged, multi-region Azure resource rollouts — define artifact sources, service topologies, and rollout steps, then start, restart, or cancel rollouts.
Use for: I need to start a staged Azure rollout across multiple regions, Cancel an in-flight rollout that is failing in a target region, Create an artifact source that points to my ARM templates, List all rollouts in a resource group and check their status
Not supported: Does not handle compute provisioning, ARM template authoring, or CI/CD pipeline triggers — use for staged multi-region rollout orchestration only.
Jentic publishes the only available OpenAPI specification for AzureDeploymentManager, keeping it validated and agent-ready. The Azure Deployment Manager (ADM) API orchestrates safe, staged rollouts of Azure resources across regions using artifact sources, service topologies, and step-by-step rollouts. It coordinates pre and post deployment health checks, manual intervention gates, and wait steps so multi-region updates can be staged, monitored, and cancelled if a region fails. Use it to model service topologies, define rollout steps, and track or cancel in-flight rollouts via the Azure Resource Manager.
Install Jentic One Beta
Connect the AzureDeploymentManager to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AzureDeploymentManager, 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 AzureDeploymentManager API.
Define artifact sources that point to ARM template repositories for staged rollouts
Model service topologies and service units that describe what gets deployed where
Author rollout steps including health checks and wait steps for safe progression
Start, monitor, cancel, or restart in-flight rollouts across multiple Azure regions
List operational metadata for Microsoft.DeploymentManager via the Azure Resource Manager
Coordinate manual approval gates between rollout regions before continuing deployment
Use Cases
Patterns agents use AzureDeploymentManager API for, with concrete tasks.
★ Multi-region staged service rollout
Coordinate the rollout of a global service across regions with the Azure Deployment Manager. Operators define a service topology, a sequence of rollout steps with health checks and wait gates, then call PUT on /rollouts/{rolloutName} to start. ADM advances region-by-region and stops automatically if a step fails, giving release engineers a safe alternative to ad-hoc ARM template runs.
Create an ArtifactSource pointing at an SAS-protected ARM template, define a two-region ServiceTopology, and start a Rollout with a 15-minute wait step between regions
Rollback when a region fails
When a deployment step reports unhealthy in a target region, an on-call agent can call POST /rollouts/{rolloutName}/cancel to stop progression, inspect the failed step via Steps_Get, and trigger remediation. This lets agents implement automated guard rails on top of ADM rollouts rather than rolling back manually through the portal.
List active rollouts in a resource group, find the one with status Failed, and call Rollouts_Cancel to halt further region progression
Manage service topology as code
Platform teams describe their global services as ServiceTopologies, ServiceUnits, and Steps so each release reuses the same shape. Agents query and update these resources via the ARM API, keeping the topology version-controlled alongside application code rather than maintained as portal clicks.
Update a ServiceUnit to point at a new ARM template version and trigger Rollouts_CreateOrUpdate to roll the change out
AI agent integration via Jentic
Release engineering agents use Jentic to discover Azure Deployment Manager operations by intent rather than hand-coding ARM calls. The agent searches Jentic for 'orchestrate an Azure rollout', loads the operation schema for Rollouts_CreateOrUpdate, and executes with structured input. Jentic handles the OAuth2 token exchange against the azure_auth flow so the agent never sees the raw bearer token.
Use Jentic search to find Rollouts_CreateOrUpdate, load its schema, and execute a rollout with a generated ARM template artifact source
Key Endpoints
27 endpoints — jentic publishes the only available openapi specification for azuredeploymentmanager, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DeploymentManager/rollouts/{rolloutName}
Create or update a rollout
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DeploymentManager/rollouts/{rolloutName}/cancel
Cancel an in-flight rollout
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DeploymentManager/rollouts/{rolloutName}/restart
Restart a paused rollout
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DeploymentManager/serviceTopologies/{serviceTopologyName}
Create or update a service topology
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DeploymentManager/artifactSources/{artifactSourceName}
Create or update an artifact source
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DeploymentManager/steps/{stepName}
Create or update a rollout step
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DeploymentManager/rollouts/{rolloutName}
Create or update a rollout
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DeploymentManager/rollouts/{rolloutName}/cancel
Cancel an in-flight rollout
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DeploymentManager/rollouts/{rolloutName}/restart
Restart a paused rollout
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DeploymentManager/serviceTopologies/{serviceTopologyName}
Create or update a service topology
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DeploymentManager/artifactSources/{artifactSourceName}
Create or update an artifact source
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DeploymentManager/steps/{stepName}
Create or update a rollout step
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Azure AD OAuth 2.0 tokens are minted and rotated inside the Jentic vault. Agents receive scoped, short-lived tokens for management.azure.com — client secrets and refresh tokens never enter agent context.
Intent-based discovery
Agents search Jentic by intent, e.g. 'orchestrate an Azure rollout', and Jentic returns the matching operation (Rollouts_CreateOrUpdate) along with its input schema, so the agent calls the right endpoint without browsing ARM docs.
Time to first call
Direct integration: 2-4 days to wire AAD auth, ARM polling, and rollout state handling. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using AzureDeploymentManager API through Jentic.
Why is there no official OpenAPI spec for AzureDeploymentManager?
Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AzureDeploymentManager via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the AzureDeploymentManager API use?
The API uses Azure Active Directory OAuth 2.0 with the implicit flow declared as the azure_auth security scheme. Tokens are presented as Bearer tokens against management.azure.com. Through Jentic, the OAuth exchange and token rotation are handled in the vault — agents call the operation by name and never see the raw access token.
Can I cancel a rollout that is already running with this API?
Yes. Call POST on /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DeploymentManager/rollouts/{rolloutName}/cancel (operationId Rollouts_Cancel). The rollout stops at the current step and you can later call the matching restart endpoint to resume.
What are the rate limits for the AzureDeploymentManager API?
Azure Resource Manager applies subscription-level throttling — typically 12,000 read and 1,200 write requests per hour per subscription, returned via x-ms-ratelimit-remaining headers. Deployment Manager does not document additional limits beyond ARM.
How do I start a staged rollout through Jentic?
Run pip install jentic, then use the async client to search 'orchestrate an Azure rollout', load the Rollouts_CreateOrUpdate operation, and execute with your ServiceTopology and ArtifactSource references. Jentic returns the rollout resource so you can poll its status.
Does the API support ARM templates other than those stored in storage accounts?
ArtifactSources currently support SAS-protected Azure storage accounts as the artifact root. Other source types are not described in the spec, so use a storage-backed ArtifactSource as the input to your rollout.
GET STARTED