canonical: https://jentic.com/apis/azure.com/frontdoormanagementclient # Microsoft Azure FrontDoorManagementClient 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. ## For AI 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. ## Scope Does not handle WAF rule authoring, regional load balancing, or DNS record creation - use for global Front Door edge management only. ## Capabilities - 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 - Purge specific content paths from the Front Door edge cache on demand - Check whether a Front Door resource name is available before creation ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: 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 | 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 | ## Key resources - **FrontDoors** — Create, list, get, update, and delete Front Door resources, plus validate custom domains and purge cached content. - **FrontendEndpoints** — List frontend endpoints on a Front Door and enable or disable HTTPS for each. - **CheckFrontDoorNameAvailability** — Validate that a proposed Front Door resource name is unique before creation. ## Why Jentic - **Setup:** Wiring Azure Front Door management by hand means registering an Azure AD app, exchanging OAuth 2.0 tokens against management.azure.com, building the Microsoft.Network/frontDoors ARM paths, and polling the Azure-AsyncOperation header on long-running provisioning rather than retrying the PUT. Through Jentic you install once, import FrontDoorManagementClient from the API Directory, store the Azure AD client credentials once, and your agent calls it. - **Permission scoping:** Front Door puts the subscription, resource group, and Front Door name in the URL path (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/frontDoors/{frontDoorName}/...), so a rule can pin your agent to one Front Door instance and its frontend endpoints. You choose the operations it may call, so destructive ones like deleting a Front Door or purging the edge cache are not included unless you add them. - **Credential handling:** Your Azure AD client credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time as a scoped bearer token. The client id and secret never enter the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'provision an Azure Front Door' or 'enable HTTPS on a frontend endpoint', and Jentic returns the matching FrontDoors or FrontendEndpoints operation with its input schema so the agent calls the right endpoint without browsing Microsoft Learn. ## Related APIs - **Azure CDN WebApplicationFirewallManagement** — Manages Web Application Firewall policies that can be attached to Front Door for L7 protection. - **Azure Traffic Manager** — DNS-based global traffic routing as an alternative to anycast Front Door routing. - **Azure DNS** — Manage DNS zones and records that point custom domains to Front Door frontend hosts. ## FAQ ### 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 with Jentic One, the self-hosted execution layer. ### 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. ### Can I limit what my agent is allowed to do with the Azure Front Door Management API? Yes. Because you run Jentic One yourself, your own rules decide which Front Door operations the agent can call and which Azure AD credentials it may use. Since the subscription, resource group, and Front Door name live in the request path, a rule can pin the agent to a single Front Door instance and its frontend endpoints. You also select the specific operations it may run, so destructive calls like deleting a Front Door or purging the edge cache are excluded unless you explicitly allow them.