Merge pull request #291310 from SnehaSudhirG/03Dec-FixBrokenLink

update schedule to scheduled

Author: prmerger-automator[bot]

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

@@ -1,30 +1,30 @@
 ---
-title: Configure schedule patching on Azure VMs for business continuity
+title: Configure scheduled 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: 09/06/2024
+ms.date: 12/03/2024
 ms.topic: how-to
 author: snehasudhirG
 ms.author: sudhirsneha
 ---
 
-# Configure schedule patching on Azure VMs for business continuity
+# Configure scheduled patching on Azure VMs for business continuity
 
 **Applies to:** :heavy_check_mark: Windows VMs :heavy_check_mark: Linux VMs :heavy_check_mark: Azure VMs.
 
-This article is an overview on how to configure schedule patching and automatic guest virtual machine (VM) patching on Azure VMs by using the new prerequisite to ensure business continuity. The steps to configure both the patching options on Azure Arc VMs remain the same.
+This article is an overview on how to configure scheduled patching and automatic guest virtual machine (VM) patching on Azure VMs by using the new prerequisite to ensure business continuity. The steps to configure both the patching options on Azure Arc VMs remain the same.
 
 Currently, you can enable [automatic guest VM patching](/azure/virtual-machines/automatic-vm-guest-patching) (autopatch) by setting the patch mode to **Azure-orchestrated** in the Azure portal or **AutomaticByPlatform** in the REST API, where patches are automatically applied during off-peak hours.
 
