Skip to main content

Front Door configuration

This guidance applies to non-production and production environments where relevant. Production approvals and readiness checks remain part of Path to Live.

Purpose

Configuration

We use Azure Front Door as our entry point into the HMCTS estate.

CFT

Configuration is located in azure-platform-terraform. A minimal configuration for production would be:

{
    product                     = "product"
    name                        = "app-name"
    custom_domain               = "your-app.service.gov.uk"
    backend_domain              = ["firewall-prod-int-palo-cftprod.uksouth.cloudapp.azure.com"]
    dns_zone_name               = "your-app.service.gov.uk"
}

SDS

Configuration is located in sds-azure-platform. A minimal configuration for production would be:

{
    name             = "app-name"
    custom_domain    = "your-app.service.gov.uk"
    backend_domain   = ["firewall-prod-int-palo-sdsprod.uksouth.cloudapp.azure.com"]
    dns_zone_name    = "your-app.service.gov.uk"
}

For other options, look at what existing applications use in the same file.

Before sending a pull request to this repo ensure that:

  • your DNS pull request has been merged,
  • your TLS certificate has been stored in vault, if you aren’t sure then just create the pull request, the build will fail if it isn’t present.

Once the above is complete, send a pull request with your configuration change, you can ask for review in #platops-code-review.

Next step in Creating a New Component: Deploy and validate your first build

This page was last reviewed on 3 December 2025. It needs to be reviewed again on 3 June 2026 by the page owner platops-build-notices .