| description | page_type | products | urlFragment | languages | ||||
|---|---|---|---|---|---|---|---|---|
This template allows you to create a secure, highly available, multi-region end to end solution with two web apps in different regions behind Azure Front Door |
sample |
|
webapp-multi-region-front-door |
|
This template deploys a identical web app infrastructure in two separate regions as well as an Azure Front Door to direct traffic. By default, one web app is set to the primary and the other is set to the secondary and all traffic is routed to the primary. In the case of a region outage in the primary region, Front Door will direct all traffic to the secondary region.
The primary region will be set to the region you select for your resource group. The secondary region will be set to East US. For a true fault tolerant deployment, don't use East US as the location for your resource group and instead use West US as those regions form one of the regional pairs assigned by Azure.
If you are new to Azure App Service, see:
If you are new to template deployment, see:
Azure Resource Manager documentation
Tags: appServices, Microsoft.Network/virtualNetworks, Microsoft.Web/serverfarms, Microsoft.Web/sites, Microsoft.Web/sites/config, Microsoft.Web/sites/hostNameBindings, Microsoft.Web/sites/networkConfig, Microsoft.Network/privateEndpoints, Microsoft.Network/privateDnsZones, Microsoft.Network/privateDnsZones/virtualNetworkLinks, Microsoft.Network/privateEndpoints/privateDnsZoneGroups