Phase 1 - Building a Multi-Region Backend on Azure (Before Azure Front Door)

When designing global applications, the first step isn’t configuring global routing. It’s building healthy, regionally distributed backends . In this tutorial, we’ll deploy: Two Azure App Services In two different regions With region-specific responses Fully validated and tested This sets the foundation for later integrating Azure Front Door . 🏗 Architecture Overview We will deploy: Resource Group: rg-afd-lab Region 1: East US 2 Region 2: Southeast Asia Linux App Service Plans (B1) Node.js web apps returning region-specific messages Architecture Diagram (PlantUML) At this stage, traffic hits each regional app directly via *.azurewebsites.net . 🚀 Step 1: Create Resource Group RG = "rg-afd-lab" LOCATION1 = "eastus2" LOCATION2 = "southeastasia" az group create \ --name $RG \ --location $LOCATION1 🧱 Step 2: Create App Service Plans SUFFIX = $RANDOM PLAN1 = "plan-eastus2- $SUFFIX " PLAN2 = "plan-sea- $SUFFIX " az appservice plan create \ --name $PLAN1 \ --resource-group $RG \ --location $LO