For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
If your organization uses Azure Front Door, you can use HUMAN’s Azure Front Door Enforcer to protect against malicious behavior, which dictates how traffic should be handled per your organization’s standards. The Azure Enforcer combines Azure’s Front Door CDN caching functionality with the Azure Function App’s ability to run serverless code in the cloud.
The client sends a request to Azure Front Door.
Front Door sends the incoming request to the Function App origin group.
Reduces Function App invocations in the case of First Party requests.
If the Enforcer in the Function App passes the request, the Azure Function proxies the request back to the same Front Door domain.
If not found in the cache, the Front Door Rule Set sends the request to the origin server.
You can learn how to install the Azure Front Door Enforcer with this article.
This process only works if you do not have an existing Enforcer integrated with your application. If you do, see our article on manual installation.
Prerequisites
An Azure subscription with at least a Contributor role and the following providers:
Microsoft.Cdn (for Front Door)
Microsoft.Storage (for Storage Accounts)
Microsoft.Sites (for App Service)
Microsoft.Resources (for Resource Groups)
Microsoft.Web (for Function Apps)
A supported Azure app service plan on the same region you want to deploy your Enforcer to. The supported plans are:
Basic
Standard
Premium
Isolated
An Azure resource group within the relevant subscription.
Depending on your preferred deployment method, the following tools:
GNU Wget. See how to install with their documentation.
Create a Service Principal Client Secret
The Enforcer requires a client secret from a Service Principal. If you have an existing one, you can use it to create a secret. If you don’t have one, you can follow the steps to create a new one.
After you create the client secret, be sure to copy and save it in a secure place. You will not be shown the secret again.
Download the Enforcer configuration file
The Enforcer configuration file, enforcerConfig.json, has important information about your HUMAN account such as your Application ID or server token that the Enforcer uses to work with your application. If you don’t have one already, you need to download this file from the HUMAN console.
Navigate to Platform Settings > Configurations > Enforcers.
Click the Enforcer that you’re currently updating.
Click the download button to download enforcerConfig.json.
Save the file in a directory that you’ll remember, such as /deploy.
Run the Deploy Tool
You can run the Deploy Tool with either of the following methods:
button to download