Merge pull request #106571 from MGoedtel/UpdateUM34b

updated tutorial and overview article

Author: PRMerger20

articles/automation/automation-tutorial-update-management.md

@@ -16,7 +16,6 @@ For pricing information, see [Automation pricing for Update Management](https://
 In this tutorial, you learn how to:
 
 > [!div class="checklist"]
-> * Onboard a VM for Update Management
 > * View an update assessment
 > * Configure alerting
 > * Schedule an update deployment
@@ -26,40 +25,13 @@ In this tutorial, you learn how to:
 
 To complete this tutorial, you need:
 
-* An Azure subscription. If you don't have one yet, you can [activate your monthly Azure credit for Visual Studio subscribers](https://azure.microsoft.com/pricing/member-offers/msdn-benefits-details/) or sign up for a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
-* An [Azure Automation account](automation-offering-get-started.md) to hold the watcher and action runbooks and the Watcher Task.
+* The [Update Management](automation-update-management.md) solution enabled for one or more of your VMs.
 * A [virtual machine](../virtual-machines/windows/quick-create-portal.md) to onboard.
 
 ## Sign in to Azure
 
 Sign in to the Azure portal at https://portal.azure.com.
 
-## Enable Update Management
-
-First, enable Update Management on your VM for this tutorial:
-
-1. In the [Azure portal](https://portal.azure.com), from the left-hand pane select **Virtual machines** or search for and select **Virtual machines** from the **Home** page.
-2. Select the VM for which you want to enable Update Management.
-3. On the VM page, under **Operations**, select **Update management**. The **Enable Update management** pane opens.
-
-Validation is performed to determine whether Update Management is enabled for this VM. This validation includes checks for a Log Analytics workspace and linked Automation account, and whether the Update Management solution is enabled in the workspace.
-
-A [Log Analytics](../azure-monitor/platform/data-platform-logs.md) workspace is used to collect data that's generated by features and services like Update Management. The workspace provides a single location to review and analyze data from multiple sources.
-
-The validation process also checks to see whether the VM is provisioned with the Log Analytics agent and Automation Hybrid Runbook Worker. This agent is used to communicate with Azure Automation and to obtain information about the update status. The agent requires port 443 to be open to communicate with the Azure Automation service and to download updates.
-
-If any of the following prerequisites were found to be missing during onboarding, they're automatically added:
-
-* [Log Analytics](../azure-monitor/platform/data-platform-logs.md) workspace
-* An [Automation account](./automation-offering-get-started.md)
-* A [Hybrid Runbook Worker](./automation-hybrid-runbook-worker.md) enabled on the VM
-
-Under **Update management**, set the location, Log Analytics workspace, and Automation account to use. Then, select **Enable**. If these options aren't available, it means that another Automation solution is enabled for the VM. In that case, the same workspace and Automation account must be used.
-
-![Enable the Update Management solution window](./media/automation-tutorial-update-management/manageupdates-update-enable.png)
-
-Enabling the solution can take several minutes. During this time, don't close the browser window. After the solution is enabled, information about missing updates on the VM flows to Azure Monitor logs. It can take between 30 minutes and 6 hours for the data to be available for analysis.
-
 ## View update assessment
 
 After Update Management is enabled, the **Update management** pane opens. If any updates are identified as missing, a list of missing updates is shown on the **Missing updates** tab.

articles/automation/automation-update-management.md

@@ -21,10 +21,10 @@ You can enable Update Management for virtual machines (VMs) using the following
 > [!NOTE]
 > The Update Management solution requires linking a Log Analytics workspace to your Automation account. For a definitive list of supported regions, see [Azure Workspace mappings](./how-to/region-mappings.md). The region mappings don't affect the ability to manage VMs in a separate region from your Automation account.
 
-An Azure [Resource Manager template](automation-update-management-deploy-template.md) is available that enables you to deploy the Update Management solution to a new or existing Automation account and Log Analytics workspace in your subscription.
-
 [!INCLUDE [azure-monitor-log-analytics-rebrand](../../includes/azure-monitor-log-analytics-rebrand.md)]
 
+An Azure [Resource Manager template](automation-update-management-deploy-template.md) is available that enables you to deploy the Update Management solution to a new or existing Automation account and Log Analytics workspace in your subscription.
+
 ## Solution overview
 
 Machines that are managed by Update Management use the following configurations to perform assessment and to update deployments:
@@ -59,7 +59,7 @@ The scheduled deployment defines which target machines receive the applicable up
 
 You also specify a schedule to approve and set a time period during which updates can be installed. This period is called the maintenance window. A 20-minute span of the maintenance window is reserved for reboots, assuming one is needed and you selected the appropriate reboot option. If patching takes longer than expected and there's less than 20 minutes in the maintenance window, a reboot won't occur.
 
-Updates are installed by runbooks in Azure Automation. You can't view these runbooks, and they don’t require any configuration. When an update deployment is created, it creates a schedule that starts a master update runbook at the specified time for the included machines. The master runbook starts a child runbook on each agent to install the required updates.
+Updates are installed by runbooks in Azure Automation. You can't view these runbooks, and they don't require any configuration. When an update deployment is created, it creates a schedule that starts a master update runbook at the specified time for the included machines. The master runbook starts a child runbook on each agent to install the required updates.
 
 At the date and time specified in the update deployment, the target machines execute the deployment in parallel. Before installation, a scan is run to verify that the updates are still required. For WSUS client machines, if the updates aren't approved in WSUS, update deployment fails.
 
@@ -243,10 +243,15 @@ Update Management relies on the locally configured update repository to update s
 
 To begin updating systems, you need to enable the Update Management solution. The following are the recommended and supported methods to onboard the solution:
 
-* [From a virtual machine](automation-onboard-solutions-from-vm.md)
-* [From browsing multiple machines](automation-onboard-solutions-from-browse.md)
-* [From your Automation account](automation-onboard-solutions-from-automation-account.md)
-* [With an Azure Automation runbook](automation-onboard-solutions.md)
+- [From a virtual machine](automation-onboard-solutions-from-vm.md)
+
+- [From browsing multiple machines](automation-onboard-solutions-from-browse.md)
+
+- [From your Automation account](automation-onboard-solutions-from-automation-account.md)
+
+- [With an Azure Automation runbook](automation-onboard-solutions.md)
+
+- [With an Azure Resource Manager template](automation-update-management-deploy-template.md)
 
 ## Next steps