Front Door should be in Enabled state
Medium
Azure
General
frontdoors-front-door-enabled-state
Applies to
Microsoft.Network/frontDoors
What CGPulse checks
A resource passes this rule when enabledState must equal Enabled. Anything else is reported as a finding with the evaluated property value attached as evidence.
How to fix it
Enable the Front Door resource to resume processing requests. In Azure Portal: Front Door > Overview > set Enabled state to Enabled. See: https://learn.microsoft.com/en-us/azure/frontdoor/front-door-overview
CLI
az afd endpoint update --ids "{id}" --enabled-state EnabledTerraform
resource "azurerm_frontdoor" "{name}" {
name = "{name}"
resource_group_name = "{rg}"
# Front Door is enabled by default when the resource exists
# Set enforce_backend_pools_certificate_name_check as needed
routing_rule { }
backend_pool { }
frontend_endpoint { }
backend_pool_health_probe { }
backend_pool_load_balancing { }
}
Compliance frameworks
Is your environment compliant with this rule?
CGPulse checks it — and 621 others — against your Azure and AWS accounts with read-only access.
Related Azure rules
- Action Group should be enabled
- Activity Log Alert should be enabled
- AKS cluster logs should be sent to Log Analytics
- AKS cluster must enable RBAC
- AKS cluster must enable RBAC
- AKS cluster should be a private cluster
- AKS cluster should disable local accounts
- AKS cluster should enable Azure RBAC for Kubernetes