Microsoft Azure DeploymentAdminClient
Browse all Azure APIsAgent-ready OpenAPI document · curated by JenticCloud InfrastructureComputeoauth22 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
List and inspect Azure Stack deployment action plans at the Microsoft.Deployment.Admin global location.
Use for: List all Azure Stack deployment action plans for a subscription, Get the details of a specific Azure Stack deployment action plan, Find all action plans generated for an Azure Stack deployment, Check the status of a deployment action plan
Not supported: Does not create or execute action plans, manage deployments themselves, or handle Azure Stack hardware - use for read-only listing and inspection of action plans only.
Jentic publishes the only available OpenAPI specification for DeploymentAdminClient, keeping it validated and agent-ready. The API exposes Azure Stack deployment action plans under Microsoft.Deployment.Admin: a global per-subscription list and a per-plan get. Operators use it to inspect the action plans an Azure Stack deployment generates so they can audit or correlate them with deployment workflows.
Install Jentic One Beta
Connect the DeploymentAdminClient to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the DeploymentAdminClient, 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fdeploymentadminclient" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fdeploymentadminclient" | 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 DeploymentAdminClient API.
List all Azure Stack deployment action plans in a subscription
Retrieve the details of a specific deployment action plan by planId
Correlate deployment action plans with Azure Stack deployment workflows
Audit which action plans have been generated against a subscription
Use Cases
Patterns agents use DeploymentAdminClient API for, with concrete tasks.
★ Azure Stack deployment audit
Operators of Azure Stack environments need a record of every action plan generated by a deployment. The list endpoint returns the full set of plans in a subscription so an audit tool can reconcile plans against deployment workflows and confirm nothing ran outside the expected change window.
List all action plans on the configured Azure Stack subscription and return planId, status, and creation timestamp for each
Action plan deep-inspect
After a failed Azure Stack deployment an engineer needs the exact action plan referenced by the deployment workflow to diagnose the failure. The get-by-planId endpoint returns the full plan descriptor so the engineer can correlate plan steps with deployment logs from a separate system.
Retrieve the action plan with planId 'abc-123' and return its current state plus any embedded step definitions
Agent-driven deployment correlation
An AI agent triaging an Azure Stack deployment failure searches Jentic for action-plan listing operations, walks the recent plans for the affected subscription, and links a candidate planId back to the deployment workflow that triggered it. Jentic isolates the operator's Azure credentials from the agent context throughout the trace.
Find action plans created in the last 4 hours on the configured subscription and return the planId of any plan in a non-Succeeded state
Key Endpoints
2 endpoints — jentic publishes the only available openapi specification for deploymentadminclient, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Deployment.Admin/locations/global/actionPlans
List action plans for the subscription
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Deployment.Admin/locations/global/actionPlans/{planId}
Get a specific action plan by planId
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Deployment.Admin/locations/global/actionPlans
List action plans for the subscription
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Deployment.Admin/locations/global/actionPlans/{planId}
Get a specific action plan by planId
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Azure Stack deployment admin surface by hand means bootstrapping AD FS or Azure AD auth for the Azure Stack ARM endpoint, handling OAuth 2.0 bearer tokens, and shaping the Microsoft.Deployment.Admin action-plan requests yourself. Through Jentic you install once, import Deployment Admin Client from the API Directory, store the Azure credential once, and your agent calls it.
Permission scoping
This surface puts the plan identifier in the URL path (/subscriptions/{id}/providers/Microsoft.Deployment.Admin/locations/global/actionPlans/{planId}), so a rule can pin your agent to a subscription scope. Both operations are read-only, a subscription list and a per-plan get, so the agent inspects action plans and cannot create, execute, or delete anything through this API.
Credential isolation
Your Azure credential is stored once, encrypted, by your own Jentic One instance and injected as a scoped bearer token at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list Azure Stack deployment action plans' or 'get an action plan by id', and Jentic returns the matching operation with the subscriptionId and planId parameters surfaced from its schema so the agent calls it directly.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using DeploymentAdminClient API through Jentic.
Why is there no official OpenAPI spec for DeploymentAdminClient?
Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call DeploymentAdminClient via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the Deployment Admin Client API use?
The API is reached through Azure Resource Manager (or the Azure Stack ARM endpoint) and uses OAuth 2.0 bearer tokens issued by Azure Active Directory or AD FS for Azure Stack. Through Jentic the credential is held in the encrypted vault and a scoped bearer token is supplied at execute time.
Can I list every deployment action plan in a subscription with this API?
Yes. GET /subscriptions/{subscriptionId}/providers/Microsoft.Deployment.Admin/locations/global/actionPlans returns the full list of action plans for the subscription. Use the per-plan GET to fetch detail on any specific planId returned by the list.
What are the rate limits for the Deployment Admin Client API?
Azure Resource Manager applies subscription-level read throttles (around 12,000 reads per hour per subscription) and returns 429 with a Retry-After header when exceeded. The two read endpoints in this API are inexpensive but should still be cached when polled regularly.
How do I retrieve a specific action plan through Jentic?
Search Jentic for 'get azure stack deployment action plan', load the schema for GET .../actionPlans/{planId}, then execute with your subscriptionId and the planId of interest. The pip install jentic Python SDK uses the async search, load, execute pattern.
Is the Deployment Admin Client API free?
There is no per-call charge for the management API itself; Azure Stack billing is governed by your Azure Stack agreement and consumption of the underlying hardware and services, not by reads against this admin surface.
Can I limit what my agent is allowed to do with the Microsoft Azure Deployment Admin API?
Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, and this API exposes only two read-only operations: a per-subscription list of Azure Stack deployment action plans and a per-plan get by planId. The plan identifier and subscription both sit in the URL path, so you can pin the agent to a single subscription scope. Even at its broadest, the agent can only inspect action plans through this API; it cannot create, execute, or delete anything.
GET STARTED