Microsoft Azure SubscriptionClient
Browse all Azure APIs★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeoauth23 EndpointsREST
For Agents
List the Azure subscription offers available to a tenant, including delegated-provider offers, for procurement and signup flows.
Use for: List all Azure subscription offers available in my tenant, Find offers exposed through a specific delegated provider, Retrieve the details of a named offer from a delegated provider, I want to enumerate available subscription plans for procurement
Not supported: Does not create subscriptions, manage billing, or transact purchases — use for listing Azure subscription offers (public and delegated-provider) only.
Jentic publishes the only available OpenAPI specification for SubscriptionClient, keeping it validated and agent-ready. The User Subscription Management Client exposes the public-tenant offers catalogue used during Azure subscription acquisition, including offers presented directly and offers presented via delegated providers. It supports listing offers and retrieving a specific offer scoped to a delegated provider id. Use it to enumerate the subscription offers a tenant can acquire and to integrate the offer catalogue into custom signup or procurement flows.
Install Jentic One Beta
Connect the SubscriptionClient to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SubscriptionClient, 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
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 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 SubscriptionClient API.
List the public offers a tenant can acquire to create new subscriptions
List the offers presented through a specific delegated provider
Retrieve a specific delegated-provider offer by name
Surface offer metadata such as plan name, identifiers, and entitlements
Drive a custom signup or procurement UI from a live offer catalogue
Use Cases
Patterns agents use SubscriptionClient API for, with concrete tasks.
★ Custom Subscription Signup Flow
A managed-service provider building a self-service portal needs to show prospective customers the subscription offers they can sign up for, including any partner-mediated plans. SubscriptionClient surfaces both the public offers list and the offers exposed by a specific delegated provider. The portal calls Offers_List during page load and renders the live catalogue without hard-coding offer ids.
Call GET /offers to list public Azure subscription offers, then call /delegatedProviders/{delegatedProviderId}/offers for the partner id 'csp-eu-1' and merge the results.
Partner-Mediated Procurement Integration
Cloud Solution Provider (CSP) partners expose offers through delegated provider records. SubscriptionClient supports listing those offers per delegated provider and retrieving a specific offer by name, enabling a procurement system to ingest the partner's catalogue and reconcile it with internal SKUs. Combined with deeper Azure billing APIs, this drives end-to-end procurement automation.
Retrieve the offer named 'MS-AZR-0145P' from delegated provider 'csp-eu-1' and emit its plan identifier and display metadata.
Agent-Driven Catalogue Refresh via Jentic
An AI agent supporting a procurement or finance team refreshes the offer catalogue on demand. Through Jentic, the agent searches by intent, loads the Offers_List operation schema, and returns the catalogue to the user without learning the Azure tenant model. Tokens stay inside the Jentic vault.
Use Jentic to load the SubscriptionClient Offers_List operation, then return the full list of offers to the user.
Key Endpoints
3 endpoints — jentic publishes the only available openapi specification for subscriptionclient, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/offers
List public Azure subscription offers
GET
/delegatedProviders/{delegatedProviderId}/offers
List offers exposed by a delegated provider
GET
/delegatedProviders/{delegatedProviderId}/offers/{offerName}
Retrieve a delegated-provider offer by name
GET
/offers
List public Azure subscription offers
GET
/delegatedProviders/{delegatedProviderId}/offers
List offers exposed by a delegated provider
GET
/delegatedProviders/{delegatedProviderId}/offers/{offerName}
Retrieve a delegated-provider offer by name
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Azure AD OAuth tokens are stored encrypted in the Jentic vault (MAXsystem). Agents calling SubscriptionClient receive scoped, short-lived bearer tokens at execution time — refresh tokens and tenant secrets never enter the agent's context.
Intent-based discovery
Agents search Jentic by intent (e.g., 'list azure subscription offers') and Jentic returns the matching SubscriptionClient operation with its full input schema, so the agent can call the right endpoint without reading ARM docs.
Time to first call
Direct integration with Azure Resource Manager — service principal setup, MSAL token handling, api-version pinning — typically takes a full day. Through Jentic: under 30 minutes — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using SubscriptionClient API through Jentic.
Why is there no official OpenAPI spec for SubscriptionClient?
Microsoft Azure publishes Swagger fragments for the subscription offers surface but does not publish a consolidated, validated OpenAPI 3 spec. Jentic generates and maintains this spec so that AI agents and developers can call SubscriptionClient via structured tooling. It is validated against the live Azure Resource Manager endpoint and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the SubscriptionClient use?
All endpoints require Azure Active Directory OAuth 2.0, declared as the azure_auth security scheme with the user_impersonation scope against https://login.microsoftonline.com. Through Jentic, tokens are held in the vault and injected at call time so the agent never sees the raw bearer token.
Can I list offers from a specific delegated provider?
Yes. Call GET /delegatedProviders/{delegatedProviderId}/offers to list every offer exposed through the specified delegated provider, and GET /delegatedProviders/{delegatedProviderId}/offers/{offerName} to retrieve a single offer by name.
What are the rate limits for the SubscriptionClient?
Calls go through Azure Resource Manager, which applies subscription-level read throttling (typically 12,000 reads per hour per subscription, varying by region and tenant). Throttled responses return HTTP 429 with a Retry-After header.
How do I list Azure offers through Jentic?
Run pip install jentic, search Jentic for 'list azure subscription offers', load the SubscriptionClient Offers_List operation, and execute it. The api-version 2015-11-01 is required by the Azure endpoint; Jentic injects it automatically as a query parameter.
Does this API let me create a new subscription?
No. SubscriptionClient at this api-version exposes only the offers catalogue. Subscription creation lives under different Microsoft.Subscription endpoints, including SubscriptionDefinitionsClient for creating subscription definitions.
GET STARTED