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-manager/includes/dynamic-scope-prerequisites.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,11 +10,11 @@ ms.date: 08/02/2023
10
10
11
11
#### [Azure VMs](#tab/avms)
12
12
13
-
- Patch Orchestration must be set to Customer Managed Schedules. This sets patch mode to AutomaticByPlatform and the **BypassPlatformSafetyChecksOnUserSchedule** = *True*.
13
+
- Patch Orchestration must be set to Customer Managed Schedules. This sets **patch mode** to *AutomaticByPlatform* and the **BypassPlatformSafetyChecksOnUserSchedule** = *True*.
14
14
- Associate a Schedule with the VM.
15
15
16
16
#### [Arc-enabled VMs](#tab/arcvms)
17
17
18
-
There are no prerequisites for patch orchestration. However, you must associate a schedule with the VM for Schedule patching. For more information, see [Configure schedule patching on Azure VMs to ensure business continuity](../prerequsite-for-schedule-patching.md).
18
+
There are **no prerequisites** for patch orchestration. However, you must associate a schedule with the VM for Schedule patching. For more information, see [Configure schedule patching on Azure VMs to ensure business continuity](../prerequsite-for-schedule-patching.md).
1. In the **Maintenance configurations** page, select the name of the maintenance configuration for which you want to add a Dynamic scope.
25
25
1. In the given maintenance configuration page > select **Dynamic scopes** > **Add a dynamic scope**.
26
-
1. In the **Add a dynamic scope** page, select **subscriptions**(mandatory).
26
+
1. In the **Add a dynamic scope** page, select **subscriptions**(mandatory).
27
27
1. In **Filter by**, choose **Select** and in the **Select Filter by**, specify the Resource group, Resource type, Location, Tags and OS type and then select **Ok**. These filters are optional fields.
28
-
1. In the **Preview of machines based on above scope**, you can view the list of machines for the selected criteria and then select **Add**.
28
+
1. In the **Preview of machines based on above scope**, you can view the list of machines for the selected criteria and then select **Save**.
29
29
> [!NOTE]
30
30
> The list of machines may be different at run time.
31
31
1. In the **Configure Azure VMs for schedule updates** page, select any one of the following options to provide your consent:
32
-
1.**Change the required options to ensure schedule supportability**- this option confirms that you want to update the patch orchestration from existing option to *Customer Managed Schedules*: This updates the following two properties on your behalf:
32
+
1.**Change the required options to ensure schedule supportability**ensures that the machines are patched as per schedule and not autopatched. By selecting this option, you are confirming that you want to update the patch orchestration to *Customer Managed Schedules*: This updates the following two properties on your behalf:
33
33
34
34
-*Patch mode = AutomaticByPlatform*
35
35
-*Set the BypassPlatformSafetyChecksOnUserSchedule = True*.
@@ -38,13 +38,14 @@ To add a Dynamic scope to an existing configuration, follow these steps:
38
38
> [!NOTE]
39
39
> In the **Preview of machines based on above scope** page, you can view only the machines that don't have patch orchestration set to *Customer Managed Schedules*.
40
40
41
-
1. Select **Save** to go back to the Dynamic scopes tab. In this tab, you can view and edit the Dynamic scope that you have created.
41
+
1. Select **Save**. Notification confirms that the Dynamic scopes are successfully applied.
42
+
1. In the **Maintenance configuration | Dynamic scopes** page, you can view and edit the Dynamic scopes that were created.
42
43
43
44
## View Dynamic scope
44
45
To view the list of Dynamic scopes associated to a given maintenance configuration, follow these steps:
45
46
46
47
1. Sign in to the [Azure portal](https://portal.azure.com) and navigate to **Azure Update Manager**.
1. In the **Maintenance configurations** page, select the name of the maintenance configuration for which you want to view the Dynamic scope.
49
50
1. In the given maintenance configuration page, select **Dynamic scopes** to view all the Dynamic scopes that are associated with the maintenance configuration.
50
51
@@ -59,7 +60,7 @@ To view the list of Dynamic scopes associated to a given maintenance configurati
59
60
## Edit a Dynamic scope
60
61
61
62
1. Sign in to the [Azure portal](https://portal.azure.com) and navigate to **Azure Update Manager**.
1. In the **Maintenance configurations** page, select the name of the maintenance configuration for which you want to edit an existing Dynamic scope.
64
65
1. In the given maintenance configuration page > select **Dynamic scopes** and select the scope you want to edit. Under **Actions** column, select the edit icon.
65
66
1. In the **Edit Dynamic scope**, select the edit icon in the **Filter By** to edit the filters as needed and select **Ok**.
@@ -77,47 +78,49 @@ To view the list of Dynamic scopes associated to a given maintenance configurati
77
78
## View patch history of a Dynamic scope
78
79
79
80
1. Sign in to the [Azure portal](https://portal.azure.com) and navigate to **Azure Update Manager**.
80
-
1. Select **History**> **Browse maintenance configurations** > **Maintenance configurations**to view the patch history of a dynamic scope.
81
+
1. Select **History** to view the patch history of a dynamic scope.
81
82
82
83
## Provide consent to apply updates
83
84
84
85
Obtaining consent to apply updates is an important step in the workflow of dynamic scoping and listed are the various ways to provide consent.
85
86
87
+
>[!NOTE]
88
+
> There are no prerequisites for Arc-enabled VMs.
89
+
86
90
#### [From Virtual Machine](#tab/vm)
87
91
88
92
1. In [Azure portal](https://portal.azure.com), go to **+Create a resource** > **Virtual machine** > **Create**.
89
-
1. In **Create a virtual machine**, select **Management** tab and under the **Guest OS Updates**, in **Patch orchestration options**, you can do the following:
90
-
1. Select **Azure-orchestrated with user managed schedules (Preview)** to confirm that:
91
-
92
-
- Patch Orchestration is set to *Azure orchestration*
93
-
- Set the Bypass platform safety checks on user schedule = *True*.
93
+
1. In **Create a virtual machine**, select **Management** tab and under the **Guest OS Updates**, in **Patch orchestration options**, select **Azure-orchestrated**. It sets the following properties:
94
94
95
-
The selection allows you to provide consent to apply the update settings, ensures that auto patching isn't applied and that patching on the VM(s) runs as per the schedule you've defined.
95
+
- Patch mode is set to *AutomaticByPlatform*
96
+
- Set the BypassPlatformSafetyChecksOnUserSchedule = *True*
96
97
97
98
1. Complete the details under **Monitoring**, **Advanced** and **Tags** tabs.
98
-
1. Select **Review + Create** and under the **Management** you can view the values as **Periodic assessment** - *Off* and **Patch orchestration options** - *Azure-orchestrated with user managed schedules (Preview)*.
99
+
1. Select **Review + Create** and under the **Management** you can view the values as **Periodic assessment** - *Off* and **Patch orchestration options** - *Azure-orchestrated*.
99
100
1. Select **Create**.
100
101
101
102
102
103
#### [From Schedule updates tab](#tab/sc)
103
104
104
105
1. Follow the steps from 1 to 5 listed in [Add a Dynamic scope](#add-a-dynamic-scope).
105
-
1. In **Machines** tab, select **Add machine**, In **Select resources** page, select the machines and select **Add**
106
-
1. In **Configure Azure VMs for schedule updates**, select **Continue to schedule updates** option to confirm that:
106
+
1. In **Configure Azure VMs for schedule updates**, page select **Change the required options to ensure schedule supportability** option to confirm that **patch orchestration** is set as **Customer Managed Schedules**. It sets the following properties:
107
107
108
-
- Patch Orchestration is set to *Azure orchestration*
109
-
- Set the Bypass platform safety checks on user schedule = *True*.
108
+
- Patch mode is set to *AutomaticByPlatform*
109
+
- Set the BypassPlatformSafetyChecksOnUserSchedule = *True*.
110
110
111
-
1. Select **Continue to schedule updates** to update the patch mode as **Azure-orchestrated** and enable the scheduled patching for the VMs after obtaining the consent.
111
+
The selection allows you to provide consent to apply the update settings, ensures that auto patching isn't applied and that patching on the VM(s) runs as per the schedule you've defined.
112
+
113
+
1. Select **Save**.
112
114
113
115
#### [From Update Settings](#tab/us)
114
116
115
-
1. In **Azure Update Manager**, go to **Overview** > **Update settings**.
117
+
1. In **Azure Update Manager**, go to **Overview** > **Settings** > **Update settings**.
116
118
1. In **Change Update settings**, select **+Add machine** to add the machines.
117
-
1. In the list of machines sorted as per the operating system, go to the **Patch orchestration** option and select **Azure-orchestrated with user managed schedules (Preview)** to confirm that:
119
+
1. In the list of machines sorted as per the operating system, go to the **Patch orchestration** option and select **Customer Managed Schedules**. It sets the following properties:
120
+
121
+
- Patch mode is set to *AutomaticByPlatform*
122
+
- Set the BypassPlatformSafetyChecksOnUserSchedule = *True*
118
123
119
-
- Patch Orchestration is set to *Azure orchestration*
120
-
- Set the Bypass platform safety checks on user schedule = *True*
121
124
1. Select **Save**.
122
125
123
126
The selection made in this workflow automatically applies the update settings and no consent is explicitly obtained.
0 commit comments