Skip to content

Commit b255850

Browse files
Merge pull request #265280 from SnehaSudhirG/05Feb-AvailabilitySetUpdate
Added new info
2 parents 34ee48f + 1c0a273 commit b255850

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

articles/update-manager/scheduled-patching.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Scheduling recurring updates in Azure Update Manager
33
description: This article details how to use Azure Update Manager to set update schedules that install recurring updates on your machines.
44
ms.service: azure-update-manager
5-
ms.date: 02/03/2024
5+
ms.date: 02/05/2024
66
ms.topic: conceptual
77
author: SnehaSudhirG
88
ms.author: sudhirsneha
@@ -33,7 +33,10 @@ Update Manager uses a maintenance control schedule instead of creating its own s
3333

3434
All VMs in a common [availability set](../virtual-machines/availability-set-overview.md) aren't updated concurrently.
3535

36-
VMs in a common availability set are updated within Update Domain boundaries. VMs across multiple Update Domains aren't updated concurrently.
36+
VMs in a common availability set are updated within Update Domain boundaries. VMs across multiple Update Domains aren't updated concurrently.
37+
38+
In scenarios where machines from the same availability set are being patched at the same time in different schedules, it is likely that they might not get patched or could potentially fail if the maintenance window exceeds. To avoid this, we recommend that you either increase the maintenance window or split the machines belonging to the same availability set across multiple schedules at different times.
39+
3740

3841
## Configure reboot settings
3942

0 commit comments

Comments
 (0)