FrontDoorManagementClient

Name: FrontDoorManagementClient API
Brand: Azure Front Door Management
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureNetworkingoauth213 EndpointsREST

For Agents

Manage Azure Front Door global load balancers, frontend endpoints, and HTTPS settings via Azure Resource Manager. Validate custom domains, enable or disable HTTPS, and purge cached content.

Connect the FrontDoorManagementClient to your agent

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

Provision and update Azure Front Door instances scoped to a resource group

List Front Doors across a subscription or filter by resource group

Enable or disable HTTPS on individual frontend endpoints

Validate a custom domain before binding it to a Front Door

GET STARTED

Start building with FrontDoorManagementClient API

Explore with Jentic

View OpenAPI Document

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

Jentic publishes the only available OpenAPI specification for FrontDoorManagementClient, keeping it validated and agent-ready. The Azure Front Door Management API lets agents provision and manage Azure Front Door instances through Azure Resource Manager, including frontend endpoints, routing rules, backend pools, and HTTPS configuration. It supports global HTTP/HTTPS load balancing, custom domain validation, and on-demand cache purging across the Front Door edge network. Authentication uses Azure AD OAuth2 against the management.azure.com control plane.

Use Cases

Patterns agents use FrontDoorManagementClient API for, with concrete tasks.

★ Global HTTP load balancing for a multi-region app

Provision an Azure Front Door to route user traffic to the lowest-latency healthy backend across regions. The API creates the Front Door resource with backend pools, health probes, and routing rules under Microsoft.Network/frontDoors, returning the anycast frontend hostname for DNS configuration. Suitable for production web workloads needing global failover and TLS termination at the edge.

Create a Front Door named 'shop-prod' in resource group 'edge-rg' with two backends and a default routing rule, then return the frontend host name.

Custom domain onboarding with HTTPS

Bind a custom domain such as cdn.example.com to a Front Door frontend endpoint and enable Azure-managed HTTPS. The API first validates the domain via FrontDoors_ValidateCustomDomain, then enables TLS through FrontendEndpoints_EnableHttps. Reduces manual cert provisioning to a single API call sequence.

Validate 'cdn.example.com' against Front Door 'shop-prod' and enable HTTPS using an Azure-managed certificate on the matching frontend endpoint.

Cache invalidation after deploys

Trigger a targeted cache purge on a Front Door instance after deploying new static assets. The Endpoints_PurgeContent operation accepts a list of content paths and clears them from the edge cache without touching unrelated assets. Useful in CI/CD pipelines that need cached content to reflect new releases within seconds.

Purge the paths /index.html and /static/* from Front Door 'shop-prod' in resource group 'edge-rg'.

AI agent edge configuration through Jentic

An infrastructure agent uses Jentic to discover Front Door operations, load their input schemas, and execute provisioning, HTTPS toggling, or cache purges without holding raw Azure credentials. Jentic resolves the agent's natural-language intent to the correct ARM operation and injects a scoped bearer token at execution time.

Use Jentic to search for 'enable HTTPS on Azure Front Door', load the FrontendEndpoints_EnableHttps schema, and execute it for endpoint 'cdn-example-com' on Front Door 'shop-prod'.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/frontDoors/{frontDoorName}

Create or update a Front Door resource

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Network/frontDoors

List all Front Doors in the subscription

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/frontDoors/{frontDoorName}/frontendEndpoints/{frontendEndpointName}/enableHttps

Enable HTTPS on a frontend endpoint

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/frontDoors/{frontDoorName}/purge

Purge content paths from the Front Door cache

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/frontDoors/{frontDoorName}/validateCustomDomain

Validate a custom domain before binding

POST

/providers/Microsoft.Network/checkFrontDoorNameAvailability

Check if a Front Door name is available

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/frontDoors/{frontDoorName}

Create or update a Front Door resource

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Network/frontDoors

List all Front Doors in the subscription

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/frontDoors/{frontDoorName}/frontendEndpoints/{frontendEndpointName}/enableHttps

Enable HTTPS on a frontend endpoint

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/frontDoors/{frontDoorName}/purge

Purge content paths from the Front Door cache

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/frontDoors/{frontDoorName}/validateCustomDomain

Why though Jentic?

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

Credential isolation

Azure service principal credentials are stored encrypted in the Jentic vault. Agents receive a scoped Azure AD bearer token at execution time — the client ID and secret never enter the agent context.

Intent-based discovery

Agents search Jentic with intents like 'provision an Azure Front Door' or 'purge edge cache', and Jentic returns the matching FrontDoorManagementClient operation with its full input schema so the agent can call the right ARM endpoint without browsing Microsoft Learn.

Time to first call

Direct integration with Azure Resource Manager: 1-3 days for AAD app registration, token exchange, and async operation polling. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Azure CDN WebApplicationFirewallManagement

Manages Web Application Firewall policies that can be attached to Front Door for L7 protection.

Choose this when the agent needs to create or update WAF rules to apply on top of a Front Door deployment.

Alternative

Azure Traffic Manager

DNS-based global traffic routing as an alternative to anycast Front Door routing.

Use Traffic Manager when the agent needs DNS-level geographic routing across endpoints rather than HTTP/HTTPS edge load balancing.

Complementary

Azure DNS

Manage DNS zones and records that point custom domains to Front Door frontend hosts.

Pair with Front Door when the agent needs to create the CNAME or alias record before validating a custom domain.

FAQs

Specific to using FrontDoorManagementClient API through Jentic.

Why is there no official OpenAPI spec for FrontDoorManagementClient?

Microsoft Azure does not publish a stand-alone OpenAPI specification for the Front Door Management API. Jentic generates and maintains this spec from Azure Resource Manager metadata so that AI agents and developers can call FrontDoorManagementClient via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Azure Front Door Management API use?

The API uses Azure Active Directory OAuth2 against management.azure.com, declared as the azure_auth security scheme in the spec. Through Jentic, your Azure service principal credentials sit in the encrypted vault and are exchanged for a scoped bearer token at execution time, so the agent never sees the client secret.

Can I enable HTTPS on a custom domain through this API?

Yes. Call POST on /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/frontDoors/{frontDoorName}/frontendEndpoints/{frontendEndpointName}/enableHttps with either an Azure-managed certificate option or a Key Vault certificate reference. Validate the custom domain first via the validateCustomDomain endpoint.

What are the rate limits for the Front Door Management API?

Azure Resource Manager applies subscription-level read and write throttles, typically around 12,000 reads and 1,200 writes per hour per subscription. Front Door provisioning operations are long-running and return 202 with an Azure-AsyncOperation header — agents should poll that URL rather than retry the original PUT.

How do I purge the Front Door cache through Jentic?

Run jentic.search('purge front door cache'), load the Endpoints_PurgeContent operation schema, and execute it with the subscription ID, resource group, Front Door name, and a contentPaths array such as ['/index.html', '/static/*']. The operation completes asynchronously.

Can this API check if a Front Door name is available before I create one?

Yes. POST /providers/Microsoft.Network/checkFrontDoorNameAvailability with the candidate name and resource type returns whether the name is globally unique. There is also a subscription-scoped variant at /subscriptions/{subscriptionId}/providers/Microsoft.Network/checkFrontDoorNameAvailability.