
Phase 2 β Global Routing with Azure Front Door (Standard) Using Azure CLI
In Phase 1, we deployed regional App Services. In Phase 2, we elevate the architecture: π Add a global entry point π Terminate TLS at the edge π Route traffic intelligently to regional backends All using Azure CLI in Cloud Shell . π§ Architecture Goal We want this flow: User β Azure Front Door (Global Edge) β Origin Group β App Service (SEA) More details Even with a single region (quota constraints), this gives us: Global Anycast entry Edge TLS termination Health-probe-based routing Future-ready multi-region expansion π Phase 2 Resources Inside one Resource Group: Azure Front Door Profile (Standard) Endpoint Origin Group Origin (App Service) Route App Service (SEA region) π Step 1 β Create Front Door Profile RG = rg-afd-lab PROFILE_NAME = afd-profile ENDPOINT_NAME = afd-endpoint az afd profile create \ --resource-group $RG \ --profile-name $PROFILE_NAME \ --sku Standard_AzureFrontDoor π Step 2 β Create Endpoint az afd endpoint create \ --resource-group $RG \ --profile-name $PROFILE_NAME
Continue reading on Dev.to Tutorial
Opens in a new tab



