You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/update-center/scheduled-patching.md
+8-5Lines changed: 8 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -168,9 +168,9 @@ A notification appears that the deployment is created.
168
168
169
169
You can browse and manage all your maintenance configurations from a single place.
170
170
171
-
1. Search **Maintenance configurations** in the Azure portal. It shows a list of all maintenance configurations along with the Guest, resource group, location, and the subscription to which it belongs.
171
+
1. Search **Maintenance configurations** in the Azure portal. It shows a list of all maintenance configurations along with the maintenance scope, resource group, location, and the subscription to which it belongs.
172
172
173
-
1. You can filter maintenance configurations using filters at the top. Maintenance configurations related to Guest OS updates are the ones that have Guest as **InGuestPatch**.
173
+
1. You can filter maintenance configurations using filters at the top. Maintenance configurations related to Guest OS updates are the ones that have Maintenance scope as **InGuestPatch**.
174
174
175
175
You can create a new Guest OS update maintenance configuration or modify an existing configuration:
176
176
@@ -183,7 +183,10 @@ You can create a new Guest OS update maintenance configuration or modify an exis
183
183
1. In the **Updates (Preview)**, select **Scheduled updates**.
184
184
1. In **Create a maintenance configuration**, follow step 3 in this [procedure](#schedule-recurring-updates-on-single-vm) to create a maintenance configuration.
> The default option selected for **Maintenance scope** is *Host (dedicated/isolated infrastructure)*. Ensure that you select it as *Guest (Azure VM, Arc-enabled VMs/servers)*.
The update management center (preview) allows you to target a dynamic group of Azure or non-Azure VMs for update deployment via Azure Policy. Using a dynamic group keeps you from having to edit your deployment to update machines. You can use subscription, resource group, tags or regions to define the scope and use dynamic scoping by using built-in policies which you can customize as per your use-case.
212
+
The update management center (preview) allows you to target a group of Azure or non-Azure VMs for update deployment via Azure Policy. The grouping using policy, keeps you from having to edit your deployment to update machines. You can use subscription, resource group, tags or regions to define the scope and use this feature for the built-in policies which you can customize as per your use-case.
210
213
211
214
> [!NOTE]
212
215
> This policy also ensures that the patch orchestration property for Azure machines is set to **Azure-orchestrated (Automatic by Platform)** as it is a prerequisite for scheduled patching.
0 commit comments