Build the foundational network infrastructure by deploying a resource group, virtual networks, subnets, and NAT gateways. These components serve as the backbone for all subsequent deployments, ensuring proper organization, security, and scalability.
Configure virtual network peering between vNet-West and vNet-East, then deploy Azure Bastion to provide secure remote access to your virtual machines without exposing them to the public internet.
Deploy and configure two public Azure Load Balancers — one in West US and one in East US — to distribute incoming traffic across virtual machines in each region for high availability and fault tolerance.
Deploy and configure two West US virtual machines serving as web servers for the distributed application. Install IIS remotely via PowerShell and add them to the LB-West backend pool.
Deploy and configure two East US virtual machines serving as web servers for the distributed application. Install IIS remotely via PowerShell and add them to the LB-East backend pool.
Configure static private IP addresses across all VMs, then test the load balancing functionality of both LB-West and LB-East — including simulating VM failures to confirm traffic failover.
Deploy and configure Azure Storage Accounts in both regions. Each account will contain a blob container for website images, later integrated with Azure Front Door CDN. Configure object replication between regions for automatic content synchronization.
Deploy Azure Front Door CDN to optimize image delivery for the web application. Add a secondary origin for failover protection and configure a custom domain for the CDN endpoint.
Deploy Azure Traffic Manager to manage global traffic distribution. Create a Traffic Manager profile with performance-based routing, add regional endpoints, and integrate a custom DNS name for branded access.