Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Applies to: ✔️ Windows VMs ✔️ Linux VMs ✔️ On-premises environment ✔️ Azure Arc-enabled servers.
This article describes how to view, add, edit, and delete a dynamic scope that's associated with a maintenance configuration in Azure Update Manager.
You can create a dynamic scope at either the subscription level or the resource group level. A subscription or resource group is mandatory for the creation of a dynamic scope, and you can't edit it after the dynamic scope is created.
Resources eligible to be attached to a dynamic scope are determined by the level at which you create the scope. If you set the scope at the resource group level (for example, RG1), resources from other groups (for example, RG2) will be unassigned if they're attached to the dynamic scope created under RG1. Those resources from other groups will be reassigned even if they're under the same subscription.
Prerequisites
Patch Orchestration must be set to Customer Managed Schedules.
Add a dynamic scope
Sign in to the Azure portal and go to Azure Update Manager.
Select Machines > Maintenance configurations.
On the Maintenance configurations pane, select the name of the maintenance configuration for which you want to add a dynamic scope.
On the page for the chosen maintenance configuration, select Dynamic scopes > Add a dynamic scope.
On the Add a dynamic scope pane, select subscriptions (mandatory).
Note
You should create subscription-level dynamic scope assignments with an empty location, because a subscription isn't associated with any specific region.
In Filter by, choose Select. In Select Filter by, specify the resource group, resource type, location, tags, and OS type. Then select Ok. These filters are optional fields.
In Preview of machines based on above scope, you can view the list of machines for the selected criteria. When you finish, select Save.
Note
The list of machines might be different at run time.
On the Configure Azure VMs for schedule updates pane, select one of the following options to provide your consent:
Change the required options to ensure schedule supportability ensures that the machines are patched according to the schedule and not automatically patched. By selecting this option, you're confirming that you want to update the patch orchestration to Customer Managed Schedules. This setting updates the following two properties on your behalf:
Patch mode = AutomaticByPlatformBypassPlatformSafetyChecksOnUserSchedule = True
Continue with supported machines only confirms that you want to proceed with only the machines that already have patch orchestration set to Customer Managed Schedules.
In Preview of machines based on above scope, you can view only the machines that don't have patch orchestration set to Customer Managed Schedules.
Select Save. A notification confirms that the dynamic scopes are successfully applied.
View a dynamic scope
Sign in to the Azure portal and go to Azure Update Manager.
Select Machines > Maintenance configurations.
On the Maintenance configurations pane, select the name of the maintenance configuration for which you want to view the dynamic scope.
On the pane for the chosen maintenance configuration, select Dynamic scopes to view all the dynamic scopes that are associated with that configuration.
The schedules associated with dynamic scopes appear in the following two areas:
- Azure Update Manager > Machines > Associated schedules column
- Virtual machine (VM) home page > Updates > Scheduling tab
To view the VMs that are associated with the schedule, go to the existing schedule and then select the Dynamic scopes tab.
Edit a dynamic scope
Sign in to the Azure portal and go to Azure Update Manager.
Select Machines > Maintenance configurations.
On the Maintenance configurations pane, select the name of the maintenance configuration for which you want to edit an existing dynamic scope.
On the pane for the chosen maintenance configuration, select Dynamic scopes, and then select the scope that you want to edit. In the Actions column, select the edit icon.
On the Edit Dynamic scope pane, in Filter By, select the edit icon. Edit the filters as needed, and then select Ok.
Select Save.
Delete a dynamic scope
Sign in to the Azure portal and go to Azure Update Manager.
Select Machines > Browse maintenance configurations > Maintenance configurations.
On the Maintenance configurations pane, select the name of the maintenance configuration for which you want to edit an existing dynamic scope.
On the pane for the chosen maintenance configuration, select Dynamic scopes, and then select the scope that you want to delete. Select Remove dynamic scope, and then select Ok.
View the patch history of a dynamic scope
Sign in to the Azure portal and go to Azure Update Manager.
Select History to view the patch history of a dynamic scope.
Provide consent to apply updates
Obtaining consent to apply updates is an important step in the workflow of dynamic scoping. The following tabs describe the various ways to provide consent.
Note
There are no prerequisites for Azure Arc-enabled VMs.
In the Azure portal, go to +Create a resource > Virtual machine > Create.
On the Create a virtual machine pane, select the Management tab. Under Guest OS Updates, in Patch orchestration options, select Azure-orchestrated. It sets the following properties:
Patch mode = AutomaticByPlatformBypassPlatformSafetyChecksOnUserSchedule = True
Complete the details on the Monitoring, Advanced, and Tags tabs.
Select Review + Create. Under Management, you can view the Periodic assessment value as Off and the Patch orchestration options value as Azure-orchestrated.
Select Create.
Related content
- Learn more about dynamic scoping, an advanced capability of scheduled patching.
- Learn how to automatically install updates according to the created schedule for a single VM and at scale.
- Learn about pre-maintenance and post-maintenance events to automatically perform tasks before and after a scheduled maintenance configuration.