Microsoft Azure UpdateAdminClient
Browse all Azure APIsAgent-ready OpenAPI document · curated by JenticCloud InfrastructureComputeoauth21 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Lists the available Microsoft.Update.Admin resource provider operations on an Azure Stack Hub admin endpoint for capability discovery and admin tooling.
Use for: List all operations the Microsoft.Update.Admin resource provider supports, Check whether the Update Admin RP is registered on this Azure Stack Hub stamp, Get the canonical operations list for the Update Admin provider on Azure Stack, Build a capability map of Microsoft.Update.Admin for an admin dashboard
Not supported: Does not download, install, or schedule updates on Stack Hub stamps and does not work against public Azure - use the full Stack Hub Update admin RP and the public Update Management API for those; this client only enumerates the provider's operations.
Jentic publishes the only available OpenAPI specification for UpdateAdminClient, keeping it validated and agent-ready. The Update Admin Management Client is the Azure Stack Hub admin-plane API for the Microsoft.Update.Admin resource provider. It lets a Stack Hub operator enumerate the operations the Update RP exposes - useful for capability discovery, documentation generation, and scripting tools that build admin dashboards over a privately deployed Azure Stack region. Authentication uses Azure Active Directory OAuth 2.0 against the local admin endpoint adminmanagement.local.azurestack.external.
Install Jentic One Beta
Connect the UpdateAdminClient to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the UpdateAdminClient, 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%2Fupdateadminclient" | 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%2Fupdateadminclient" | 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 UpdateAdminClient API.
Enumerate every operation exposed by the Microsoft.Update.Admin resource provider on an Azure Stack Hub region
Drive capability discovery for admin tooling that needs to know which Update Admin actions are available before invoking them
Generate documentation tables of Update Admin operations directly from the live Stack Hub region rather than static docs
Validate that the Microsoft.Update.Admin RP is registered and reachable on a freshly built Azure Stack Hub stamp
Feed an Azure Stack Hub operator dashboard with the canonical operation list so admin commands can be wired into UI menus
Use Cases
Patterns agents use UpdateAdminClient API for, with concrete tasks.
★ Stack Hub readiness check after deployment
After standing up a new Azure Stack Hub region, operators need to confirm that admin-plane RPs are registered and responding. Calling GET /providers/Microsoft.Update.Admin/operations returns the operation list if the provider is healthy and a 404 or 503 if it is not. The check is cheap, idempotent, and a useful first step in a post-deploy smoke test that runs against every admin RP.
Call GET /providers/Microsoft.Update.Admin/operations on the admin endpoint adminmanagement.local.azurestack.external and assert that the returned operation list is non-empty.
Capability discovery for admin UIs
An Azure Stack Hub admin dashboard that surfaces Update RP commands needs the canonical operation names so it can render menu items, map them to RBAC roles, and avoid hardcoding strings that drift across stamp versions. This endpoint returns each operation's name, display.provider, display.resource, and display.operation so the UI can group and label them automatically.
Fetch the operations list for Microsoft.Update.Admin and emit a JSON map of operation name > display.operation suitable for populating an admin UI sidebar.
Static documentation generation
Documentation pipelines that produce per-stamp admin reference docs benefit from pulling the operation list at build time rather than maintaining hand-edited tables. Calling this endpoint during the docs build emits a markdown table of every Update Admin operation along with its display metadata, ensuring docs always match the deployed stamp version.
Call the Update Admin operations endpoint, sort the response by display.operation, and write a markdown table with columns name, resource, operation, description.
Agent-driven Stack Hub admin scripting via Jentic
An agent automating Azure Stack Hub admin tasks can use Jentic to discover the Update Admin operations and chain them with other admin RP calls without scraping internal docs. Jentic returns the spec-described operation as a callable tool with the input schema attached, and credential handling for the admin Azure AD token stays inside the vault.
Search Jentic for 'list azure stack update admin operations', execute the operation against the admin endpoint, and return the operation count plus the names list.
Key Endpoints
1 endpoints — jentic publishes the only available openapi specification for updateadminclient, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/providers/Microsoft.Update.Admin/operations
List all operations exposed by the Microsoft.Update.Admin resource provider
GET
/providers/Microsoft.Update.Admin/operations
List all operations exposed by the Microsoft.Update.Admin resource provider
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring UpdateAdminClient by hand means resolving the Azure Stack Hub admin endpoint at adminmanagement.local.azurestack.external, configuring Azure AD OAuth 2.0 against the stamp's admin tenant, and pinning the 2016-05-01 api-version before you can even list the provider's operations. Through Jentic you install once, import UpdateAdminClient from the API Directory, store the Azure Stack admin OAuth token once, and your agent calls it.
Permission scoping
This client exposes a single read-only operation, GET /providers/Microsoft.Update.Admin/operations, which enumerates the provider's operations and takes no resource id. You choose the operations it may call, so the agent can be held to that one discovery read and nothing that changes state.
Credential isolation
Your Azure Stack admin OAuth token is stored once, encrypted, by your own Jentic One instance and injected 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 Update Admin operations', and Jentic returns the GET /providers/Microsoft.Update.Admin/operations operation with its input schema, which needs no parameters, so the agent runs it without reading the Azure Stack admin reference.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using UpdateAdminClient API through Jentic.
Why is there no official OpenAPI spec for UpdateAdminClient?
Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call UpdateAdminClient 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 UpdateAdminClient use?
It uses Azure Active Directory OAuth 2.0 with the user_impersonation scope. Because the base URL is adminmanagement.local.azurestack.external, the AAD tenant configured on the Azure Stack Hub stamp issues the token. Through Jentic, the admin AAD client secret is held encrypted and a scoped bearer token is issued at execution time.
Can I list all Update Admin operations with the UpdateAdminClient?
Yes. GET /providers/Microsoft.Update.Admin/operations returns the canonical operation list for the Microsoft.Update.Admin resource provider on the Stack Hub admin endpoint. The response includes name, display.provider, display.resource, display.operation, and description for each operation.
What are the rate limits for the UpdateAdminClient?
Azure Stack Hub admin-plane throttling is configured per stamp by the operator and is not declared in the spec. The endpoint is read-only and lightweight, so practical limits are well above normal admin-tooling traffic; respect any Retry-After header on a 429.
How do I call the UpdateAdminClient through Jentic?
Run pip install jentic, then client.search('list azure stack update admin operations'), client.load on the returned operation (GET /providers/Microsoft.Update.Admin/operations), and client.execute against the admin endpoint. Jentic injects the AAD bearer token from the vault.
Does the UpdateAdminClient work against public Azure?
No. The base URL is adminmanagement.local.azurestack.external, which only resolves inside an Azure Stack Hub admin network. For public Azure VM patching use the Update Management API on management.azure.com instead.
Can I limit what my agent is allowed to do with the Azure Update Admin API?
Yes. Because you run Jentic One yourself, you decide which operations your agent may call, and this API exposes only a single read-only operation, GET /providers/Microsoft.Update.Admin/operations, which enumerates the Microsoft.Update.Admin resource provider's operations and takes no resource id. You can hold the agent to that one discovery read so it can list available operations but cannot change any state on the Azure Stack Hub stamp. Your own rules also govern the Azure Active Directory admin token, which your self-hosted instance stores encrypted and injects only when the allowed operation runs, so it never enters the agent's prompt or logs.
GET STARTED