
Phase 3 - Azure Front Door Standard with Custom Domain & Managed TLS
This guide walks through setting up Azure Front Door (AFD) to front an Azure App Service using a custom subdomain and automated SSL/TLS certificates. 📋 Prerequisites An existing Azure App Service (e.g., app-sea-3446.azurewebsites.net ). A domain managed in a DNS provider (e.g., AWS Route53 ). Azure CLI installed and authenticated. Architure 🏗️ Phase 1: Infrastructure Setup First, we create the Front Door profile, endpoint, and origin group. # Variables RG = "rg-afd-lab" PROFILE_NAME = "afd-profile" ENDPOINT_NAME = "afd-endpoint" ORIGIN_GROUP = "app-origin-group" APP_HOSTNAME = "app-sea-3446.azurewebsites.net" # 1. Create Profile az afd profile create -g $RG --profile-name $PROFILE_NAME --sku Standard_AzureFrontDoor # 2. Create Endpoint az afd endpoint create -g $RG --profile-name $PROFILE_NAME --endpoint-name $ENDPOINT_NAME --enabled-state Enabled # 3. Create Origin Group with Health Probes az afd origin-group create -g $RG --profile-name $PROFILE_NAME --origin-group-name $ORIGIN_GROUP
Continue reading on Dev.to
Opens in a new tab



