Skip to content

Commit 7932c19

Browse files
Merge pull request #219033 from maulikshah23/patch-9
Update automatic-vm-guest-patching.md
2 parents a726e4e + ed4877c commit 7932c19

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

articles/virtual-machines/automatic-vm-guest-patching.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -67,6 +67,10 @@ For OS types that release patches on a fixed cadence, VMs configured to the publ
6767

6868
As a new rollout is triggered every month, a VM will receive at least one patch rollout every month if the VM is powered on during off-peak hours. This process ensures that the VM is patched with the latest available security and critical patches on a monthly basis. To ensure consistency in the set of patches installed, you can configure your VMs to assess and download patches from your own private repositories.
6969

70+
**Application Health Extension**
71+
72+
To monitor your application's health on an instance Azure recommends the installation of the [Application Health Extension](../virtual-machine-scale-sets/virtual-machine-scale-sets-health-extension.md). Once a patch is applied, the extension can validate that the VM is in a healthy state based on the configured criteria. Azure can stop applying the patch in subsequent availability sets or regions if significant nuymber of VMs are negatively impated.
73+
7074
## Supported OS images
7175

7276
> [!IMPORTANT]

0 commit comments

Comments
 (0)