Microsoft Azure StorageManagementClient
Browse all Azure APIs43
AI ReadinessFoundational (D-)43/100
Agent-ready OpenAPI document · curated by JenticCloud InfrastructureComputeoauth21 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Inspect storage acquisitions in an Azure Stack stamp by region, used by Azure Stack operators to monitor storage capacity events.
Use for: List storage acquisitions in my Azure Stack region eastus-stamp, Find every acquisition recorded by the Microsoft.Storage.Admin provider, Retrieve Azure Stack storage acquisition history for a specific location, Check whether storage acquisitions have been issued in this Azure Stack stamp
Not supported: Does not manage public Azure storage accounts, blobs, or files - use for Azure Stack admin storage acquisitions listing only.
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.
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.
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%2Fstoragemanagementclient" | 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%2Fstoragemanagementclient" | 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 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
Surface storage capacity acquisition history for an Azure Stack stamp
Support operator-side audits of Azure Stack storage activity
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
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
S
StorageManagementClient
- Foundational (D-)43/100
74
Foundational Compliance63
Developer Experience & Jentic Compatibility20
AI-Readiness & Agent Experience94
Agent Usability35
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
74
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
96%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
20
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
81%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
0%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
35
Security
Trust, risk posture, and security compliance.
Grade: FSignals: 1
35%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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
Alternatives and complements available in the Jentic catalogue.
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 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.
GET STARTED