Availability zones support for Azure Functions is available on Premium (Elastic Premium) and Dedicated (App Service) plans. A zone-redundant function app plan automatically balances its instances between availability zones for higher availability. This article describes how to migrate to the public multitenant Premium plan with availability zone support. For migration to zone redundancy on Dedicated plans, refer here.
Downtime requirementsBecause you can't convert preexisting Premium plans to use availability zones, you must instead migrate your app by creating a side-by-side deployment on a new Premium plan app. Downtime depends on how you choose to redirect traffic during the migration from your old app to your new availability zone-enabled function app.
Consider HTTP-based functions that use an Application Gateway, custom domain, or Azure Front Door. In this case, downtime depends on how long it takes to update those respective services with the new app information.
You might also be routing traffic to multiple apps at the same time using a service such as Azure Traffic Manager. In this scenario, you can only fully switch to the new availability zone-enabled app after everything is deployed and tested fully.
For message-based functions, you should write defensive functions to ensure messages aren't lost during the migration.
Migration guidance: RedeploymentTo enable an existing function app to use availability zones, you must redeploy your project files to a new function app hosted in an availability zone-enabled Premium plan.
Use these steps to enable availability zones:
Learn about the Azure Functions Premium plan
Learn about Azure Functions support for availability zone redundancy and disaster recovery
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4