Loading...

Public Preview Announcement: Azure VMSS Zonal Expansion

Public Preview Announcement: Azure VMSS Zonal Expansion

Authors: Jerry Steele, Senior Product Manager

 

We're thrilled to introduce the public preview of VMSS Zonal Expansion. This feature enables you to take regionally (non-zonal) configured VMs and distribute across Azure availability zones in a zonal configuration, enhancing your business continuity and resilience with minimal disruption and potentially increasing your availability SLA from 99.95% to 99.99%.

 

Azure availability zones are distinct data centers within a region, each with its unique power, network, and cooling system.  Azure ensures the highest SLA guarantees for VMs distributed across multiple availability zones, otherwise known as a zonal redundant configuration. Previously, migrating VMs from a non-zonal configuration to a zonal or zone redundant configuration was manual, time-consuming, and led to significant app downtime. Our new features simplify the end to end process for migrating your VM infrastructure to span availability zones.   

 

This feature allows you to modify a virtual machine scale set (VMSS) to expand the set of zones over which to spread VM instances. New instances will be evenly and explicitly spread across availability zones, allowing you to update your scale set environment to the Azure recommended zone-redundant availability strategy without deleting and recreating instances and without application downtime. This preview is supported for VMSS stateless infrastructure workloads that do not need to preserve disks or network resources. It is not supported for scale sets with stateful workloads or used with Service Fabric or Azure Kubernetes Services. 

 

Benefits

  • This feature enables you to increase the availability and resiliency of your scale set by taking advantage of higher zonal availability SLA (99.99%) vs regional availability SLA (99.95%) 
  • Update the selection of zones over which the scale set will spread instances without deleting and recreating the scale set
  • Expand your scale set to take advantage of new availability zones that were not available when the scale set was created. 

How does it work?

Consider a regional virtual machine scale set with an application running across 10 instances. A regional scale set does not have zones explicitly specified (zones=[] or zones=null). When this scale set was created in the southcentralus region, the region did not support Availability Zones. Since then, the region has been upgraded to support 3 Availability Zones. Workloads where VM instances are spread across Availability Zones receive a higher availability SLA than regional deployments, and you would like to take advantage of the improved availability to improve the reliability of your application.   

Before this preview feature was enabled, you could not change the zonal configuration of a virtual machine scale set, so you would have to recreate your application in a new zonal scale set. With the VMSS Zonal Expansion feature, expanding to a zonal scale set can be done in place without application downtime.  

 

VMSS zonal expansion is done in three steps:  

  1. Prepare for zonal expansion: Check your quota, the availability of your VM size and disk types in the desired zones, and the validity of your scale set configuration for zonal expansion.  
  2. Update the zones parameter on the scale set: Use the REST API, Azure Portal, Azure CLI, or Azure PowerShell to change the zones parameter on the scale set. For example, using the CLI  
     
    az vmss update --set zones=["1","2","3"] -n myScaleSet -g myResourceGroup  
  3. Add new zonal instances and remove original instances: Update the capacity of the scale set to add additional instances in the selected zones. Then, scale in to remove the original regional VMs. You can either manually scale out and in, or automate the process with rolling upgrades + maxsurge (also in preview).  

 

This example describes expanding from a regional scale set (no zones defined) to zone spanning scale set (3 zones defined). You could also expand from zonal (1 zone defined) to multiple zones defined.  

Learn More

We understand that the applications you deploy to the cloud are mission critical, and how important it is that the applications you build on top of Azure and virtual machines and virtual machine scale sets are reliable and resilient in the face of rapidly changing requirements, usage, network traffic and internet environments. This is the beginning of a set of features we are planning to help you achieve the highest reliability and SLAs for your mission critical workloads on Azure. 

 

This is part of our ongoing commitment to helping you elevate the availability of your workloads to the highest SLAs. We look forward to your feedback on these features! 

 

Learn how to scale your virtual machine scale set across multiple zones and register for the preview today!

Published on:

Learn more
Azure Compute Blog articles
Azure Compute Blog articles

Azure Compute Blog articles

Share post:

Related posts

See our new Azure Cosmos DB Design Patterns

Design patterns are where good data modeling lives or dies. In a NoSQL database like Azure Cosmos DB, the difference between a schema that sca...

8 hours ago

Need a different partition key in Azure Cosmos DB? Pick the right approach

Once you create a container, its partition key is fixed at creation, and you can’t change it in place. However, if your original key starts ca...

14 hours ago

Azure SDK Release (June 2026)

Azure SDK releases every month. In this post, you'll find this month's highlights and release notes. The post Azure SDK Release (June 2026) ap...

22 hours ago

Fundamentals of Azure DevOps with SQL projects

Building automated pipelines with your SQL database projects enables you to build a rich CI/CD ecosystem to ensure that your application is be...

4 days ago

Upcoming Change: NTLM Removal in Git (libcurl) – Impact to Azure DevOps Server Customers

Overview In September 2026, NTLM support will be removed from libcurl, which is used by Git for HTTP(S) operations. As a result, Git operation...

5 days ago

What’s new across Microsoft SQL in 2026 so far (SQL Server, Azure SQL, and SQL database in Fabric)

We’re halfway through 2026, and Microsoft SQL has not slowed down. Since SQLCon/FabCon in March (where we released a ton of things, and those ...

5 days ago

Power Automate Flow — HTTP Trigger to Azure OpenAI

Build the secure Power Automate HTTP trigger flow that receives free text from the portal, calls Azure OpenAI using your smart-form-extract de...

7 days ago

Spring AI 2.0 is GA: Vector Search, Memory, and Agents on Azure Cosmos DB

The wait is over. Spring AI 2.0 is generally available, and Azure Cosmos DB is right there with it. With this release, Spring AI graduates int...

7 days ago
Stay up to date with latest Microsoft Dynamics 365 and Power Platform news!
* Yes, I agree to the privacy policy