|
| 1 | +--- |
| 2 | +title: Patching guidance overview for Microsoft Configuration Manager to Azure |
| 3 | +description: Patching guidance overview for Microsoft Configuration Manager to Azure. View on how to get started with Azure Update Manager, mapping capabilities of MCM software and FAQs. |
| 4 | +author: snehasudhirG |
| 5 | +ms.service: azure-update-manager |
| 6 | +ms.topic: conceptual |
| 7 | +ms.date: 08/23/2023 |
| 8 | +ms.author: sudhirsneha |
| 9 | +--- |
| 10 | + |
| 11 | +# Guidance on patching while migrating from Microsoft Configuration Manager to Azure |
| 12 | + |
| 13 | +**Applies to:** :heavy_check_mark: Windows VMs :heavy_check_mark: Linux VMs :heavy_check_mark: On-premises environment :heavy_check_mark: Azure Arc-enabled servers. |
| 14 | + |
| 15 | +This article provides the details on how to patch your migrated virtual machines on Azure. |
| 16 | + |
| 17 | +Microsoft Configuration Manager (MCM) helps you to manage PCs and servers, keep software up-to-date, set configuration and security policies, and monitor system status. |
| 18 | + |
| 19 | + The [Azure Migration tool](https://learn.microsoft.com/mem/configmgr/core/support/azure-migration-tool) helps you to programmatically create Azure virtual machines (VMs) for Configuration Manager and installs the various site roles with default settings. The validation of new roles and removal of the on-premises site system role enables MCM to provide all the on-premises capabilities and experiences in Azure. |
| 20 | + |
| 21 | +Additionally, you can use the native [Azure Update Manager](overview.md) to manage and govern update compliance for Windows and Linux machines across your deployments in Azure, on-premises, and on the other cloud platforms, from a single dashboard, with no operational cost for managing the patching infrastructure. Azure Update Manager is similar to the update management component of MCM that is designed as a standalone Azure service to provide SaaS experience on Azure to manage hybrid environments. |
| 22 | + |
| 23 | +The MCM in Azure and Azure Update Manager can fulfill your patching requirements as per your requirement. |
| 24 | +- Using MCM, you can continue with the existing investments in MCM and the processes to maintain the patch update management cycle for Windows VMs. |
| 25 | +- Using Azure Update Manager, you can achieve a consistent management of VMs and operating system updates across your cloud and hybrid environments. You don't need to maintain Azure virtual machines for hosting the different Configuration Manager roles and don't need an MCM license thereby reducing the total cost for maintaining the patch update management cycle for all the machines in your environment. [Learn more](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/what-s-uup-new-update-style-coming-next-week/ba-p/3773065). |
| 26 | + |
| 27 | + |
| 28 | +## Manage software updates using Azure Update Manager |
| 29 | + |
| 30 | +1. Sign in to the [Azure portal](https://portal.azure.com) and search for Azure Update Manager (preview). |
| 31 | + |
| 32 | + :::image type="content" source="./media/guidance-migration-azure/update-manager-service-selection-inline.png" alt-text="Screenshot of selecting the Azure Update Manager from Azure portal." lightbox="./media/guidance-migration-azure/update-manager-service-selection-expanded.png"::: |
| 33 | + |
| 34 | +1. In the **Azure Update Manager (Preview)** home page, under **Manage** > **Machines**, select your subscription to view all your machines. |
| 35 | +1. Filter as per the available options to know the status of your specific machines. |
| 36 | + |
| 37 | + :::image type="content" source="./media/guidance-migration-azure/filter-machine-status-inline.png" alt-text="Screenshot of selecting the filters in Azure Update Manager to view the machines." lightbox="./media/guidance-migration-azure/filter-machine-status-expanded.png"::: |
| 38 | + |
| 39 | +1. Select the suitable [assessment](assessment-options.md) and [patching](updates-maintenance-schedules.md) options as per your requirement. |
| 40 | + |
| 41 | +## Map MCM capabilities to Azure Update Manager |
| 42 | + |
| 43 | +The following table explains the mapping capabilities of MCM software Update Management to Azure Update Manager. |
| 44 | + |
| 45 | +| **Capability** | **Microsoft Configuration Manager** | **Azure Update Manager**| |
| 46 | +| --- | --- | --- | |
| 47 | +|Synchronize software updates between sites(Central Admin site, Primary, Secondary sites)| The top site (either central admin site or stand-alone primary site) connects to Microsoft Update to retrieve software update. [Learn more](https://learn.microsoft.com/mem/configmgr/sum/understand/software-updates-introduction). After the top sites are synchronized, the child sites are synchronized. | There's no hierarchy of machines in Azure and therefore all machines connected to Azure receive updates from the source repository. | |
| 48 | +|Synchronize software updates/check for updates (retrieve patch metadata). | You can scan for updates periodically by setting configuration on the Software update point. [Learn more](https://learn.microsoft.com/mem/configmgr/sum/get-started/synchronize-software-updates#to-schedule-software-updates-synchronization). | You can enable periodic assessment to enable scan of patches every 24 hours. [Learn more](assessment-options.md). | |
| 49 | +|Configuring classifications/products to synchronize/scan/assess | You can choose the update classifications (security or critical updates) to synchronize/scan/assess. [Learn more](https://learn.microsoft.com/mem/configmgr/sum/get-started/configure-classifications-and-products). | There's no such capability here. The entire software metadata is scanned.| |
| 50 | +|Deploy software updates (install patches)| Provides three modes of deploying updates: </br> Manual deployment </br> Automatic deployment </br> Phased deployment [Learn more](https://learn.microsoft.com/mem/configmgr/sum/deploy-use/deploy-software-updates).| Manual deployment is mapped to deploying [one-time updates](deploy-updates.md) and Automatic deployment is mapped to [scheduled updates](scheduled-patching.md). (The [Automatic Deployment Rules (ADRs)](https://learn.microsoft.com/mem/configmgr/sum/deploy-use/automatically-deploy-software-updates#BKMK_CreateAutomaticDeploymentRule) can be mapped to schedules). There's no phased deployment option. | |
| 51 | + |
| 52 | +## Limitations in Azure Update Manager (preview) |
| 53 | + |
| 54 | +The following are the current limitations: |
| 55 | + |
| 56 | +- **Orchestration groups with Pre/Post scripts** - [Orchestration groups](https://learn.microsoft.com/mem/configmgr/sum/deploy-use/orchestration-groups) can't be created in Azure Update Manager to specify a maintenance sequence, allow some machines for updates at the same time and so on. (The orchestration groups allow you to use the pre/post scripts to run tasks before and after a patch deployment). |
| 57 | + |
| 58 | +### Patching machines |
| 59 | +After you set up configurations for assessment and patching, you can deploy/install either through [on-demand updates](deploy-updates.md) (one time or manual update) or [schedule updates](scheduled-patching.md) (automatic update) only. You can also deploy updates using [Azure Update Manager's API](manage-vms-programmatically.md). |
| 60 | + |
| 61 | +## Frequently asked questions |
| 62 | + |
| 63 | +### Where does Azure Update Manager get its updates from? |
| 64 | + |
| 65 | +Azure Update Manager refers to the repository that the machines point to. Most Windows machines by default point to the Windows Update catalog and Linux machines are configured to get updates from the `apt` or `yum` repositories. If the machines point to another repository such as [WSUS](https://learn.microsoft.com/windows-server/administration/windows-server-update-services/get-started/windows-server-update-services-wsus) or a local repository then Azure Update Manager gets the updates from that repository. |
| 66 | + |
| 67 | +### Can Azure Update Manager patch OS, SQL and Third party software? |
| 68 | + |
| 69 | +Azure Update Manager refers to the repositories that the VMs point to. If the repository contains third party and SQL patches, Azure Update Manager can install SQL and third party patches. |
| 70 | +> [!NOTE] |
| 71 | +> By default, Windows VMs point to Windows Update repository that does not contain SQL and third party patches. If the VMs point to Microsoft Update, Azure Update Manager will patch OS, SQL, and third party updates. |
| 72 | +
|
| 73 | +### Do I need to configure WSUS to use Azure Update Manager? |
| 74 | + |
| 75 | +You don't need WSUS to deploy patches in Azure Update Manager. Typically, all the machines connect to the internet repository to get updates (unless the machines point to WSUS or local repository that isn't connected to the internet). [Learn more](https://learn.microsoft.com/mem/configmgr/sum/). |
| 76 | + |
| 77 | +## Next steps |
| 78 | +- [An overview on Azure Update Manager](overview.md) |
| 79 | +- [Check update compliance](view-updates.md) |
| 80 | +- [Deploy updates now (on-demand) for single machine](deploy-updates.md) |
| 81 | +- [Schedule recurring updates](scheduled-patching.md) |
0 commit comments