Skip to content

Commit 25be53d

Browse files
authored
Update virtual-machine-scale-sets-maxsurge.md
1 parent 9981cc2 commit 25be53d

File tree

1 file changed

+13
-0
lines changed

1 file changed

+13
-0
lines changed

articles/virtual-machine-scale-sets/virtual-machine-scale-sets-maxsurge.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,19 @@ ms.custom: upgradepolicy. maxsurge
1818
1919
Rolling upgrades with MaxSurge can help improve service uptime during upgrade events. With MaxSurge enabled, new instances are created in batches using the latest scale model. When the new instances are fully created and healthy, they begin taking traffic. The scale set then deletes instances in batches matching the old scale set model. The process continues until all instances are brought up-to-date.
2020

21+
## Prerequisites
22+
23+
Before configuring a rolling upgrade policy on a Virtual Machine Scale Set with Flexible Orchestration or enabling MaxSurge on either Flexible or Uniform Orchestration deployments, register the feature providers to your subscription.
24+
25+
## Feature Registration
26+
27+
```azurepowershell-interactive
28+
Register-AzProviderFeature -FeatureName VMSSFlexRollingUpgrade -ProviderNameSpace Microsoft.Compute
29+
30+
Register-AzProviderFeature -FeatureName MaxSurgeRollingUpgrade -ProviderNamespace Microsoft.Compute
31+
```
32+
33+
2134
## Concepts
2235

2336
> [!NOTE]

0 commit comments

Comments
 (0)