Skip to content

Commit f78ebc8

Browse files
committed
Feedback incorporated - added a note and edited the heading for dynamic grouping
1 parent 1e3ab79 commit f78ebc8

File tree

1 file changed

+8
-5
lines changed

1 file changed

+8
-5
lines changed

articles/update-center/scheduled-patching.md

Lines changed: 8 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -168,9 +168,9 @@ A notification appears that the deployment is created.
168168

169169
You can browse and manage all your maintenance configurations from a single place.
170170

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.
172172

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**.
174174

175175
You can create a new Guest OS update maintenance configuration or modify an existing configuration:
176176

@@ -183,7 +183,10 @@ You can create a new Guest OS update maintenance configuration or modify an exis
183183
1. In the **Updates (Preview)**, select **Scheduled updates**.
184184
1. In **Create a maintenance configuration**, follow step 3 in this [procedure](#schedule-recurring-updates-on-single-vm) to create a maintenance configuration.
185185

186-
:::image type="content" source="./media/scheduled-updates/create-maintenance-configuration.png" alt-text="Create Maintenance configuration.":::
186+
> [!NOTE]
187+
> 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)*.
188+
189+
:::image type="content" source="./media/scheduled-updates/create-maintenance-configuration.png" alt-text="Create Maintenance configuration.":::
187190

188191

189192
### Add/remove machines from maintenance configuration
@@ -204,9 +207,9 @@ You can create a new Guest OS update maintenance configuration or modify an exis
204207

205208
:::image type="content" source="./media/scheduled-updates/change-update-selection-criteria-of-maintenance-configuration-inline.png" alt-text="Change update selection criteria of Maintenance configuration." lightbox="./media/scheduled-updates/change-update-selection-criteria-of-maintenance-configuration-expanded.png":::
206209

207-
## Dynamic scoping using policy
210+
## Grouping using policy
208211

209-
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.
210213

211214
> [!NOTE]
212215
> 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

Comments
 (0)