Back to Azure Resource templates index <–
Azure Front Door is a global, scalable entry-point that uses the Microsoft global edge network to create fast, secure, and widely scalable web applications
Template Locations
Infrastructure As Code Advisor (Beta)
WAF-compliance
The WAF-compliance advisor validates templates based on the Well Architected Framework practices. Every day a GitHub Action updates the templates compliance data and lists the recomendations.
Sustainbility Advisor
The sustainability advisor is based on the Sogeti Cloud Reference Architecture with sustainble practices. These sustainble practices cover application code, cloud infrastructures and data. The global Sogeti community is continously evolving the sustainble practices and every day new and tuned are added. For cloud infrastructures the sustainble practices are automatically validated and reported below.
note: when 100% it can be that there is no sustainble practices yet for this Cloud infrastructure.
Online documentation
Template reference
Service description
Requirements
- Resource group must been created with a valid name and location.
Input values
- afdCustomName: Name of the Azure Front Door (Optional).
- defaultBackendAddress: FQDN of the first / default backend of this frontdoor
Output values
Azure CLI examples
After deployment of Azure Front Door you most likely need to configure additional backend and routing rules by using the CLI. The Yml snippit below can be used, which adds a second backend pool (API), loadbalancing and healthprobe and routing: Please Update FDNNAME and [FQDN.additionalbackend].
- name: Provisioning Frontdoor Additional backends and Rules
run: |
az extension add --name front-door
az network front-door probe create --resource-group $ --front-door-name $ --name "apiprobe" --path "/healthcheck" --interval 240 --probeMethod GET --protocol https --enabled Enabled
az network front-door load-balancing create --resource-group $ --front-door-name $ --name "apilb" --sample-size 5 --successful-samples-required 3 --additional-latency 40
az network front-door backend-pool create --name 'API' --probe "apiprobe" --load-balancing "apilb" --address '[FQDN.additionalbackend]' --http-port 80 --https-port 443 --priority 1 --weight 50 --front-door-name $ --resource-group $
az network front-door routing-rule create --name 'APIRouting' -f $ --frontend-endpoints "FDNNAME-azurefd-net" --backend-pool 'API' --patterns '/api/*' '/swagger/*' --route-type 'Forward' --accepted-protocols "Https" --forwarding-protocol "HttpsOnly" --resource-group $ \
Compliance Advisor details
Resource Health Result
| Message | ResourceType | Severity |
|---|---|---|
| Location for the resource should not be hardcoded, it should be parameterized and should refer from Resource Group's location i.e. [resourceGroup().location] | Microsoft.Network/frontdoors | 2 |
| Your current API Version i.e.2020-05-01 for the resource Microsoft.Network/frontdoors is outdatedconsider updating to new recent version available i.e. 2021-06-01 or 2020-07-01 | Microsoft.Network/frontdoors | 2 |
| To help other contributors understand the purpose of the resource, specify comments for each resource in the template | Microsoft.Network/frontdoors | 1 |
| It is recommended to parameterized your tag and make it as object type | Microsoft.Network/frontdoors | 1 |
TemplateParameterHealthResult
| Message | Severity |
|---|---|
| Define default values for parameters that aren't sensitive. By specifying a default value, it's easier to deploy the template, and users of your template see an example of an appropriate value i.e. afdCustomNameRead More | 1 |
| Define default values for parameters that aren't sensitive. By specifying a default value, it's easier to deploy the template, and users of your template see an example of an appropriate value i.e. defaultBackendAddressRead More | 1 |
TemplateVariableHealthResult
| Message | Severity |
|---|---|
| It is recommended to make your variable as camel case, wherever possible for e.g. environmentRead More | 1 |