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

# Microsoft Azure SubscriptionsManagementClient

Jentic publishes the only available OpenAPI specification for SubscriptionsManagementClient, keeping it validated and agent-ready. The Admin Subscriptions Management Client exposes the Azure Stack admin endpoint for managing the plans acquired by tenant subscriptions on a stamp. It supports listing, retrieving, creating, and deleting plan acquisitions associated with a target subscription. Use it for operator-side control of which Azure Stack plans are attached to which tenant subscriptions.

## For AI agents

Manage Azure Stack acquired plans on tenant subscriptions: list, retrieve, attach, and delete plan acquisitions per target subscription.

## Scope

Does not manage public Azure subscriptions, list offers, or run tenant workloads - use for Azure Stack admin acquired plans on tenant subscriptions only.

## Capabilities

- List every acquired plan attached to a target tenant subscription
- Retrieve a single acquired plan by its plan acquisition id
- Attach a new plan acquisition to a target subscription on Azure Stack
- Remove a plan acquisition to detach a plan from a tenant subscription
- Operate exclusively against the Azure Stack admin endpoint for tenant plan governance

## Use cases

### Tenant Plan Governance on Azure Stack

Azure Stack operators control which plans tenants can use by attaching plan acquisitions to target subscriptions. SubscriptionsManagementClient lists the acquired plans on a target subscription, supports adding new plan acquisitions via PUT, and removing them via DELETE. This drives a governance workflow where plan changes are scripted from a CMDB rather than applied manually in the admin portal.

Example prompt: List acquired plans on target subscription '11111111-2222-3333-4444-555555555555' under admin subscription 'aaaa...' and attach a new plan acquisition referencing plan id 'standard-plan-2026'.

### Tenant Onboarding Automation

When a new tenant is onboarded onto Azure Stack, the operator must attach the right plans to enable consumption of compute, storage, and networking. SubscriptionsManagementClient supports the AcquiredPlans_Create call (PUT under the target subscription) so the onboarding pipeline can issue the plan acquisition as part of an end-to-end script.

Example prompt: PUT a new acquired plan with id 'plan-acq-001' on target subscription 'tenant-1' referencing plan resource id 'resource-id-of-standard-plan'.

### Tenant Offboarding Cleanup

When a tenant leaves a stamp, plan acquisitions attached to that subscription need to be removed before the subscription itself is decommissioned. SubscriptionsManagementClient supports DELETE on /acquiredPlans/{planAcquisitionId} so an offboarding workflow can sweep all plan acquisitions before tearing down the subscription record.

Example prompt: List all acquired plans on target subscription 'tenant-leaving' and call DELETE for each planAcquisitionId returned.

### Agent-Driven Stack Operations via Jentic

An AI agent supporting an Azure Stack operations team can apply plan acquisitions through Jentic. The agent searches by intent, loads the AcquiredPlans operation schemas, and submits the requests against the admin endpoint. Jentic isolates the admin Azure AD credentials.

Example prompt: Use Jentic to load the SubscriptionsManagementClient AcquiredPlans_List operation, then call it for target subscription 'tenant-1' and summarise the plan acquisitions by plan name.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /subscriptions/{subscriptionId}/providers/Microsoft.Subscriptions.Admin/subscriptions/{targetSubscriptionId}/acquiredPlans | List acquired plans on a target tenant subscription |
| GET | /subscriptions/{subscriptionId}/providers/Microsoft.Subscriptions.Admin/subscriptions/{targetSubscriptionId}/acquiredPlans/{planAcquisitionId} | Get a specific acquired plan by id |
| PUT | /subscriptions/{subscriptionId}/providers/Microsoft.Subscriptions.Admin/subscriptions/{targetSubscriptionId}/acquiredPlans/{planAcquisitionId} | Create or attach a plan acquisition to a target subscription |
| DELETE | /subscriptions/{subscriptionId}/providers/Microsoft.Subscriptions.Admin/subscriptions/{targetSubscriptionId}/acquiredPlans/{planAcquisitionId} | Delete a plan acquisition from a target subscription |

## Key resources

- **Acquired Plans** — Plan acquisitions attached to a target tenant subscription, with list, get, create, and delete

## Why Jentic

- **Setup:** Wiring SubscriptionsManagementClient by hand means resolving the Azure Stack admin endpoint at adminmanagement.local.azurestack.external, configuring Azure AD OAuth 2.0 against the stamp's admin tenant, pinning the 2015-11-01 api-version, and coding the ARM-style 429 back-off yourself before you can attach a plan. Through Jentic you install once, import SubscriptionsManagementClient from the API Directory, store the Azure Stack admin OAuth token once, and your agent calls it.
- **Permission scoping:** The target subscription and plan acquisition id are URL path parameters (/subscriptions/{subscriptionId}/providers/Microsoft.Subscriptions.Admin/subscriptions/{targetSubscriptionId}/acquiredPlans/{planAcquisitionId}), so a rule can pin your agent to acquired plans on one target subscription. You choose the operations it may call, so destructive ones like delete a plan acquisition or attach one with PUT are not included unless you add them.
- **Credential handling:** Your Azure Stack admin OAuth token 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 acquired plans on an Azure Stack subscription' or 'attach a plan to a tenant subscription', and Jentic returns the matching operation with its input schema so the agent supplies the subscription and plan ids without reading the Azure Stack admin reference.

## Related APIs

- **SubscriptionDefinitionsClient** — Public Azure subscription definition creation rather than Azure Stack plan acquisitions
- **SubscriptionClient** — Lists offers used as inputs to subscription creation on public Azure
- **StorageManagementClient** — Azure Stack admin storage acquisitions endpoint on the same admin base URL

## FAQ

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

Microsoft Azure publishes Swagger fragments for the Azure Stack admin Microsoft.Subscriptions.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 SubscriptionsManagementClient 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 SubscriptionsManagementClient use?

All endpoints require 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 vault and injected at call time so the agent never sees the raw bearer token.

### Can I attach a plan to a tenant subscription on Azure Stack?

Yes. PUT /subscriptions/{subscriptionId}/providers/Microsoft.Subscriptions.Admin/subscriptions/{targetSubscriptionId}/acquiredPlans/{planAcquisitionId} attaches a plan to the target tenant subscription. The body references the plan resource id and any associated SKU.

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

Calls go through the Azure Stack admin endpoint, which inherits the Azure Resource Manager throttling pattern (writes typically capped per subscription per hour). Throttled responses return HTTP 429 with a Retry-After header; the spec does not encode these limits, so handle them in client code.

### How do I list acquired plans through Jentic?

Run pip install jentic, search Jentic for 'list acquired plans on an azure stack subscription', load the AcquiredPlans_List operation, and execute it with subscriptionId, targetSubscriptionId, and the api-version 2015-11-01. 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 subscription provisioning, use SubscriptionDefinitionsClient and SubscriptionClient.

### Can I limit what my agent is allowed to do with the Azure Stack Subscriptions Management API?

Yes. Because you run Jentic One yourself, your own rules decide which acquired-plans operations and credentials the agent may use. The target subscription and plan acquisition id are URL path parameters, so a rule can pin the agent to acquired plans on a single target subscription and grant only the read calls, list acquired plans and get a plan by id, while withholding the PUT that attaches a plan and the DELETE that removes one. Nothing destructive is callable unless you explicitly add it to the agent's allowed operations.