For Agents
Provision and manage Azure App Service Environments — single-tenant isolated App Service deployments inside a VNet — including capacity, scaling, and diagnostics, from an AI agent.
Get started with AppServiceEnvironments API Client in minutes using your preferred integration method.
# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
"jentic": {
"url": "https://api.jentic.com/mcp",
"auth": "oauth"
}
}
# Then ask your agent:
"provision an Azure App Service Environment"
# → Jentic returns the GET /events tool with parameter schema, agent executes.What an agent can do with AppServiceEnvironments API Client API.
Provision App Service Environment v2 instances inside an Azure virtual network
Inspect compute and virtual IP capacity for sizing and quota planning
Rebind an ASE to a different virtual network or subnet
Scale multi-role pools and worker pools that back hosted App Service plans
GET STARTED
Use for: I need to provision a new App Service Environment in West Europe, Scale the worker pool of my ASE to support more isolated App Service plans, List all App Service Environments in my subscription, Retrieve the virtual IP capacity for an existing ASE
Not supported: Does not deploy application code, manage non-isolated App Service workloads, or configure VNet routing tables — use for App Service Environment v2 control-plane management only.
Jentic publishes the only available OpenAPI document for AppServiceEnvironments API Client, keeping it validated and agent-ready.
AppServiceEnvironments API Client is the Azure Resource Manager API for App Service Environment v2 (ASE) — Azure's single-tenant, isolated deployment of App Service that runs inside a customer virtual network. It covers ASE provisioning, capacity and virtual IP inspection, virtual network rebinding, diagnostics, multi-role pool scaling, worker pool sizing, metric retrieval, and operation tracking. Use this client to manage the dedicated infrastructure that hosts isolated App Service apps.
Retrieve diagnostic information for an ASE for troubleshooting
List long-running ARM operations performed against an ASE
Patterns agents use AppServiceEnvironments API Client API for, with concrete tasks.
★ Provisioning Compliance-Grade Hosting
Regulated industries (finance, healthcare, government) need App Service workloads that run inside their own VNet with no shared front-end. The API provisions an ASE, attaches it to a designated subnet, and sets the internal load balancer mode — all under ARM with role-based access control. Provisioning is a long-running operation taking up to several hours, tracked through the operations subresource.
PUT a hostingEnvironments resource with the target subnet ID and internal load balancer mode, then poll the long-running operation until provisioningState is Succeeded.
Capacity Planning and Scaling
Platform engineering teams managing ASEs need real-time capacity data to decide when to scale worker pools. The compute and virtual IP capacity endpoints return available cores and IPs; combining them with worker pool size lets ops decide when to add Isolated SKU workers. Scaling is exposed as a PATCH on workerPools/{workerPoolName}.
GET capacities/compute and capacities/virtualip, decide whether to scale, then PATCH workerPools/{workerPoolName} with the new workerCount.
VNet Rebinding for Network Migration
Network teams migrating an ASE to a redesigned VNet structure use the changeVirtualNetwork action to rebind without recreating the ASE. The operation reassigns the ASE to the new subnet, preserving hosted apps and certificates. It is a long-running operation, surfaced through the operations subresource.
POST to /hostingEnvironments/{name}/changeVirtualNetwork with the new subnet ID, then poll operations/{operationId} until completion.
Agent-Driven ASE Diagnostics via Jentic
An ops AI agent investigating App Service availability incidents can pull ASE diagnostics through Jentic without holding the Azure subscription credentials. Jentic returns the diagnostic schema, the agent executes against the named ASE, and the returned diagnostic objects feed an incident summary or runbook automation.
Search Jentic for 'get App Service Environment diagnostics', execute the call against the target ASE name, and summarise any items where the diagnostic level indicates an issue.
42 endpoints — appserviceenvironments api client is the azure resource manager api for app service environment v2 (ase) — azure's single-tenant, isolated deployment of app service that runs inside a customer virtual network.
METHOD
PATH
DESCRIPTION
/subscriptions/{subscriptionId}/providers/Microsoft.Web/hostingEnvironments
List all App Service Environments in the subscription
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/hostingEnvironments/{name}
Create or update an ASE
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/hostingEnvironments/{name}/changeVirtualNetwork
Rebind an ASE to a different VNet or subnet
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/hostingEnvironments/{name}/capacities/compute
Retrieve compute capacity for an ASE
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/hostingEnvironments/{name}/diagnostics
List diagnostics for an ASE
/subscriptions/{subscriptionId}/providers/Microsoft.Web/hostingEnvironments
List all App Service Environments in the subscription
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/hostingEnvironments/{name}
Create or update an ASE
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/hostingEnvironments/{name}/changeVirtualNetwork
Rebind an ASE to a different VNet or subnet
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/hostingEnvironments/{name}/capacities/compute
Retrieve compute capacity for an ASE
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/hostingEnvironments/{name}/diagnostics
Three things that make agents converge on Jentic-routed access.
Credential isolation
Azure AD bearer tokens for management.azure.com are vaulted by Jentic. Agents receive scoped, short-lived session tokens at call time and never see client secrets or refresh tokens.
Intent-based discovery
Agents search by intent ('provision an App Service Environment') and Jentic returns the matching ARM operation with its parameter schema and api-version, so agents do not have to navigate the 42 endpoints across hostingEnvironments, capacities, worker pools, diagnostics, and operations.
Time to first call
Direct ARM integration: 2-4 days for AAD setup, ARM long-running operation handling, and capacity polling logic. Through Jentic: under 1 hour — search, load, execute, poll.
Alternatives and complements available in the Jentic catalogue.
AppServicePlans API Client
Manage the App Service plans hosted inside an ASE
Use App Service Plans when sizing the SKU for plans that run within the ASE.
Web Apps API Client
Deploy and manage Web Apps that live inside the ASE
Use Web Apps once the ASE and plan are provisioned to deploy the actual application code.
Monitor Management Client
Configure metric alerts and diagnostic settings on ASE resources
Pair when the agent needs to set up alerting on ASE health and worker pool capacity.
Specific to using AppServiceEnvironments API Client API through Jentic.
What authentication does the AppServiceEnvironments API Client use?
Azure Active Directory OAuth 2.0 bearer tokens scoped to https://management.azure.com/. Jentic vaults the bearer token and supplies a scoped session at call time, so the agent never holds the underlying client secret.
Can I provision a new ASE through this API?
Yes. PUT to /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/hostingEnvironments/{name} with the virtualNetwork.id and internalLoadBalancingMode in the properties block. ASE provisioning is long-running — poll the resource's provisioningState until it reaches Succeeded, which can take several hours.
What are the rate limits for the AppServiceEnvironments API?
Calls are bound by Azure Resource Manager throttling — generally 12,000 reads and 1,200 writes per hour per subscription. Long-running provisioning operations consume a single write but generate many polling reads; budget those when designing automation.
How do I scale the worker pool of an ASE through Jentic?
Search Jentic for 'scale ASE worker pool'. Jentic returns the schema for PATCH /hostingEnvironments/{name}/workerPools/{workerPoolName}; execute with the new workerCount value. The change is asynchronous and reflected in subsequent GETs on the worker pool resource.
Can I retrieve diagnostic data for an ASE?
Yes. GET /hostingEnvironments/{name}/diagnostics returns the diagnostic items available for the ASE; GET /hostingEnvironments/{name}/diagnostics/{diagnosticsName} returns the detail for a specific diagnostic item including findings and recommendations.
How do I move an ASE to a new virtual network?
POST to /hostingEnvironments/{name}/changeVirtualNetwork with the new subnet's resource ID. This is a long-running operation; poll the operations subresource to track progress and confirm completion.
List diagnostics for an ASE