Skip to content

Commit ff7ce48

Browse files
Update articles/operational-excellence/relocation-static-web-apps.md
Co-authored-by: Craig Shoemaker <[email protected]>
1 parent 6d436ba commit ff7ce48

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/operational-excellence/relocation-static-web-apps.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ Review the following prerequisites before you prepare for the relocation.
5353

5454
## Downtime
5555

56-
The relocation of an Azure Static Web site introduces downtime to your application. The downtime is affected by which high availability pattern you have implemented for your Azure Static Web site. General patterns are
56+
The relocation of an Azure Static Web site introduces downtime to your application. The downtime is affected by which high availability pattern you have implemented for your Azure Static Web site. General patterns are:
5757
- Cold Standby - the workload data is backed up regularly based on the requirements of the workload. In case of a disaster, the workload is redeployed in a new Azure region and the data is restored.
5858
- Warm Standby - the workload is deployed in the BCDR region and the data is replicated asynchronously or synchronously. In the event of a disaster, the deployment in the DR region is scaled up and out.
5959
- [Multi-region](https://learn.microsoft.com/en-us/azure/architecture/web-apps/app-service/architectures/multi-region) - the workload is deployed in both regions and the data is replicated synchronously. Both regions have a writable copy of the data. The implementation can be Active/Passive or Active/Active.

0 commit comments

Comments
 (0)