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/prerequsite-for-schedule-patching.md
+90-77Lines changed: 90 additions & 77 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,18 +1,18 @@
1
1
---
2
-
title: Prerequisites for scheduled patching in update management center (preview).
3
-
description: The article describes the new prerequisites to configure scheduled patching in Update management center (preview).
2
+
title: Configure schedule patching on Azure VMs to ensure business continuity in update management center (preview).
3
+
description: The article describes the new prerequisites to configure scheduled patching to ensure business continuity in Update management center (preview).
4
4
ms.service: update-management-center
5
-
ms.date: 04/18/2023
5
+
ms.date: 04/24/2023
6
6
ms.topic: conceptual
7
7
author: snehasudhirG
8
8
ms.author: sudhirsneha
9
9
---
10
10
11
-
# Configure Azure VMs for enhanced patching
11
+
# Configure schedule patching on Azure VMs to ensure business continuity
12
12
13
13
**Applies to:**:heavy_check_mark: Windows VMs :heavy_check_mark: Linux VMs :heavy_check_mark: Azure VMs.
14
14
15
-
This article is an overview on how to configure Schedule patching and Automatic guest VM patching on Azure VMs using the new prerequisite. The steps to configure both the patching options on Arc VMs continue to remain the same.
15
+
This article is an overview on how to configure Schedule patching and Automatic guest VM patching on Azure VMs using the new prerequisite to ensure business continuity. The steps to configure both the patching options on Arc VMs continue to remain the same.
16
16
17
17
Currently, you can enable [Automatic guest VM patching](../virtual-machines/automatic-vm-guest-patching.md) (Autopatch) by setting the patch mode to **Azure-orchestrated** or **AutomaticByPlatform** on Azure portal and using REST API respectively, where patches are automatically applied during off-peak hours.
18
18
@@ -22,7 +22,7 @@ However, in certain cases, when you remove the schedule from a VM, there is a po
22
22
23
23
24
24
> [!IMPORTANT]
25
-
> For a seamless scheduled patching experience, you must ensure that the new VM propertyis enabled on all your Azure VMs (existing or new) that have schedules attached to them **before April 30, 2023**. Failing to update will give an error that the prerequisites aren't met.
25
+
> 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 **before May 12, 2023**. This setting will ensure machines are patched using your configured schedules and not autopatched. Failing to enable the pre-requisite will give an error that the prerequisites aren't met.
26
26
27
27
28
28
## Enable schedule patching on Azure VMs
@@ -31,9 +31,9 @@ However, in certain cases, when you remove the schedule from a VM, there is a po
31
31
32
32
**Prerequisite**
33
33
34
-
Patch orchestration = Azure-orchestrated with user managed schedules (Preview).
34
+
Patch orchestration = Customer managed schedules.
35
35
36
-
Select the patch orchestration option as **Azure-orchestrated with user managed schedules(Preview)**.
36
+
Select the patch orchestration option as **Customer managed schedules**.
37
37
The new patch orchestration option enables the following VM properties on your behalf after receiving your consent:
38
38
39
39
- Patch mode = Azure-orchestrated
@@ -60,15 +60,15 @@ To schedule patch the newly created VMs, follow the procedure from step 2 in **E
60
60
You can update the patch orchestration option for existing VMs that either already have schedules associated or are to be newly associated with a schedule:
61
61
62
62
> [!NOTE]
63
-
> If the **Patch orchestration** is set as *Azure-orchestrated or Azure-orchestrated Global safe deployment (AutomaticByPlatform)*, the **BypassPlatformSafetyChecksOnUserSchedule** is set to *False* and there is no schedule associated, the VM(s) will be autopatched.
63
+
> If the **Patch orchestration** is set as *Azure-orchestrated or Azure-orchestrated safe deployment (AutomaticByPlatform)*, the **BypassPlatformSafetyChecksOnUserSchedule** is set to *False* and there is no schedule associated, the VM(s) will be autopatched.
64
64
65
65
To update the patch mode, follow these steps:
66
66
67
67
1. Sign in to the [Azure portal](https://portal.azure.com)
68
68
1. Go to **Update management center (Preview)**, select **Update Settings**.
69
69
1. In **Change update settings**, select **+Add machine**.
70
70
1. In **Select resources**, select your VMs and then select **Add**.
71
-
1. In **Change update settings**, under **Patch orchestration**, select *Azure-orchestrated with user managed schedules(Preview)* and then select **Save**.
71
+
1. In **Change update settings**, under **Patch orchestration**, select *Customer managed schedules* and then select **Save**.
72
72
73
73
Attach a schedule after you complete the above steps.
74
74
@@ -79,55 +79,61 @@ Attach a schedule after you complete the above steps.
79
79
- Patch mode = AutomaticByPlatform
80
80
- BypassPlatformSafetyChecksOnUserSchedule = TRUE
81
81
82
-
**Enable for new VMs**
82
+
**Enable on Windows VMs**
83
83
84
84
```
85
-
PUT on `/subscriptions/subscription_id/resourceGroups/myResourceGroup/providers/Microsoft.Compute/virtualMachines/myVirtualMachine?api-version=2020-12-01`
85
+
PUT on `/subscriptions/subscription_id/resourceGroups/myResourceGroup/providers/Microsoft.Compute/virtualMachines/myVirtualMachine?api-version=2023-03-01`
86
86
```
87
87
88
88
```json
89
-
{
90
-
"location": "<location>",
91
-
"properties": {
92
-
"osProfile": {
93
-
"windowsConfiguration": {
94
-
"provisionVMAgent": true,
95
-
"enableAutomaticUpdates": true,
96
-
"patchSettings": {
97
-
"patchMode": "AutomaticByPlatform"
98
-
}
99
-
}
100
-
}
101
-
}
102
-
}
103
-
```
89
+
{
90
+
"location":"<location>",
91
+
"properties": {
92
+
"osProfile": {
93
+
"windowsConfiguration": {
94
+
"provisionVMAgent": true,
95
+
"enableAutomaticUpdates": true,
96
+
"patchSettings": {
97
+
"patchMode": "AutomaticByPlatform",
98
+
"automaticByPlatformSettings":{
99
+
"bypassPlatformSafetyChecksOnUserSchedule":true
100
+
}
101
+
}
102
+
}
103
+
}
104
+
}
105
+
}
104
106
105
-
**Enable for existing VMs**
107
+
```
108
+
**Enable on Linux VMs**
106
109
107
110
```
108
-
PUT on `/subscriptions/subscription_id/resourceGroups/myResourceGroup/providers/Microsoft.Compute/virtualMachines/myVirtualMachine?api-version=2020-12-01`
111
+
PUT on `/subscriptions/subscription_id/resourceGroups/myResourceGroup/providers/Microsoft.Compute/virtualMachines/myVirtualMachine?api-version=2023-03-01`
109
112
```
110
113
111
114
```json
112
-
{
113
-
"location": "<location>",
114
-
"properties": {
115
-
"osProfile": {
116
-
"windowsConfiguration": {
117
-
"provisionVMAgent": true,
118
-
"enableAutomaticUpdates": true,
119
-
"patchSettings": {
120
-
"patchMode": "AutomaticByPlatform"
121
-
}
122
-
}
123
-
}
124
-
}
125
-
}
115
+
{
116
+
117
+
"location":"<location>",
118
+
"properties": {
119
+
"osProfile": {
120
+
" linuxConfiguration": {
121
+
"provisionVMAgent": true,
122
+
"enableAutomaticUpdates": true,
123
+
"patchSettings": {
124
+
"patchMode": "AutomaticByPlatform",
125
+
"automaticByPlatformSettings":{
126
+
"bypassPlatformSafetyChecksOnUserSchedule":true
127
+
}
128
+
}
129
+
}
130
+
}
131
+
}
132
+
}
126
133
```
127
134
---
128
135
> [!NOTE]
129
136
> Currently, you can only enable the new prerequisite for schedule patching via Azure portal and REST API. It cannot be enabled via Azure CLI and PowerShell.
130
-
131
137
---
132
138
133
139
## Enable automatic guest VM patching on Azure VMs
@@ -162,7 +168,7 @@ To update the patch mode, follow these steps:
162
168
1. Go to **Update management center (Preview)**, select **Update Settings**.
163
169
1. In **Change update settings**, select **+Add machine**.
164
170
1. In **Select resources**, select your VMs and then select **Add**.
165
-
1. In **Change update settings**, under **Patch orchestration**, select *Azure-orchestrated Global safe deployment* and then select **Save**.
171
+
1. In **Change update settings**, under **Patch orchestration**, select *Azure-orchestrated-safe deployment* and then select **Save**.
166
172
167
173
168
174
# [REST API](#tab/auto-rest-api)
@@ -172,50 +178,57 @@ To update the patch mode, follow these steps:
PUT on `/subscriptions/subscription_id/resourceGroups/myResourceGroup/providers/Microsoft.Compute/virtualMachines/myVirtualMachine?api-version=2020-12-01`
184
+
PUT on `/subscriptions/subscription_id/resourceGroups/myResourceGroup/providers/Microsoft.Compute/virtualMachines/myVirtualMachine?api-version=2023-03-01`
179
185
```
180
186
181
187
```json
182
-
{
183
-
"location": "<location>",
184
-
"properties": {
185
-
"osProfile": {
186
-
"windowsConfiguration": {
187
-
"provisionVMAgent": true,
188
-
"enableAutomaticUpdates": true,
189
-
"patchSettings": {
190
-
"patchMode": "AutomaticByPlatform"
191
-
}
192
-
}
193
-
}
194
-
}
195
-
}
188
+
{
189
+
190
+
"location":"<location>",
191
+
"properties": {
192
+
"osProfile": {
193
+
"windowsConfiguration": {
194
+
"provisionVMAgent": true,
195
+
"enableAutomaticUpdates": true,
196
+
"patchSettings": {
197
+
"patchMode": "AutomaticByPlatform",
198
+
"automaticByPlatformSettings":{
199
+
"bypassPlatformSafetyChecksOnUserSchedule":false
200
+
}
201
+
}
202
+
}
203
+
}
204
+
}
205
+
}
196
206
```
197
207
198
-
**Enable for existing VMs**
208
+
**Enable on Linux VMs**
199
209
200
210
```
201
-
PUT on `/subscriptions/subscription_id/resourceGroups/myResourceGroup/providers/Microsoft.Compute/virtualMachines/myVirtualMachine?api-version=2020-12-01`
211
+
PUT on `/subscriptions/subscription_id/resourceGroups/myResourceGroup/providers/Microsoft.Compute/virtualMachines/myVirtualMachine?api-version=2023-03-01`
0 commit comments