canonical: https://jentic.com/apis/azure.com/azure-keyvaultmanagementclient

# Microsoft Azure KeyVaultManagementClient

Jentic publishes the only available OpenAPI specification for KeyVaultManagementClient, keeping it validated and agent-ready. KeyVaultManagementClient is the Azure Stack admin control-plane API for the Microsoft.KeyVault.Admin resource provider. It exposes the operations catalog used by Azure Stack Hub administrators to inspect what management actions the local Key Vault provider supports. The surface is intentionally narrow and is designed for hub-level introspection rather than vault, key, or secret data operations.

## For AI agents

List the available admin operations exposed by the Microsoft.KeyVault.Admin resource provider on Azure Stack Hub. Use for provider capability discovery, not for managing vaults, keys, or secrets.

## Scope

Does not handle vault creation, key operations, secret storage, or certificate management - use only for listing Microsoft.KeyVault.Admin provider operations on Azure Stack Hub.

## Capabilities

- List the admin operations catalog exposed by the Microsoft.KeyVault.Admin resource provider
- Discover which Key Vault administrative actions are available on a given Azure Stack Hub deployment
- Audit the resource-provider operation surface for Azure Stack Key Vault compliance reviews
- Verify Key Vault admin RBAC scope by enumerating provider operations before assigning roles
- Confirm Microsoft.KeyVault.Admin provider availability during Azure Stack Hub deployment validation

## Use cases

### Azure Stack Hub Provider Discovery

Operators running Azure Stack Hub need to confirm which administrative operations are exposed by the Microsoft.KeyVault.Admin resource provider before authoring custom RBAC roles or admin runbooks. This API returns the operations catalog so administrators know exactly what action strings (for example, Microsoft.KeyVault.Admin/operations/read) can be used in role definitions. The endpoint is read-only and returns within milliseconds.

Example prompt: Call GET /providers/Microsoft.KeyVault.Admin/operations and return the list of operation names so the agent can build a custom RBAC role definition for a Key Vault administrator on Azure Stack Hub.

### Compliance and Audit Reviews

Security teams auditing Azure Stack Hub deployments need a deterministic list of every administrative action the Key Vault provider can expose. Calling Operations_List gives auditors the canonical action namespace so they can map RBAC assignments back to documented operations and flag drift. No vault data is returned, so the call is safe for read-only audit accounts.

Example prompt: Fetch the Microsoft.KeyVault.Admin operations list and produce a CSV of operation names mapped to existing RBAC role assignments for the audit report.

### Agent-Driven Azure Stack Tooling

AI agents building tooling around Azure Stack Hub use Jentic to discover the Microsoft.KeyVault.Admin operation list without scraping Microsoft documentation. The agent searches for a Key Vault admin discovery query, Jentic returns the structured operation, and the agent executes the call against an Azure Stack management endpoint with an OAuth 2.0 token from your Jentic One instance.

Example prompt: Use Jentic search to locate the KeyVaultManagementClient Operations_List endpoint, load its schema, and execute the call against the Azure Stack Hub admin management endpoint, returning the operation names to the orchestrator.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /providers/Microsoft.KeyVault.Admin/operations | List Microsoft.KeyVault.Admin provider operations |

## Key resources

- **KeyVault Operations** — Read-only listing of administrative operations exposed by the Microsoft.KeyVault.Admin resource provider on Azure Stack Hub.

## Why Jentic

- **Setup:** Wiring this Azure Stack Key Vault admin API by hand means registering an Azure AD app against your Azure Stack management endpoint, negotiating OAuth 2.0 tokens, and pointing calls at the management.local.azurestack.external host. Through Jentic you install once, import KeyVaultManagementClient from the API Directory, store the Azure AD credential once, and your agent calls it.
- **Permission scoping:** This API exposes a single read operation that lists Microsoft.KeyVault.Admin provider operations, so limit the agent to the operation it needs, which is listing those provider operations. You choose the operations it may call, so nothing beyond that read is included unless you add it.
- **Credential handling:** Your Azure AD credential for the Azure Stack admin surface 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.
- **Discovery method:** Agents search Jentic by intent such as 'list Azure Stack Key Vault admin operations', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **KeyVaultClient** — The data-plane API for managing keys, secrets, and certificates inside a vault.
- **ManagedServiceIdentityClient** — Provisions user-assigned managed identities that often need access to Key Vault.
- **PolicyClient** — Define and enforce Azure policies, including compliance checks against Key Vault provider actions.

## FAQ

### Why is there no official OpenAPI spec for KeyVaultManagementClient?

Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call KeyVaultManagementClient 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 KeyVaultManagementClient use?

It uses Azure Active Directory OAuth 2.0 bearer tokens scoped to the Azure Stack Hub admin management endpoint. Through Jentic, the OAuth client credentials and access tokens are stored encrypted in your Jentic One instance and never appear in the agent's context - agents receive scoped tokens only at call time.

### Can I manage vaults, keys, or secrets with the KeyVaultManagementClient?

No. This client only exposes GET /providers/Microsoft.KeyVault.Admin/operations, which returns the provider's operation catalog. To create vaults, manage keys, or read secrets you need the Azure Resource Manager Key Vault management API and the Key Vault data-plane API.

### What are the rate limits for the KeyVaultManagementClient?

Azure Resource Manager applies subscription-level throttling - typically 12,000 read requests per hour per subscription per region, with 429 responses including a Retry-After header. The single operations endpoint is rarely a bottleneck in practice.

### How do I list Key Vault admin operations through Jentic?

Run pip install jentic, then search Jentic for 'list azure stack key vault admin operations'. Jentic returns the Operations_List schema, after which the agent loads it and executes a GET against /providers/Microsoft.KeyVault.Admin/operations on your Azure Stack management endpoint.

### Is the KeyVaultManagementClient API free to use?

The API itself is included with Azure Stack Hub - there is no per-call charge for the operations endpoint. Underlying Azure Stack Hub licensing and support agreements still apply.

### Can I limit what my agent is allowed to do with the Microsoft Azure Key Vault admin API?

Yes. Because Jentic One is self-hosted, you decide which operations your agent may call, and this API exposes only one read operation, GET /providers/Microsoft.KeyVault.Admin/operations, which lists the provider's admin operation catalog. You can restrict the agent to that single read so it can enumerate Microsoft.KeyVault.Admin operations but cannot create vaults, manage keys, or read secrets. The Azure AD credential is held by your own Jentic One instance and injected only at call time, so the agent never sees it and can act only within the scope you set.