Azure Blog Post: Applications on Azure Discussion
Azure App Service users can now take advantage of the latest updates to Availability Zones, offering improved resiliency and availability for their applications. Here's a comprehensive guide on how to implement and manage Availability Zones in Azure App Service effectively.
First and foremost, it's essential to utilise the Premium v2 to v4 tiers of App Service plans, as these are the only ones that support zone redundancy. This feature distributes your app resources across multiple physically separate availability zones in a region to improve resiliency and availability [1].
To enable zone redundancy, deploy at least three instances (workers) in the App Service plan. Although some documentation mentions a minimum of two instances, practical experience and error messages indicate that fewer than three instances are not allowed for zone redundancy [1][3].
Ensure the App Service plan is created in a resource group and scale unit that supports availability zones. If your current scale unit does not support zones, create the plan in a new resource group to get assigned to a supporting scale unit [1].
It's crucial to understand that once zone redundancy is enabled on an App Service plan, all apps under that plan become zone redundant. Therefore, ensure your apps can work with distributed deployment [1].
For even higher reliability, consider using multi-region deployments combined with availability zone redundancy. While availability zones protect against datacenter failure within a region, multi-region deployment guards against entire region failures [1].
To further enhance security, use managed identities and secure connection strings when integrating with services like Azure App Configuration. This approach maintains the benefits of zone redundancy while ensuring a secure connection [5].
Monitor your App Service plan's instance distribution across zones and verify failover behavior to validate that zone redundancy is functioning as expected.
Availability Zones refer to the deployment of applications across multiple availability zones within an Azure region. The zone redundant setting for App Service plans and App Service Environment v3 is now mutable throughout the life of the resources [2]. For App Service Environment v3, the minimum instance fee for enabling Availability Zones has been removed [4]. The minimum instance requirement for enabling Availability Zones has been reduced from three instances to two [4].
Currently, ARM/Bicep or Azure CLI can be used to enable the new Availability Zone features. Azure Portal support will be available by mid-June 2025 [6]. The new Availability Zone features for Azure App Service are now generally available [7].
Each availability zone consists of one or more data centers with independent power, cooling, and networking. The physical zone for each instance is now displayed, aiding in the verification of zone redundancy status for audits and compliance reviews [6]. Availability Zones ensure uninterrupted service by protecting applications and data from data center failures [8].
For more details on how to get started with Availability Zones on Premium V4, consult the documentation provided by Azure [9]. Many existing App Service plans with two or more instances will automatically support Availability Zones without additional setup [1].
In summary, to implement and manage Availability Zones effectively in Azure App Service, select the appropriate Premium plan, deploy at least three instances, ensure your scale unit supports zones, understand the impact on all hosted apps in a plan, and combine with multi-region deployments for best resiliency [1][3][5].
Utilising data-and-cloud-computing technology, Azure App Service users can now implement and manage Availability Zones effectively by selecting the appropriate Premium plan, deploying at least three instances, ensuring their scale unit supports zones, understanding the impact on all hosted apps in a plan, and considering multi-region deployments for enhanced resiliency.
Enhancing the security of data-and-cloud-computing integrations, use managed identities and secure connection strings when integrating with services like Azure App Configuration for zone redundancy.
