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/azure-functions/functions-zone-redundancy.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ Availability zone configuration for Azure Functions depends on your [Functions h
27
27
28
28
## Prerequisites
29
29
30
-
Before configuring zone redundancy, review the requirements and details listed in [Reliability in Azure Functions - Resilience to availability zone failures](/azure/reliability/reliability-functions#resilience-to-availability-zone-failures).
30
+
Before configuring zone redundancy, review the requirements and details listed in [Reliability in Azure Functions - Resilience to availability zone failures](/azure/reliability/reliability-functions#resilience-to-availability-zone-failures).
31
31
32
32
::: zone pivot="premium-plan"
33
33
@@ -427,15 +427,15 @@ You can't change the availability zone support of an existing Elastic Premium pl
427
427
428
428
### Downtime
429
429
430
-
The downtime required for this migration depends on how you choose to redirect traffic during the migration from your old app to your new availability zone-enabled function app:
430
+
The downtime required for this migration depends on how you redirect traffic during the migration to your new availability zone-enabled function app:
431
431
432
432
- Consider HTTP-based functions that use an [Application Gateway](/azure/app-service/networking/app-gateway-with-service-endpoints), [custom domain](/azure/app-service/app-service-web-tutorial-custom-domain), or [Azure Front Door](/azure/frontdoor/front-door-overview). In this case, downtime depends on how long it takes to update those respective services with the new app information.
433
433
- You might also be routing traffic to multiple apps at the same time using a service such as [Azure Traffic Manager](/azure/app-service/web-sites-traffic-manager). In this scenario, you can only fully switch to the new zone-redundant app after everything is deployed and tested fully.
434
434
- For message-based functions, you should [write defensive functions](/azure/azure-functions/performance-reliability#write-defensive-functions) to ensure messages aren't lost during the migration.
435
435
436
436
### Migration steps
437
437
438
-
To enable an existing Premium plan function app to use availability zones, you must redeploy your project files to a new function app hosted in an zone-redundant Premium plan. Follow these steps:
438
+
To enable an existing Premium plan function app to use availability zones, redeploy your project files to a new function app hosted in an zone-redundant Premium plan. Follow these steps:
439
439
440
440
1. If you're already hosted in a Premium plan in a supported region, you can reuse your existing resource group and skip to the next step. Otherwise, create a new resource group in a supported region. For a list of regions that support zone redundancy for Azure Functions Premium plans, see [Reliability in Azure Functions - Resilience to availability zone failures - Requirements](/azure/reliability/reliability-functions#requirements).
441
441
1. Create a zone-redundant Premium plan in a supported region.
0 commit comments