SubscriptionDefinitionsClient

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeoauth25 EndpointsREST

For Agents

Create, list, and retrieve Azure subscription definitions and check the status of asynchronous subscription creation operations.

Connect the SubscriptionDefinitionsClient to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SubscriptionDefinitionsClient, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

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

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 SubscriptionDefinitionsClient API.

Create a new Azure subscription definition by name

List every subscription definition in the calling tenant

Retrieve a specific subscription definition and its current state

Poll the status of an asynchronous subscription creation operation

GET STARTED

Start building with SubscriptionDefinitionsClient API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for SubscriptionDefinitionsClient, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for SubscriptionDefinitionsClient, keeping it validated and agent-ready. The Subscription Definitions client exposes a programmatic interface to create, retrieve, and list Azure subscription definitions, plus a long-running-operation status endpoint. It is part of the Microsoft.Subscription resource provider and is intended for tenants and CSPs that automate subscription provisioning at scale. Use it to script subscription creation flows that previously required manual portal steps.

Use Cases

Patterns agents use SubscriptionDefinitionsClient API for, with concrete tasks.

★ Automated Subscription Provisioning

Enterprises and CSPs that onboard new business units or customers regularly need to spin up Azure subscriptions programmatically. SubscriptionDefinitionsClient supports create-by-PUT on /subscriptionDefinitions/{name} with the offer and billing context, returning a long-running operation id. A provisioning service polls /subscriptionOperations/{operationId} until completion, then hands the new subscription to downstream automation.

Call PUT /providers/Microsoft.Subscription/subscriptionDefinitions/contoso-prod with the offerType and target tenant id, then poll the returned operation id every 30 seconds until status is Succeeded.

Subscription Inventory Across the Tenant

Finance and operations teams need an authoritative list of subscription definitions created in a tenant — both successful and in-flight. SubscriptionDefinitionsClient supports SubscriptionDefinitions_List for a full inventory and SubscriptionDefinitions_Get for a single record. Combined with billing data, this drives chargeback reports and licence audits.

List every subscription definition in the tenant and emit a CSV of name, state, and offerType.

Operation Status Tracking

Subscription creation is asynchronous, returning an operation id that may take minutes to complete. SubscriptionDefinitionsClient exposes /subscriptionOperations/{operationId} so a provisioning workflow can poll status without re-issuing the create request, which would risk duplicate subscriptions. This enables idempotent automation.

Poll GET /providers/Microsoft.Subscription/subscriptionOperations/abc-123 every 30 seconds until status is Succeeded or Failed and emit the final result.

Agent-Driven Subscription Creation via Jentic

An AI agent supporting a CSP back office can create new subscriptions on demand. Through Jentic, the agent searches by intent, loads the SubscriptionDefinitions_Create operation schema, and submits the request. Jentic isolates the Azure AD credential and surfaces only the operation id and final status to the agent.

Use Jentic to load the SubscriptionDefinitions_Create operation, then create a subscription definition 'tenant-onboarding-2026-q2' with the supplied offerType and tenant id.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/providers/Microsoft.Subscription/operations

List operations exposed by the resource provider

GET

/providers/Microsoft.Subscription/subscriptionDefinitions

List subscription definitions in the tenant

GET

/providers/Microsoft.Subscription/subscriptionDefinitions/{subscriptionDefinitionName}

Retrieve a subscription definition by name

PUT

/providers/Microsoft.Subscription/subscriptionDefinitions/{subscriptionDefinitionName}

Create a subscription definition

GET

/providers/Microsoft.Subscription/subscriptionOperations/{operationId}

Get the status of a long-running subscription operation

GET

/providers/Microsoft.Subscription/operations

List operations exposed by the resource provider

GET

/providers/Microsoft.Subscription/subscriptionDefinitions

List subscription definitions in the tenant

GET

/providers/Microsoft.Subscription/subscriptionDefinitions/{subscriptionDefinitionName}

Retrieve a subscription definition by name

PUT

/providers/Microsoft.Subscription/subscriptionDefinitions/{subscriptionDefinitionName}

Create a subscription definition

GET

/providers/Microsoft.Subscription/subscriptionOperations/{operationId}

Get the status of a long-running subscription operation

Why though 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 SubscriptionDefinitionsClient 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., 'create an azure subscription definition') and Jentic returns the matching SubscriptionDefinitionsClient operation with its full input schema, so the agent can submit create or status calls without reading ARM docs.

Time to first call

Direct integration with Azure Resource Manager — service principal setup, MSAL token handling, async operation polling — typically takes 1-2 days. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

SubscriptionClient

List public and delegated-provider offers used as input to subscription creation

Call SubscriptionClient first to discover available offers, then create a subscription definition referencing the chosen offer.

Alternative

SubscriptionsManagementClient

Azure Stack admin-side subscriptions management

Use for Azure Stack tenants; use SubscriptionDefinitionsClient for public Azure subscription provisioning.

Complementary

SqlManagementClient

Manage Azure SQL Database resources within freshly created subscriptions

Useful as a downstream step once subscriptions are provisioned and SQL workloads need configuration.

FAQs

Specific to using SubscriptionDefinitionsClient API through Jentic.

Why is there no official OpenAPI spec for SubscriptionDefinitionsClient?

Microsoft Azure publishes Swagger fragments for the Microsoft.Subscription resource provider but does not publish a consolidated, validated OpenAPI 3 spec for the subscription definitions surface. Jentic generates and maintains this spec so that AI agents and developers can call SubscriptionDefinitionsClient via structured tooling. It is validated against the live Azure Resource Manager API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the SubscriptionDefinitionsClient 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, Azure tokens are held in the vault and injected at call time so the agent never sees the raw bearer token.

Can I create an Azure subscription with this API?

Yes. PUT /providers/Microsoft.Subscription/subscriptionDefinitions/{subscriptionDefinitionName} creates a new subscription definition. The call is asynchronous and returns an operation id; poll GET /providers/Microsoft.Subscription/subscriptionOperations/{operationId} until status is Succeeded.

What are the rate limits for the SubscriptionDefinitionsClient?

Calls go through Azure Resource Manager, which throttles writes per subscription (typically 1,200 writes per hour). Subscription creation is intrinsically slow; do not retry the PUT call on timeout — instead poll the returned operation id.

How do I create an Azure subscription through Jentic?

Run pip install jentic, search Jentic for 'create an azure subscription definition', load the SubscriptionDefinitions_Create operation, and execute it with subscriptionDefinitionName and the body containing offerType and tenant id. Jentic returns the operation id; call the status operation to poll completion.

Does this API let me browse available offers?

No. Browse offers with SubscriptionClient (GET /offers and GET /delegatedProviders/{id}/offers). Once you have the offer identifier, pass it into a SubscriptionDefinitions_Create call here.