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
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -330,7 +330,7 @@ Steps to create an active-active architecture for your web app in App Service ar
330
330
331
331
1. Create an Azure Front Door profile with:
332
332
- An endpoint.
333
-
- Two origins inside the same origin group, each with a priority of 1. The equal priority tells Azure Front Door to route traffic to both regions equally (thus active-active).
333
+
- Two origin groups, each with a priority of 1. The equal priority tells Azure Front Door to route traffic to both regions equally (thus active-active).
334
334
- A route.
335
335
336
336
1.[Limit network traffic to the web apps only from the Azure Front Door instance](../app-service/app-service-ip-restrictions.md#restrict-access-to-a-specific-azure-front-door-instance).
@@ -339,7 +339,7 @@ Steps to create an active-active architecture for your web app in App Service ar
339
339
340
340
1. Deploy code to both the web apps with [continuous deployment](../app-service/deploy-continuous-deployment.md).
341
341
342
-
[Tutorial: Create a highly available multi-region app in Azure App Service](../app-service/tutorial-multi-region-app.md) shows you how to set up an *active-passive* architecture. The same steps with minimal changes (setting priority to “1” for both origin groups in Azure Front Door) give you an *active-active* architecture.
342
+
[Tutorial: Create a highly available multi-region app in Azure App Service](../app-service/tutorial-multi-region-app.md) shows you how to set up an *active-passive* architecture. The same steps with minimal changes (setting priority to “1” for both origins in the origin group in Azure Front Door) give you an active-active architecture.
343
343
344
344
345
345
##### Active-passive architecture
@@ -386,7 +386,8 @@ Steps to create an active-passive architecture for your web app in App Service a
386
386
1. Create two instances of your web app, with one in each App Service plan.
387
387
1. Create an Azure Front Door profile with:
388
388
- An endpoint.
389
-
- Two origins inside the same origin group, one with a priority of 1 and the other with a priority of 2.
389
+
- An origin group with a priority of 1 for the primary region.
390
+
- A second origin group with a priority of 2 for the secondary region. The difference in priority tells Azure Front Door to prefer the primary region when it's online (thus active-passive).
390
391
- A route.
391
392
1.[Limit network traffic to the web apps only from the Azure Front Door instance](../app-service/app-service-ip-restrictions.md#restrict-access-to-a-specific-azure-front-door-instance).
392
393
1. Setup and configure all other back-end Azure service, such as databases, storage accounts, and authentication providers.
0 commit comments