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
You can check the registration status of each feature by using:
@@ -212,6 +214,7 @@ You can update the scale set to scale out instances to one or more additional av
212
214
213
215
> [!IMPORTANT]
214
216
> When you expand the scale set to additional zones, the original instances are not migrated or changed. When you scale out, new instances will be created and spread evenly across the selected availability zones. When you scale in the scale set, any regional instances will be priorized for removal first. After that, instances will be removed based on the [scale in policy](virtual-machine-scale-sets-scale-in-policy.md).
217
+
215
218
Expanding to a zonal scale set is done in 3 steps:
216
219
217
220
1. Prepare for zonal expansion
@@ -322,3 +325,24 @@ Now that you have created a scale set in an Availability Zone, you can learn how
0 commit comments