You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/reliability/reliability-app-service.md
+6-5Lines changed: 6 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -170,15 +170,18 @@ Azure App Service is a single-region service. If the region becomes unavailable,
170
170
171
171
### Alternative multi-region solutions
172
172
173
-
If you need to use App Service in multiple regions, you need to deploy separate resources in each region. If you create an identical deployment in a secondary Azure region using a multi-region geography architecture, your application becomes less susceptible to a single-region disaster. When you follow this approach, you need to deploy your application to the instances in each region, and configure load balancing and failover policies. You also need to replicate your data across the regions so that you can recover your last application state.
173
+
If you need to use App Service in multiple regions, you need to deploy separate resources in each region. By creating identical deployments in multple Azure regions, your application becomes less susceptible to a single-region failure.
174
+
175
+
When you follow this approach, you need to deploy your application to the instances in each region, and configure load balancing and failover policies. You also need to replicate your data across the regions so that you can recover your last application state.
174
176
175
177
::: zone pivot="free-shared-basic,premium"
176
178
177
179
For example architectures that illustrates this approach, see:
178
180
179
181
-[Reference architecture: Highly available multi-region web application](/azure/architecture/web-apps/app-service/architectures/multi-region).
180
182
-[Multi-region App Service apps for disaster recovery](/azure/architecture/web-apps/guides/multi-region-app-service/multi-region-app-service)<!-- TODO Can't publish until this is ready -->
181
-
-[Tutorial: Create a highly available multi-region app in Azure App Service](/azure/app-service/tutorial-multi-region-app)
183
+
184
+
To follow along with a tutorial that creates a multi-region app, see [Tutorial: Create a highly available multi-region app in Azure App Service](/azure/app-service/tutorial-multi-region-app).
182
185
183
186
::: zone-end
184
187
@@ -192,9 +195,7 @@ For an example approach that illustrates this architecture, see [High availabili
192
195
193
196
When you use the Basic tier or higher, you can back up your App Service app to a file by using the [App Service backup and restore capabilities](../app-service/manage-backup.md). This feature can be useful if it's hard to redeploy your code, or if you store state on disk. For most solutions, you shouldn't rely on App Service backups, and you should use the other capabilities described in this article to support your resiliency requirements.
194
197
195
-
To learn more about backups and how they contribute to a resiliency strategy, see [new conceptual article].
196
-
197
-
If you need to use consistent configuration for multiple Azure App Service resources, consider deploying infrastructure as code by using a tool like [Bicep](/azure/azure-resource-manager/bicep/overview?tabs=bicep) or [Terraform](/azure/developer/terraform/overview).
198
+
To learn more about backups and how they contribute to a resiliency strategy, see [new conceptual article]. <!-- TODO We should omit this until we've got the conceptual article ready -->
0 commit comments