-For customizing control over your patch installation, you can use [schedule patching](updates-maintenance-schedules.md#scheduled-patching) to define your maintenance window. You can [enable schedule patching](scheduled-patching.md#schedule-recurring-updates-on-a-single-vm) by setting the patch mode to **Azure-orchestrated** in the Azure portal or **AutomaticByPlatform** in the REST API and attaching a schedule to the Azure VM. So, the VM properties couldn't be differentiated between **schedule patching** or **Automatic guest VM patching** because both had the patch mode set to **Azure-orchestrated**.
+For customizing control over your patch installation, you can use [scheduled patching](updates-maintenance-schedules.md#scheduled-patching) to define your maintenance window. You can [enable scheduled patching](scheduled-patching.md#schedule-recurring-updates-on-a-single-vm) by setting the patch mode to **Azure-orchestrated** in the Azure portal or **AutomaticByPlatform** in the REST API and attaching a scheduled to the Azure VM. So, the VM properties couldn't be differentiated between **scheduled patching** or **Automatic guest VM patching** because both had the patch mode set to **Azure-orchestrated**.
 
-In some instances, when you remove the schedule from a VM, there's a possibility that the VM might be autopatched and rebooted. To overcome the limitations, we've introduced a new prerequisite, `ByPassPlatformSafetyChecksOnUserSchedule`, which can now be set to `true` to identify a VM by using schedule patching. It means that VMs with this property set to `true` are no longer autopatched when the VMs don't have an associated maintenance configuration.
+In some instances, when you remove the scheduled from a VM, there's a possibility that the VM might be autopatched and rebooted. To overcome the limitations, we've introduced a new prerequisite, `ByPassPlatformSafetyChecksOnUserSchedule`, which can now be set to `true` to identify a VM by using scheduled patching. It means that VMs with this property set to `true` are no longer autopatched when the VMs don't have an associated maintenance configuration.
 
 > [!IMPORTANT]
 > For a continued scheduled patching experience, you must ensure that the new VM property, `BypassPlatformSafetyChecksOnUserSchedule`, is enabled on all your Azure VMs (existing or new) that have schedules attached to them by **June 30, 2023**. This setting ensures that machines are patched by using your configured schedules and not autopatched. Failing to enable by June 30, 2023, gives an error that the prerequisites aren't met.
 
-## Schedule patching in an availability set
+## Scheduled patching in an availability set
 
 All VMs in a common [availability set](/azure/virtual-machines/availability-set-overview) aren't updated concurrently.
 
@@ -43,9 +43,9 @@ To identify the list of VMs with the associated schedules for which you have to
 
    In the corresponding **Name** column, you can view the list of VMs to which you need to enable the `ByPassPlatformSafetyChecksOnUserSchedule` flag.
 
-## Enable schedule patching on Azure VMs
+## Enable scheduled patching on Azure VMs
 
-To enable schedule patching on Azure VMs, follow these steps.
+To enable scheduled patching on Azure VMs, follow these steps.
 
 # [Azure portal](#tab/new-prereq-portal)
 
@@ -190,7 +190,7 @@ Update-AzVM -VM $VirtualMachine -ResourceGroupName "<resourceGroup>"
 ---
 
 > [!NOTE]
-> You can now enable the new prerequisite for schedule patching via the Azure portal, REST API, PowerShell and Azure CLI.
+> You can now enable the new prerequisite for scheduled patching via the Azure portal, REST API, PowerShell and Azure CLI.
 
 ## Enable automatic guest VM patching on Azure VMs
 
@@ -289,18 +289,18 @@ PATCH on `/subscriptions/subscription_id/resourceGroups/myResourceGroup/provider
 
 Scenarios | Azure-orchestrated | BypassPlatformSafetyChecksOnUserSchedule | Schedule associated |Expected behavior in Azure |
 --- | --- | --- | --- | ---|
-Scenario 1 | Yes | True | Yes | The schedule patch runs as defined by user. |
-Scenario 2 | Yes | True | No | Autopatch and schedule patch don't run.|
-Scenario 3 | Yes | False | Yes | Autopatch and schedule patch don't run. You get an error that the prerequisites for schedule patch aren't met.|
+Scenario 1 | Yes | True | Yes | The scheduled patch runs as defined by user. |
+Scenario 2 | Yes | True | No | Autopatch and scheduled patch don't run.|
+Scenario 3 | Yes | False | Yes | Autopatch and scheduled patch don't run. You get an error that the prerequisites for scheduled patch aren't met.|
 Scenario 4 | Yes |  False | No   | The VM is autopatched.|
-Scenario 5 | No | True | Yes | Autopatch and schedule patch don't run. You get an error that the prerequisites for schedule patch aren't met. |
-Scenario 6 | No | True | No | Autopatch and schedule patch don't run.|
-Scenario 7 | No | False | Yes | Autopatch and schedule patch don't run. You get an error that the prerequisites for schedule patch aren't met.|
-Scenario 8 | No | False | No | Autopatch and schedule patch don't run.|
+Scenario 5 | No | True | Yes | Autopatch and schedule patch don't run. You get an error that the prerequisites for scheduled patch aren't met. |
+Scenario 6 | No | True | No | Autopatch and scheduled patch don't run.|
+Scenario 7 | No | False | Yes | Autopatch and scheduled patch don't run. You get an error that the prerequisites for scheduled patch aren't met.|
+Scenario 8 | No | False | No | Autopatch and scheduled patch don't run.|
 
 ## Next steps
 
-- Learn more about [Dynamic scope](dynamic-scope-overview.md), an advanced capability of schedule patching.
+- Learn more about [Dynamic scope](dynamic-scope-overview.md), an advanced capability of scheduled patching.
 - Follow the instructions on how to [manage various operations of Dynamic scope](manage-dynamic-scoping.md)
 - Learn on how to [automatically installs the updates according to the created schedule both for a single VM and at scale](scheduled-patching.md).
 - Learn about [pre and post events](pre-post-scripts-overview.md) to automatically perform tasks before and after a scheduled maintenance configuration.

articles/update-manager/scheduled-patching.md

@@ -24,12 +24,12 @@ Update Manager uses a maintenance control schedule instead of creating its own s
 ## Prerequisites for scheduled patching
 
 1. See [Prerequisites for Update Manager](prerequisites.md).
-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.
+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.
 
 	> [!NOTE]
 	> 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).
 
-## Schedule patching in an availability set
+## Scheduled patching in an availability set
 
 All VMs in a common [availability set](/azure/virtual-machines/availability-set-overview) aren't updated concurrently.