Microsoft Azure AppServiceEnvironments API Client

Name: AppServiceEnvironments API Client API
Brand: AppServiceEnvironments API Client
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeoauth242 Endpoints

Install Jentic One Beta

Connect the AppServiceEnvironments API Client to your agent

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

GET STARTED

Start building with AppServiceEnvironments API Client API

Explore with Jentic

View OpenAPI Document

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.

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.

Use Cases

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.

Key Endpoints

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

GET

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

List all App Service Environments in the subscription

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/hostingEnvironments/{name}

Create or update an ASE

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/hostingEnvironments/{name}/changeVirtualNetwork

Rebind an ASE to a different VNet or subnet

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/hostingEnvironments/{name}/capacities/compute

Retrieve compute capacity for an ASE

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/hostingEnvironments/{name}/diagnostics

List diagnostics for an ASE

GET

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

List all App Service Environments in the subscription

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/hostingEnvironments/{name}

Create or update an ASE

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/hostingEnvironments/{name}/changeVirtualNetwork

Rebind an ASE to a different VNet or subnet

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/hostingEnvironments/{name}/capacities/compute

Retrieve compute capacity for an ASE

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/hostingEnvironments/{name}/diagnostics

Why Jentic?

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

Credential isolation

Your Azure AD service principal credential is stored once, encrypted, by your own Jentic One instance and exchanged for a short-lived bearer token at execution time. The secret never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'provision an App Service Environment' or 'get App Service Environment diagnostics', and Jentic returns the matching operation with its input schema so the agent supplies the subnet id and environment name without navigating the hostingEnvironments path layout.

Time to first call

FAQs

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 securely stores 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.

Can I limit what my agent is allowed to do with the Microsoft Azure App Service Environments API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. App Service Environments are addressed by path parameters (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/hostingEnvironments/{name}/...), so you can pin the agent to a single subscription, resource group, and named environment. You also choose the operations it may call, so sensitive ones like rebinding the virtual network via changeVirtualNetwork or scaling a worker pool with PATCH workerPools are excluded unless you add them, while read-only calls such as listing environments or reading compute capacity stay available.