canonical: https://jentic.com/apis/azure.com/storagemanagementclient

# Microsoft Azure StorageManagementClient

Jentic publishes the only available OpenAPI specification for StorageManagementClient, keeping it validated and agent-ready. The Admin Storage Management Client exposes the Azure Stack on-premises admin endpoint for the Microsoft.Storage.Admin resource provider. It returns the list of storage acquisitions in a given Azure Stack location, which represents disk acquisitions made by the storage service inside an Azure Stack stamp. Use it for operator-side observability of Azure Stack storage rather than public Azure cloud workloads.

## For AI agents

Inspect storage acquisitions in an Azure Stack stamp by region, used by Azure Stack operators to monitor storage capacity events.

## Scope

Does not manage public Azure storage accounts, blobs, or files - use for Azure Stack admin storage acquisitions listing only.

## Capabilities

- List all storage acquisitions in a specified Azure Stack location
- Filter acquisitions by subscription scope on the admin endpoint
- Retrieve acquisition records issued by the Microsoft.Storage.Admin provider
- Surface storage capacity acquisition history for an Azure Stack stamp
- Support operator-side audits of Azure Stack storage activity

## Use cases

### Azure Stack Storage Capacity Reporting

Azure Stack operators need visibility into the storage acquisitions that the platform has issued inside a given stamp, both for capacity planning and chargeback. The Acquisitions_List endpoint returns the acquisition records held by the Microsoft.Storage.Admin provider for a chosen location, scoped to an admin subscription. This drives nightly reports that track how disk allocation is evolving inside a stamp.

Example prompt: List all storage acquisitions in Azure Stack location 'redmond' under admin subscription '11111111-2222-3333-4444-555555555555'.

### Operator Audit of Disk Allocation

When an Azure Stack stamp shows unexpected storage pressure, operators want a chronological view of acquisitions that have been issued. The admin endpoint exposes acquisitions per location so an operator can correlate spikes in the acquisition record with tenant workloads running on the stamp. Combined with the broader Azure Stack admin APIs, it produces a clear capacity audit trail.

Example prompt: Pull acquisitions for Azure Stack location 'eastus-stamp' over the last 90 days and emit a CSV grouped by acquisition id.

### Agent-Driven Azure Stack Monitoring via Jentic

An AI agent monitoring an Azure Stack estate can call StorageManagementClient through Jentic without learning the admin OAuth flow. Jentic stores the admin Azure AD token in its vault and returns just the response payload to the agent. The agent surfaces acquisitions in a chat operator console.

Example prompt: Use Jentic to load the StorageManagementClient acquisitions list operation, then call it for location 'redmond' and summarise the result.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /subscriptions/{subscriptionId}/providers/Microsoft.Storage.Admin/locations/{location}/acquisitions | List storage acquisitions in an Azure Stack location |

## Key resources

- **Acquisitions** — List storage acquisitions issued by the Microsoft.Storage.Admin provider in a location

## Why Jentic

- **Setup:** Wiring this Microsoft.Storage.Admin endpoint by hand means discovering the on-premises Azure Stack admin host at adminmanagement.local.azurestack.external, running the OAuth2 token exchange against the admin tenant, and passing the correct admin api-version on every call. Through Jentic you install once, import Azure Stack Storage Management from the API Directory, store the Azure Stack admin credential once, and your agent calls it.
- **Permission scoping:** This API puts the admin subscription and Azure Stack location in the URL path (/subscriptions/{subscriptionId}/providers/Microsoft.Storage.Admin/locations/{location}/acquisitions), so a rule can pin your agent to listing acquisitions in one stamp location. The single operation here is a read, so you can limit the agent to just that acquisitions listing.
- **Credential handling:** Your Azure Stack admin credential 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 storage acquisitions for a location', and Jentic returns the matching Microsoft.Storage.Admin operation with its input schema so the agent calls the right endpoint without reading the Azure Stack admin reference.

## Related APIs

- **StorageImportExport** — Public Azure bulk data transfer for storage accounts
- **SubscriptionsManagementClient** — Azure Stack admin subscriptions management on the same admin endpoint
- **StorSimpleManagementClient** — Hybrid cloud storage appliance management for non-Azure-Stack environments

## FAQ

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

Microsoft Azure publishes Swagger fragments for the Azure Stack admin Microsoft.Storage.Admin provider but does not publish a consolidated, validated OpenAPI 3 spec. Jentic generates and maintains this spec so that AI agents and operators can call StorageManagementClient via structured tooling. It is validated against the live Azure Stack admin endpoint and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the StorageManagementClient use?

The endpoint requires Azure Active Directory OAuth 2.0 against the Azure Stack admin tenant, declared as the azure_auth security scheme with the user_impersonation scope. Through Jentic, the admin access token is held in your Jentic One instance and injected at call time so the agent never sees the raw bearer token.

### Can I list storage acquisitions for a specific Azure Stack location?

Yes. Call GET /subscriptions/{subscriptionId}/providers/Microsoft.Storage.Admin/locations/{location}/acquisitions where {subscriptionId} is the Azure Stack admin subscription and {location} is the stamp identifier (for example 'redmond' or 'eastus-stamp').

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

Calls go through the Azure Stack admin endpoint, which inherits the same per-subscription read throttling pattern as Azure Resource Manager. The exact ceiling varies by stamp configuration; throttled responses return HTTP 429 with a Retry-After header.

### How do I list Azure Stack acquisitions through Jentic?

Run pip install jentic, search Jentic for 'list azure stack storage acquisitions', load the Acquisitions_List operation, and execute it with subscriptionId, location, and the admin api-version 2019-08-08-preview. Jentic handles the Azure Stack admin token exchange.

### Does this API work against public Azure?

No. The base URL is https://adminmanagement.local.azurestack.external/, which is the on-premises Azure Stack admin endpoint. For public Azure storage, use the StorageImportExport API or the public Microsoft.Storage resource provider APIs.

### Can I limit what my agent is allowed to do with the Azure Stack Storage Management (Admin) API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, and this API has a single read operation that lists storage acquisitions, so you can restrict the agent to just that listing call. The admin subscription and Azure Stack location are carried in the request path (/subscriptions/{subscriptionId}/providers/Microsoft.Storage.Admin/locations/{location}/acquisitions), so you can pin the agent to acquisitions in one stamp location. The admin credential stays in your own instance and is injected at call time, so the agent never handles the raw token.