|
| 1 | +--- |
| 2 | +title: Azure Update Manager operations |
| 3 | +description: This article tells what Azure Update Manager works in Azure is and the system updates for your Windows and Linux machines in Azure. |
| 4 | +ms.service: azure-update-manager |
| 5 | +ms.custom: linux-related-content |
| 6 | +author: SnehaSudhirG |
| 7 | +ms.author: sudhirsneha |
| 8 | +ms.date: 07/14/2024 |
| 9 | +ms.topic: overview |
| 10 | +--- |
| 11 | + |
| 12 | +# How Update Manager works |
| 13 | + |
| 14 | +Update Manager assesses and applies updates to all Azure machines and Azure Arc-enabled servers for both Windows and Linux. |
| 15 | + |
| 16 | + |
| 17 | + |
| 18 | +## Update Manager VM extensions |
| 19 | + |
| 20 | +When an Azure Update Manager operation(AUM) is enabled or triggered on your Azure or Arc-enabled server, AUM installs an [Azure extension](../virtual-machines/extensions/overview.md) or [Arc-enabled servers extensions](../azure-arc/servers/manage-vm-extensions.md) respectively on your machine to manage the updates. |
| 21 | + |
| 22 | +The extension is automatically installed on your machine when you initiate any Update Manager operation on your machine for the first time, such as Check for updates, Install one-time update, Periodic Assessment or when scheduled update deployment runs on your machine for the first time. |
| 23 | + |
| 24 | +Customer doesn't have to explicitly install the extension and its lifecycle as it is managed by Azure Update Manager including installation and configuration. The Update Manager extension is installed and managed by using the below agents, which are required for Update Manager to work on your machines: |
| 25 | + |
| 26 | +- [Azure VM Windows agent](../virtual-machines/extensions/agent-windows.md) or the [Azure VM Linux agent](../virtual-machines/extensions/agent-linux.md) for Azure VMs. |
| 27 | +- [Azure Arc-enabled servers agent](../azure-arc/servers/agent-overview.md) |
| 28 | + |
| 29 | +>[!NOTE] |
| 30 | +> Arc connectivity is a prerequisite for Update Manager, non-Azure machines including Arc-enabled VMWare, SCVMM etc. |
| 31 | +
|
| 32 | +For Azure machines, single extension is installed whereas for Azure Arc-enabled machines, two extensions are installed. Below are the details of extensions, which get installed: |
| 33 | + |
| 34 | +#### [Azure VM extensions](#tab/azure-vms) |
| 35 | + |
| 36 | +| Operating system| Extension |
| 37 | +|----------|-------------| |
| 38 | +|Windows | Microsoft.CPlat.Core.WindowsPatchExtension| |
| 39 | +|Linux | Microsoft.CPlat.Core.LinuxPatchExtension | |
| 40 | + |
| 41 | +#### [Azure Arc-enabled VM extensions](#tab/azure-arc-vms) |
| 42 | + |
| 43 | +| Operating system| Extension |
| 44 | +|----------|-------------| |
| 45 | +|Windows | Microsoft.CPlat.Core.WindowsPatchExtension (Periodic assessment) <br> Microsoft.SoftwareUpdateManagement.WindowsOsUpdateExtension (On-demand operations and Schedule patching) | |
| 46 | +|Linux | Microsoft.SoftwareUpdateManagement.LinuxOsUpdateExtension (On-demand operations and Schedule patching) <br> Microsoft.CPlat.Core.LinuxPatchExtension (Periodic assessment) | |
| 47 | + |
| 48 | +To view the available extensions for a VM in the Azure portal: |
| 49 | + |
| 50 | +1. Go to the [Azure portal](https://portal.azure.com) and select a VM. |
| 51 | +1. On the VM home page, under **Settings**, select **Extensions + applications**. |
| 52 | +1. On the **Extensions** tab, you can view the available extensions. |
| 53 | +--- |
| 54 | + |
| 55 | +### Update source |
| 56 | + |
| 57 | +Azure Update Manager honors the update source settings on the machine and will fetch updates accordingly. AUM doesn't publish or provide updates. |
| 58 | + |
| 59 | +#### [Windows](#tab/update-win) |
| 60 | + |
| 61 | +If the [Windows Update Agent (WUA)](https://learn.microsoft.com/windows/win32/wua_sdk/updating-the-windows-update-agent) is configured to fetch updates from Windows Update repository or Microsoft Update repository or [Windows Server Update Services](https://learn.microsoft.com/windows-server/administration/windows-server-update-services/get-started/windows-server-update-services-wsus) (WSUS), AUM will honor these settings. For more information, see how to [configure Windows Update client](https://learn.microsoft.com/windows-server/administration/windows-server-update-services/get-started/windows-server-update-services-wsus). By default, **it is configured to fetch updates from Windows Updates repository**. |
| 62 | + |
| 63 | +#### [Linux](#tab/update-lin) |
| 64 | + |
| 65 | +If the package manager points to a public YUM, APT or Zypper repository or a local repository, AUM will honor the settings of the package manager. |
| 66 | + |
| 67 | +--- |
| 68 | + |
| 69 | +AUM performs the following steps: |
| 70 | + |
| 71 | +- Retrieve the assessment information about status of system updates for it specified by the Windows Update client or Linux package manager. |
| 72 | +- Initiate the download and installation of updates with the Windows Update client or Linux package manager. |
| 73 | + |
| 74 | +>[!Note] |
| 75 | +> 1. The machines will report their update status based on the source they are configured to synchronize with. If the Windows Update service is configured to report to WSUS, the results in Update Manager might differ from what Microsoft Update shows, depending on when WSUS last synchronized with Microsoft Update. This behavior is the same for Linux machines that are configured to report to a local repository instead of a public package repository. |
| 76 | +> 1. Update Manager will only find updates that the Windows Update service finds when you select the local **Check for updates** button on the local Windows system. On Linux systems only updates on the local repository will be discovered. |
| 77 | +
|
| 78 | +### Updates data stored in Azure Resource Graph |
| 79 | + |
| 80 | +Update Manager extension pushes all the pending updates information and update installation results to [Azure Resource Graph](https://learn.microsoft.com/azure/governance/resource-graph/overview) where data is retained for below time periods: |
| 81 | + |
| 82 | +|Data | Retention period in Azure Resource graph | |
| 83 | +|------------------|---------------------------------------------------| |
| 84 | +|Pending updates (ARG table name: patchassessmentresources) | Seven Days| |
| 85 | +|Update installation results (ARG table name: patchinstallationresources)| 30 days| |
| 86 | + |
| 87 | +For more information, see [log structure of Azure Resource Graph](query-logs.md) and [sample queries](sample-query-logs.md). |
| 88 | + |
| 89 | +### How patches are installed in Azure Update Manager |
| 90 | + |
| 91 | +In Azure Update Manager, patches are installed in the following manner: |
| 92 | + |
| 93 | +1. It begins with a fresh assessment of the available updates on the VM. |
| 94 | +1. Update installation follows the assessment. |
| 95 | + - In Windows, the selected updates that meet the customer's criteria are installed one by one, |
| 96 | + - In Linux, they're installed in batches. |
| 97 | +1. During update installation, Maintenance window utilization is checked at multiple steps. For Windows and Linux, 10 and 15 minutes of the maintenance window are reserved for reboot at any point respectively. Before proceeding with the installation of the remaining updates, it checks whether the expected reboot time plus the average update installation time (for the next update or next set of updates) doesn't exceed the maintenance window. |
| 98 | +In the case of Windows, the average update installation time is 10 minutes for all types of updates except for service pack updates. For service pack updates, it’s 15 minutes. |
| 99 | +1. Note that an ongoing update installation (once started based on the calculation above) isn't forcibly stopped even if it exceeds the maintenance window, to avoid landing the machine in a possibly undetermined state. However, it doesn't continue installing the remaining updates once the maintenance window has been exceeded, and a maintenance window exceeded error is thrown in such cases. |
| 100 | +1. Patching/Update installation is only marked as successful if all selected updates are installed, and all operations involved (including Reboot & Assessment) succeed. Otherwise, it's marked as Failed or Completed with warnings. For example, |
| 101 | + |
| 102 | + |Scenario |Update installation status | |
| 103 | + |------------|---------------------------| |
| 104 | + |One of the selected updates fails to install.| Failed | |
| 105 | + |Reboot doesn't happen for any reason & wait time for reboot times out. | Failed | |
| 106 | + | Machine fails to start during a reboot. | Failed | |
| 107 | + | Initial or final assessment failed| Failed | |
| 108 | + | Reboot is required by the updates, but Never reboot option is selected. | Completed with warnings| |
| 109 | + | ESM packages skipped patching in ubuntu 18 or lower if Ubuntu pro license wasn't present. | Completed with warnings| |
| 110 | +1. An assessment is conducted at the end. Note that the reboot and assessment done at the end of the update installation may not occur in some cases, for example if the maintenance window has already been exceeded, if the update installation fails for some reason, etc. |
| 111 | + |
| 112 | +## Next steps |
| 113 | + |
| 114 | +- [Prerequisites of Update Manager](prerequisites.md) |
| 115 | +- [View updates for a single machine](view-updates.md). |
| 116 | +- [Deploy updates now (on-demand) for a single machine](deploy-updates.md). |
| 117 | +- [Enable periodic assessment at scale using policy](https://aka.ms/aum-policy-support). |
| 118 | +- [Schedule recurring updates](scheduled-patching.md) |
| 119 | +- [Manage update settings via the portal](manage-update-settings.md). |
| 120 | +- [Manage multiple machines by using Update Manager](manage-multiple-machines.md). |
0 commit comments