Microsoft Azure StorageManagementClient

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeoauth21 EndpointsREST

For Agents

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

Install Jentic One Beta

Connect the StorageManagementClient to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the StorageManagementClient, 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.

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 | sh

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 instance

Jentic 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 StorageManagementClient API.

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

GET STARTED

Start building with StorageManagementClient API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use StorageManagementClient API for, with concrete tasks.

★ 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.

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.

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.

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

Key Endpoints

1 endpoints — jentic publishes the only available openapi specification for storagemanagementclient, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Storage.Admin/locations/{location}/acquisitions

List storage acquisitions in an Azure Stack location

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Storage.Admin/locations/{location}/acquisitions

List storage acquisitions in an Azure Stack location

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Azure Stack admin OAuth tokens are stored encrypted in the Jentic vault (MAXsystem). Agents calling StorageManagementClient receive scoped, short-lived bearer tokens at execution time — admin client secrets and refresh tokens never enter the agent's context.

Intent-based discovery

Agents search Jentic by intent (e.g., 'list azure stack storage acquisitions') and Jentic returns the matching StorageManagementClient operation with its full input schema, so the agent can call it without reading Azure Stack admin docs.

Time to first call

Direct integration with Azure Stack admin OAuth — discovery of the admin tenant, MSAL configuration, api-version handling — typically takes a full day. Through Jentic: under 30 minutes — search, load schema, execute.

FAQs

Specific to using StorageManagementClient API through Jentic.

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 at https://app.jentic.com/sign-up.

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 the Jentic vault 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.