Front Door should have HTTPS enabled on all frontend endpoints

High Azure General frontdoors-front-door-https-enabled

Applies to

Microsoft.Network/frontDoors

What CGPulse checks

A resource passes this rule when frontendEndpoints.allHttpsEnabled must equal true. Anything else is reported as a finding with the evaluated property value attached as evidence.

How to fix it

Enable HTTPS on all endpoints to encrypt user traffic in transit. In Azure Portal: Front Door > Frontend hosts > enable HTTPS with a valid TLS certificate. See: https://learn.microsoft.com/en-us/azure/frontdoor/front-door-custom-domain-https

CLI

az afd endpoint update --ids "{id}" --enabled-state Enabled

Terraform

resource "azurerm_frontdoor" "{name}" {
  name                = "{name}"
  resource_group_name = "{rg}"
  frontend_endpoint {
    name      = "{name}-frontend"
    host_name = "{name}.azurefd.net"
  }
  # Enable HTTPS on custom domains via azurerm_frontdoor_custom_https_configuration
}
resource "azurerm_frontdoor_custom_https_configuration" "{name}" {
  frontend_endpoint_id              = azurerm_frontdoor.{name}.frontend_endpoints["{name}-frontend"]
  custom_https_provisioning_enabled = true
  custom_https_configuration {
    certificate_source = "FrontDoor"
  }
}

Compliance frameworks

Cloud Security BaselineDP-3

Vendor documentation

Is your environment compliant with this rule?

CGPulse checks it — and 621 others — against your Azure and AWS accounts with read-only access.

Run a free scan