Skip to content

Commit f3f755c

Browse files
committed
fixed warning
1 parent 7b5de9e commit f3f755c

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/update-manager/scheduled-patching.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ Update Manager uses a maintenance control schedule instead of creating its own s
2424
## Prerequisites for scheduled patching
2525

2626
1. See [Prerequisites for Update Manager](prerequisites.md).
27-
1. Patch orchestration of the Azure machines should be set to **Customer Managed Schedules**. For more information, see [Enable schedule patching on existing VMs](prerequsite-for-schedule-patching.md#enable-schedule-patching-on-azure-vms). For Azure Arc-enabled machines, it isn't a requirement.
27+
1. Patch orchestration of the Azure machines should be set to **Customer Managed Schedules**. For more information, see [Enable schedule patching on existing VMs](prerequsite-for-schedule-patching.md#enable-scheduled-patching-on-azure-vms). For Azure Arc-enabled machines, it isn't a requirement.
2828

2929
> [!NOTE]
3030
> If you set the patch mode to **Azure orchestrated** (`AutomaticByPlatform`) but do not enable the **BypassPlatformSafetyChecksOnUserSchedule** flag and do not attach a maintenance configuration to an Azure machine, it's treated as an [automatic guest patching](/azure/virtual-machines/automatic-vm-guest-patching)-enabled machine. The Azure platform automatically installs updates according to its own schedule. [Learn more](prerequisites.md).

0 commit comments

Comments
 (0)