Merge pull request #266701 from SnehaSudhirG/20Feb-AVSetUpdate

updated the availability set section

Author: prmerger-automator[bot]

articles/update-manager/prerequsite-for-schedule-patching.md

@@ -3,7 +3,7 @@ title: Configure schedule patching on Azure VMs for business continuity
 description: The article describes the new prerequisites to configure scheduled patching to ensure business continuity in Azure Update Manager.
 ms.service: azure-update-manager
 ms.custom: devx-track-azurepowershell
-ms.date: 02/03/2024
+ms.date: 02/20/2024
 ms.topic: conceptual
 author: snehasudhirG
 ms.author: sudhirsneha
@@ -28,7 +28,9 @@ In some instances, when you remove the schedule from a VM, there's a possibility
 
 All VMs in a common [availability set](../virtual-machines/availability-set-overview.md) aren't updated concurrently.
 
-VMs in a common availability set are updated within Update Domain boundaries. VMs across multiple Update Domains aren't updated concurrently.
+VMs in a common availability set are updated within Update Domain boundaries. VMs across multiple Update Domains aren't updated concurrently. 
+
+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. 
 
 ## Find VMs with associated schedules