Skip to content

Commit 08f9b3c

Browse files
authored
Update virtual-machine-scale-sets-automatic-upgrade.md
updated the capitalization.
1 parent a7990fa commit 08f9b3c

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/virtual-machine-scale-sets/virtual-machine-scale-sets-automatic-upgrade.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ Automatic OS upgrade has the following characteristics:
3535

3636
An upgrade works by replacing the OS disk of a VM with a new disk created using the latest image version. Any configured extensions and custom data scripts are run on the OS disk, while data disks are retained. To minimize the application downtime, upgrades take place in batches, with no more than 20% of the scale set upgrading at any time.
3737

38-
You must integrate an Azure Load Balancer application health probe or [Application Health extension](virtual-machine-scale-sets-health-extension.md) to track the health of the application after an upgrade. This allows the platform to validate the VM health to ensure updates are applied in a Safe manner. We recommend incorporating an application heartbeat to validate upgrade success.
38+
You must integrate an Azure Load Balancer application health probe or [Application Health extension](virtual-machine-scale-sets-health-extension.md) to track the health of the application after an upgrade. This allows the platform to validate the VM health to ensure updates are applied in a safe manner. We recommend incorporating an application heartbeat to validate upgrade success.
3939

4040
### Availability-first Updates
4141
The availability-first model for platform orchestrated updates described below ensures that availability configurations in Azure are respected across multiple availability levels.

0 commit comments

Comments
 (0)