Microsoft Azure Provider API Client

Name: Provider API Client API
Brand: Provider API Client
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeoauth23 Endpoints

Install Jentic One Beta

Connect the Provider API Client to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Provider API Client, 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.

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 | sh

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 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 Provider API Client API.

List the operations available on the Microsoft.Web provider

List runtime stacks supported by Azure App Service across all regions

List the runtime stacks available within a specific subscription

GET STARTED

Start building with Provider API Client API

Explore with Jentic

View OpenAPI Document

For Agents

Look up the operations and runtime stacks supported by the Microsoft.Web provider so an agent can pick a valid App Service stack version before provisioning.

Use for: List the runtime stacks supported by Azure App Service, Find which Node.js versions are available on Azure App Service, Check whether a specific Python runtime is supported in my subscription, List all Microsoft.Web provider operations

Not supported: Does not provision App Service plans, deploy code, or change stack versions on existing apps - use for read-only Microsoft.Web provider operation and available-stack discovery only.

Use Cases

Patterns agents use Provider API Client API for, with concrete tasks.

★ Stack version validation before provisioning

Before provisioning a Web App, an automation flow needs to confirm the desired runtime stack version is still supported by Azure App Service. The API returns the catalogue of supported stacks and minor versions so the agent can pick a valid value or fail fast with a clear error rather than failing during provisioning.

List the available stacks filtered by osTypeSelected=Linux and confirm whether 'python|3.11' is supported

Subscription-scoped stack catalogue

Some customers see a different stack catalogue depending on their subscription's region availability or feature flags. The subscription-scoped listing returns the stacks visible to a specific subscription so an internal portal can show only what the user is actually allowed to deploy.

List available stacks for subscription X and return the supported Java versions visible to that subscription

Operation discovery for Microsoft.Web

Tooling that wraps Azure RBAC or audit logs needs the catalogue of Microsoft.Web provider operations to produce role definitions or readable audit lines. The operations listing returns the canonical operation names with their display strings.

List all Microsoft.Web provider operations and filter for those involving 'sites/write'

Agent-driven stack selection

An AI agent provisioning a Web App needs to translate a user's intent (such as 'host a Node.js 20 app') into a concrete stack version. The agent calls the available stacks endpoint, picks the matching runtime, and then hands the value to the App Service create operation. Jentic isolates the AAD secret so the agent only sees scoped bearer tokens.

Resolve 'Node.js 20 LTS on Linux' to a concrete Microsoft.Web stack version that is currently available in subscription X

Key Endpoints

3 endpoints — jentic publishes the only available openapi specification for provider api client, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/providers/Microsoft.Web/availableStacks

List all available App Service stacks

GET

/providers/Microsoft.Web/operations

List Microsoft.Web provider operations

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Web/availableStacks

List available stacks visible to a subscription

GET

/providers/Microsoft.Web/availableStacks

List all available App Service stacks

GET

/providers/Microsoft.Web/operations

List Microsoft.Web provider operations

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Web/availableStacks

List available stacks visible to a subscription

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Azure AD OAuth 2.0 credential is stored once, encrypted, by your own Jentic One instance and a scoped bearer token is injected at execution time. The client secret never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list azure app service available stacks' or 'find supported node.js versions', and Jentic returns the matching listing operation with its input schema so the agent supplies the subscription id and optional OS filter without browsing the reference docs.

Time to first call

FAQs

Specific to using Provider API Client API through Jentic.

Why is there no official OpenAPI spec for Provider API Client?

Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Provider API Client via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Microsoft.Web Provider API use?

The API runs through Azure Resource Manager and uses OAuth 2.0 bearer tokens issued by Azure Active Directory under the azure_auth scheme with the user_impersonation scope. Through Jentic, the AAD client secret is held in the encrypted vault and a short-lived access token is supplied at execute time so the secret never appears in the agent's context.

Can I filter the available stacks by operating system?

Yes. GET /providers/Microsoft.Web/availableStacks accepts an osTypeSelected query parameter (Linux or Windows) so the response includes only the stacks for the chosen OS. The same query parameter is supported on the subscription-scoped variant.

What are the rate limits for the Microsoft.Web Provider API?

Azure Resource Manager applies subscription-level read throttles (around 12,000 reads per hour per region per subscription) and returns 429 with a Retry-After header when exceeded. These are read-only listing endpoints, so the read budget is the only limit that applies.

How do I list available stacks through Jentic?

Search Jentic for 'list azure app service available stacks', load the schema for GET /subscriptions/{subscriptionId}/providers/Microsoft.Web/availableStacks, then execute with the subscriptionId and an optional osTypeSelected. The pip install jentic Python SDK uses the async search, load, execute pattern.

Is the Microsoft.Web Provider API free?

There is no per-call charge for the management API itself; these listing endpoints are read-only metadata calls and do not provision any billable resources. You pay for App Service plans and apps once you provision them via the App Service APIs.

Can I limit what my agent is allowed to do with the Provider API Client?

Yes. Because you run Jentic One yourself, you decide which operations the agent may call, so you can allow only the read-only listing calls such as GET /providers/Microsoft.Web/availableStacks and GET /providers/Microsoft.Web/operations and nothing else. The subscription id is carried in the URL path and the OS filter is passed as a query parameter, so you can hold the agent to a single subscription and to listing available stacks and provider operations. Your Azure AD credential stays in your own instance and a scoped bearer token is injected only at execution time, so the agent never sees the client secret.