Microsoft Azure FrontDoorManagementClient

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.