Skip to content

Commit 2ba35b4

Browse files
Merge pull request #289863 from bmcder/patch-4
Update scheduled-patching.md
2 parents 8cb13b1 + 69900c6 commit 2ba35b4

File tree

1 file changed

+0
-3
lines changed

1 file changed

+0
-3
lines changed

articles/update-manager/scheduled-patching.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -12,9 +12,6 @@ ms.author: sudhirsneha
1212

1313
**Applies to:** :heavy_check_mark: Windows VMs :heavy_check_mark: Linux VMs :heavy_check_mark: On-premises environment :heavy_check_mark: Azure Arc-enabled servers.
1414

15-
> [!IMPORTANT]
16-
> - For a seamless scheduled patching experience, we recommend that for all Azure virtual machines (VMs), you update the patch orchestration to **Customer Managed Schedules** by **June 30, 2023**. If you fail to update the patch orchestration by June 30, 2023, you can experience a disruption in business continuity because the schedules will fail to patch the VMs. [Learn more](prerequsite-for-schedule-patching.md).
17-
1815
You can use Azure Update Manager to create and save recurring deployment schedules. You can create a schedule on a daily, weekly, or hourly cadence. You can specify the machines that must be updated as part of the schedule and the updates to be installed.
1916

2017
This schedule then automatically installs the updates according to the created schedule for a single VM and at scale.

0 commit comments

Comments
 (0)