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/virtual-machines/maintenance-configurations-portal.md
+1-21Lines changed: 1 addition & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,7 +32,7 @@ With Maintenance Configurations, you can now take more control over when to appl
32
32
1. In the Basics tab, choose a subscription and resource group, provide a name for the configuration, choose a region, and select one of the scopes we offer which you wish to apply updates for. Click **Add a schedule** to add or modify the schedule for your configuration.
33
33
34
34
> [!IMPORTANT]
35
-
> There are different **scopes** which support certain machine types and schedules, so please ensure you are selecting the right scope for your virtual machine.
35
+
> Certain virtual machine types and schedules will require a specific kind of scope. Check out [maintenance configuration scopes](maintenance-configurations.md#scopes) to find the right one for your virtual machine.
@@ -72,32 +72,12 @@ You can verify that the configuration was applied correctly or check to see any
72
72
73
73
74
74
75
-
<!-- You can also check the configuration for a specific virtual machine on its properties page. Click **Maintenance** to see the configuration assigned to that virtual machine.
76
-
77
-
 -->
78
-
79
75
## Check for pending updates
80
76
81
77
You can check if there are any updates pending for a maintenance configuration. In **Maintenance Configurations**, on the details for the configuration, click **Machines** and check **Maintenance status**.
82
78
83
79
84
80
85
-
<!-- You can also check a specific host using **Virtual Machines** or properties of the dedicated host.
86
-
87
-
 -->
88
-
89
-
<!-- ## Apply updates
90
-
91
-
You can apply pending updates on demand. On the VM or Azure Dedicated Host details, click **Maintenance** and click **Apply maintenance now**. Apply update calls can take upto 2 hours to complete.
92
-
93
-
94
-
95
-
## Check the status of applying updates
96
-
97
-
You can check on the progress of the updates for a configuration in **Maintenance Configurations** or using **Virtual Machines**. On the VM details, click **Maintenance**. In the following example, the **Maintenance state** shows an update is **Pending**.
98
-
99
-
 -->
100
-
101
81
## Delete a maintenance configuration
102
82
103
83
To delete a configuration, open the configuration details and click **Delete**.
Copy file name to clipboardExpand all lines: articles/virtual-machines/maintenance-configurations.md
+38-14Lines changed: 38 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,30 +8,54 @@ ms.topic: conceptual
8
8
ms.workload: infrastructure-services
9
9
ms.date: 10/06/2021
10
10
ms.author: cynthn
11
-
#pmcontact: shants
11
+
#pmcontact: pphillips
12
12
---
13
13
14
-
# Managing platform updates with Maintenance Configurations
14
+
# Managing VM updates with Maintenance Configurations
15
15
16
16
**Applies to:**:heavy_check_mark: Linux VMs :heavy_check_mark: Windows VMs :heavy_check_mark: Flexible scale sets :heavy_check_mark: Uniform scale sets
17
17
18
-
Manage platform updates, that don't require a reboot, using Maintenance Configurations. Azure frequently updates its infrastructure to improve reliability, performance, security or launch new features. Most updates are transparent to users. Some sensitive workloads, like gaming, media streaming, and financial transactions, can't tolerate even few seconds of a VM freezing or disconnecting for maintenance. Creating a Maintenance Configuration gives you the option to wait on platform updates and apply them within a 35-day rolling window.
18
+
Maintenance Configurations give you the ability to control and manage updates for many Azure virtual machine resources since Azure frequently updates its infrastructure to improve reliability, performance, security or launch new features. Most updates are transparent to users, but some sensitive workloads, like gaming, media streaming, and financial transactions, can't tolerate even few seconds of a VM freezing or disconnecting for maintenance. Maintenance configurations is integrated with Azure Resource Graph (ARG) for low latency and high scale customer experience.
19
19
20
+
>[!IMPORTANT]
21
+
> Users are required to have a role of at least contributor in order to use maintenance configurations.
20
22
21
-
With Maintenance Configurations, you can:
22
-
- Batch updates into one update package.
23
-
- Wait up to 35 days to apply updates for **Host** machines.
24
-
- Automate platform updates by configuring your maintenance schedule.
25
-
- Maintenance Configurations work across subscriptions and resource groups.
23
+
## Scopes
26
24
27
-
## Limitations
25
+
Maintenance Configurations currently supports three (3) scopes: Host, OS image, and Guest. While each scope allows scheduling and managing updates, the major difference lies in the resource they each support. This section outlines the details on the various scopes and their supported types:
28
26
29
-
- Maintenance window duration can vary month over month and sometimes it can take up to 2 hours to apply the pending updates once it is initiated by the user.
30
-
- After 35 days, an update will automatically be applied to your **Host** machines.
31
-
- Rack level maintenance cannot be controlled through maintenance configurations.
32
-
- User must have **Resource Contributor** access.
33
-
- Users need to know the nuances of the scopes required for their machine.
With this scope, you can manage platform updates that do not require a reboot on your *isolated VMs*, *isolated Virtual Machine Scale Set instances* and *dedicated hosts*. Some features and limitations unique to the host scope are:
37
+
38
+
- Schedules can be set anytime within 35 days. After 35 days, updates are automatically applied.
39
+
- A minimum of a 2 hour maintenance window is required for this scope.
40
+
41
+
[Learn more about Azure Dedicated Hosts](dedicated-hosts.md)
42
+
43
+
### OS image
44
+
Using this scope with maintenance configurations lets you decide when to apply upgrades to OS disks in your *virtual machine scale sets* through an easier and more predictable experience. An upgrade works by replacing the OS disk of a VM with a new disk created using the latest image version. Any configured extensions and custom data scripts are run on the OS disk, while data disks are retained. Some features and limitations unique to this scope are:
45
+
46
+
- Scale sets need to have [automatic OS upgrades](/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-automatic-upgrade.md) enabled in order to use maintenance configurations.
47
+
- Schedule recurrence is defaulted to daily
48
+
- A minimum of 5 hours is required for the maintenance window
49
+
50
+
### Guest
51
+
This scope is integrated with [update management center](../update-center/overview.md) which allows you to save recurring deployment schedules to install updates for your Windows Server and Linux machines in Azure, in on-premises environments, and in other cloud environments connected using Azure Arc-enabled servers. Some features and limitations unique to this scope include:
52
+
53
+
-[Patch orchestration](automatic-vm-guest-patching.md#patch-orchestration-modes) for virtual machines need to be set to AutomaticByPlatform
54
+
- A minimum of 1 hour and 10 minutes is required for the maintenance window.
55
+
- There is no limit to the recurrence of your schedule
56
+
57
+
To learn more about this topic, checkout [update management center and scheduled patching](../update-center/scheduled-patching.md)
58
+
35
59
## Management options
36
60
37
61
You can create and manage maintenance configurations using any of the following options:
0 commit comments