Microsoft Azure StorageManagementClient

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.