|
| 1 | +--- |
| 2 | +title: Maintenance control for Azure virtual machines using the Azure portal |
| 3 | +description: Learn how to control when maintenance is applied to your Azure VMs using Maintenance control and the Azure portal. |
| 4 | +author: cynthn |
| 5 | +ms.service: virtual-machines |
| 6 | +ms.topic: article |
| 7 | +ms.workload: infrastructure-services |
| 8 | +ms.date: 04/22/2020 |
| 9 | +ms.author: cynthn |
| 10 | +#pmcontact: shants |
| 11 | +--- |
| 12 | + |
| 13 | +# Control updates with Maintenance Control and the Azure portal |
| 14 | + |
| 15 | +Maintenance control lets you decide when to apply updates to your isolated VMs and Azure dedicated hosts. This topic covers the Azure portal options for Maintenance control. For more about benefits of using Maintenance control, its limitations, and other management options, see [Managing platform updates with Maintenance Control](maintenance-control.md). |
| 16 | + |
| 17 | +## Create a maintenance configuration |
| 18 | + |
| 19 | +1. Sign in to the Azure portal. |
| 20 | + |
| 21 | +1. Search for **Maintenance Configurations**. |
| 22 | + |
| 23 | +  |
| 24 | + |
| 25 | +1. Click **Add**. |
| 26 | + |
| 27 | +  |
| 28 | + |
| 29 | +1. Choose a subscription and resource group, provide a name for the configuration, and choose a region. Click **Next**. |
| 30 | + |
| 31 | +  |
| 32 | + |
| 33 | +1. Add tags and values. Click **Next**. |
| 34 | + |
| 35 | +  |
| 36 | + |
| 37 | +1. Review the summary. Click **Create**. |
| 38 | + |
| 39 | +  |
| 40 | + |
| 41 | +1. After the deployment is complete, click **Go to resource**. |
| 42 | + |
| 43 | +  |
| 44 | + |
| 45 | +## Assign the configuration |
| 46 | + |
| 47 | +On the details page of the maintenance configuration, click Assignments and then click **Assign resource**. |
| 48 | + |
| 49 | + |
| 50 | + |
| 51 | +Select the resources that you want the maintenance configuration assigned to and click **Ok**. The **Type** column shows whether the resource is an isolated VM or Azure dedicated host. The VM needs to be running to assign the configuration. An error occurs if you try to assign a configuration to a VM that is stopped. |
| 52 | + |
| 53 | +<!---Shantanu to add details about the error case---> |
| 54 | + |
| 55 | + |
| 56 | + |
| 57 | +## Check configuration |
| 58 | + |
| 59 | +You can verify that the configuration was applied correctly or check to see any maintenance configuration that is currently assigned using **Maintenance Configurations**. The **Type** column shows whether the configuration is assigned to an isolated VM or Azure dedicated host. |
| 60 | + |
| 61 | + |
| 62 | + |
| 63 | +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. |
| 64 | + |
| 65 | + |
| 66 | + |
| 67 | +## Check for pending updates |
| 68 | + |
| 69 | +There are also two ways to check if updates are pending for a maintenance configuration. In **Maintenance Configurations**, on the details for the configuration, click **Assignments** and check **Maintenance status**. |
| 70 | + |
| 71 | + |
| 72 | + |
| 73 | +You can also check a specific host using **Virtual Machines** or properties of the dedicated host. |
| 74 | + |
| 75 | + |
| 76 | + |
| 77 | +## Apply updates |
| 78 | + |
| 79 | +You can apply pending updates on demand using **Virtual Machines**. On the VM details, click **Maintenance** and click **Apply maintenance now**. |
| 80 | + |
| 81 | + |
| 82 | + |
| 83 | +## Check the status of applying updates |
| 84 | + |
| 85 | +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**. |
| 86 | + |
| 87 | + |
| 88 | + |
| 89 | +## Delete a maintenance configuration |
| 90 | + |
| 91 | +To delete a configuration, open the configuration details and click **Delete**. |
| 92 | + |
| 93 | + |
| 94 | + |
| 95 | + |
| 96 | +## Next steps |
| 97 | + |
| 98 | +To learn more, see [Maintenance and updates](maintenance-and-updates.md). |
0 commit comments