Microsoft Azure AppServicePlans API Client
Browse all Azure APIs★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeoauth229 EndpointsREST
For Agents
Provision and scale Azure App Service plans, list the Web Apps they host, and manage hybrid connections from an AI agent.
Use for: I need to provision a new App Service plan in the Premium V2 tier, Scale my App Service plan from 2 to 5 instances, List all Web Apps running on a specific App Service plan, Find all App Service plans in my subscription
Not supported: Does not deploy application code, manage Function App configuration, or operate App Service Environments — use for App Service plan (server farm) control-plane management only.
AppServicePlans API Client is the Azure Resource Manager API for managing App Service plans (server farms) — the compute units that host Web Apps, Function Apps, and API Apps. It covers plan creation, SKU and capacity changes, listing the apps that run on a plan, hybrid connection management, and per-plan capability inspection. Use this client to size and scale the underlying compute for App Service workloads.
Install Jentic One Beta
Connect the AppServicePlans API Client to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AppServicePlans 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.
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 AppServicePlans API Client API.
Provision App Service plans (server farms) at the desired SKU and capacity
List the Web Apps and Function Apps that run on a given plan
Scale a plan's worker count and SKU tier in place
Inspect per-plan capabilities and hybrid connection plan limits
Manage hybrid connections that bridge App Service plans to on-premises resources
List all App Service plans across a subscription or resource group
Use Cases
Patterns agents use AppServicePlans API Client API for, with concrete tasks.
★ Capacity Right-Sizing
Platform engineering teams running Web Apps on App Service need to keep plan capacity aligned with traffic. Listing apps per plan and inspecting current SKU and worker count gives the data needed to right-size; PATCH on the plan resource updates SKU and capacity in place without redeploying apps. Scale-out is near-instant once new workers are warm.
GET the plan, decide the new sku.name and sku.capacity, then PATCH the plan resource and verify the response includes the updated capacity.
App Inventory by Plan
Internal developer portals need to map which apps live on which compute plans for cost allocation and on-call routing. The /sites subresource on each plan returns the full list of Web Apps and Function Apps; combined with a subscription-wide plan list it produces a complete plan-to-app graph in two API calls per plan.
List plans in the subscription, then for each plan GET /serverfarms/{name}/sites and aggregate the results into a plan-to-apps map keyed by plan name.
Hybrid Connection Management
Apps that need to call on-prem services through Azure Hybrid Connections require those connections to be attached to the hosting App Service plan. The API exposes endpoints to list, retrieve, and remove hybrid connections per plan, plus the connection's keys and limits — enough to fully script the hybrid wiring inside a deployment pipeline.
GET the plan's hybrid connections, list keys for a specific relay, and use the keys to wire an on-prem listener to the App Service plan.
Agent-Driven Plan Provisioning via Jentic
An AI infra agent receiving a 'create a Premium plan in West Europe with 3 instances' instruction can use Jentic to find the plan creation operation, supply the SKU and worker count, and confirm provisioning. Jentic returns the schema and Azure ARM credentials are vaulted, so the agent never holds the subscription bearer token in context.
Search Jentic for 'create an App Service plan', execute the PUT on /serverfarms/{name} with sku.name=P1v2 and sku.capacity=3, and verify provisioningState is Succeeded.
Key Endpoints
29 endpoints — appserviceplans api client is the azure resource manager api for managing app service plans (server farms) — the compute units that host web apps, function apps, and api apps.
METHOD
PATH
DESCRIPTION
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Web/serverfarms
List all App Service plans in the subscription
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/serverfarms/{name}
Create or update an App Service plan
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/serverfarms/{name}/capabilities
List capabilities of a plan SKU
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/serverfarms/{name}/hybridConnectionPlanLimits/limit
Get hybrid connection plan limits
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/serverfarms/{name}/hybridConnectionNamespaces/{namespaceName}/relays/{relayName}/sites
List sites using a hybrid connection relay
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Web/serverfarms
List all App Service plans in the subscription
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/serverfarms/{name}
Create or update an App Service plan
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/serverfarms/{name}/capabilities
List capabilities of a plan SKU
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/serverfarms/{name}/hybridConnectionPlanLimits/limit
Get hybrid connection plan limits
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/serverfarms/{name}/hybridConnectionNamespaces/{namespaceName}/relays/{relayName}/sites
List sites using a hybrid connection relay
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Azure AD bearer tokens are stored in the Jentic vault. Agents receive a scoped session token only at call time; client secrets and refresh tokens never enter agent context.
Intent-based discovery
Agents search by intent ('scale my App Service plan') and Jentic returns the matching ARM operation with its parameter schema and api-version. The agent does not have to know whether the right call is PUT, PATCH, or POST.
Time to first call
Direct ARM integration: 1-2 days for AAD setup, ARM client wiring, and SKU enumeration. Through Jentic: under 30 minutes — search, load, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using AppServicePlans API Client API through Jentic.
What authentication does the AppServicePlans API Client use?
Azure Active Directory OAuth 2.0 bearer tokens scoped to https://management.azure.com/. Jentic stores the bearer token in its encrypted vault and issues a scoped session at call time.
Can I scale a plan's worker count with this API?
Yes. PATCH /serverfarms/{name} with the desired sku.capacity value (and sku.name if changing tier). Scale-out is propagated by Azure shortly after the call; the response reflects the new desired capacity, and subsequent GETs show the realised count.
What are the rate limits for the AppServicePlans API?
Calls go through Azure Resource Manager and follow ARM throttling — typically 12,000 reads and 1,200 writes per hour per subscription. Listing all plans across many resource groups is read-heavy; consider caching plan metadata when polling.
How do I list the Web Apps on a plan via Jentic?
Search Jentic for 'list Web Apps on App Service plan'. Jentic returns the schema for GET /serverfarms/{name}/sites; execute it with the plan name and resource group. The response includes site name, kind, and state for every app on the plan.
Is the AppServicePlans API free to call?
Management calls themselves do not have a per-request charge. App Service plan billing is based on SKU and instance count — Free, Shared, Basic, Standard, Premium, PremiumV2, PremiumV3, Isolated, and IsolatedV2 each have published hourly rates on the Azure App Service pricing page.
How do I check hybrid connection limits for a plan?
GET /serverfarms/{name}/hybridConnectionPlanLimits/limit returns the maximum number of hybrid connections the plan SKU permits. Free and Shared tiers do not support hybrid connections; Basic and above scale up to 25, 200, or higher depending on tier.
GET STARTED