Merge pull request #96435 from MGoedtel/UpdateAAUM1119

updated paragraph about Saved Searches

Author: megvanhuygen

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

@@ -1,13 +1,13 @@
 ---
 title: Manage updates and patches for your Azure VMs
-description: This article provides an overview of how to use Azure Automation Update Management to manage updates and patches for your Azure Windows VMs.
+description: This article provides an overview of how to use Azure Automation Update Management to manage updates and patches for your Azure and non-Azure VMs.
 services: automation
-author: zjalexander
+author: mgoedtel
 ms.service: automation
 ms.subservice: update-management
 ms.topic: tutorial
-ms.date: 12/04/2018
-ms.author: zachal
+ms.date: 11/20/2019
+ms.author: magoedte
 ms.custom: mvc
 ---
 # Manage updates and patches for your Azure VMs
@@ -45,15 +45,15 @@ First, enable Update Management on your VM for this tutorial:
 1. Select the VM for which you want to enable Update Management.
 1. 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 an Azure Log Analytics workspace and linked Automation account, and whether the Update Management solution is in the workspace.
+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](../log-analytics/log-analytics-overview.md?toc=%2fazure%2fautomation%2ftoc.json) 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.
+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 Microsoft Monitoring Agent (MMA) 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.
+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](../log-analytics/log-analytics-overview.md?toc=%2fazure%2fautomation%2ftoc.json) workspace
+* [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)
 
@@ -65,9 +65,9 @@ Enabling the solution can take up to a few minutes. During this time, don't clos
 
 ## View update assessment
 
-After Update Management is enabled, the **Update management** pane opens. If any updates are missing, a list of missing updates is shown on the **Missing updates** tab.
+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.
 
-Under **INFORMATION LINK**, select the update link to open the support article for the update in a new window. You can learn important information about the update in this window.
+Under **INFORMATION LINK**, select the update link to open the support article for the update. You can learn important information about the update.
 
 ![View update status](./media/automation-tutorial-update-management/manageupdates-view-status-win.png)
 

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

@@ -1,18 +1,18 @@
 ---
 title: Use dynamic groups with Azure Update Management
-description: describes how dynamic groups work with Update Management
+description: This article describes how dynamic groups work with Azure Automation Update Management.
 services: automation
 ms.service: automation
 ms.subservice: update-management
-author: bobbytreed
-ms.author: robreed
-ms.date: 10/02/2019
+author: mgoedtel
+ms.author: magoedte
+ms.date: 11/20/2019
 ms.topic: conceptual
 manager: carmonm
 ---
 # Use dynamic groups with Update Management
 
-Update Management provides the ability to target a dynamic group of Azure or Non-Azure VMs for update deployments. These groups are evaluated at deployment time so you do not have to edit your deployment to add machines.
+Update Management provides the ability to target a dynamic group of Azure or non-Azure VMs for update deployments. These groups are evaluated at deployment time so you do not have to edit your deployment to add machines.
 
 ## Azure machines
 
@@ -31,7 +31,7 @@ To preview the results of a dynamic group, click the **Preview** button. This pr
 
 ## Non-Azure machines
 
-For Non-Azure machines, saved searches also referred to as computer groups are used to create the dynamic group. To learn how to create a saved search, see [Creating a computer group](../azure-monitor/platform/computer-groups.md#creating-a-computer-group). Once your group is created you can select it from the list of saved searches. Click **Preview** to preview the computers in the saved search at that time.
+For non-Azure machines, saved searches also referred to as computer groups, are used to create the dynamic group. To learn how to create a saved search, see [Creating a computer group](../azure-monitor/platform/computer-groups.md#creating-a-computer-group). Once your group is created you can select it from the list of saved searches. Click **Preview** to preview the computers in the saved search at that time.
 
 ![Select groups](./media/automation-update-management/select-groups-2.png)
 

articles/automation/manage-update-multi.md

@@ -1,12 +1,12 @@
 ---
 title: Manage updates for multiple Azure virtual machines
-description: This article describes how to manage updates for Azure virtual machines.
+description: This article describes how to manage updates for Azure and non-Azure virtual machines.
 services: automation
 ms.service: automation
 ms.subservice: update-management
-author: bobbytreed
-ms.author: robreed
-ms.date: 04/02/2019
+author: mgoedtel
+ms.author: magoedte
+ms.date: 11/20/2019
 ms.topic: conceptual
 manager: carmonm
 ---
@@ -25,6 +25,8 @@ To use Update Management, you need:
 
 - A virtual machine or computer with one of the supported operating systems installed.
 
+- Access to an update repository for Linux VMs onboarded to the solution.
+
 ## Supported operating systems
 
 Update Management is supported on the following operating systems:
@@ -33,18 +35,14 @@ Update Management is supported on the following operating systems:
 |---------|---------|
 |Windows Server 2008, Windows Server 2008 R2 RTM    | Supports only update assessments.         |
 |Windows Server 2008 R2 SP1 and later     |Windows PowerShell 4.0 or later is required. ([Download WMF 4.0](https://www.microsoft.com/download/details.aspx?id=40855))</br> Windows PowerShell 5.1 is recommended for increased reliability. ([Download WMF 5.1](https://www.microsoft.com/download/details.aspx?id=54616))         |
-|CentOS 6 (x86/x64) and 7 (x64)      | Linux agents must have access to an update repository.        |
-|Red Hat Enterprise 6 (x86/x64) and 7 (x64)     | Linux agents must have access to an update repository.        |
-|SUSE Linux Enterprise Server 11 (x86/x64) and 12 (x64)     | Linux agents must have access to an update repository.        |
-|Ubuntu 14.04 LTS, 16.04 LTS and 18.04 LTS (x86/x64)      |Linux agents must have access to an update repository.         |
+|CentOS 6 (x86/x64) and 7 (x64)      | |
+|Red Hat Enterprise 6 (x86/x64) and 7 (x64)     | |
+|SUSE Linux Enterprise Server 11 (x86/x64) and 12 (x64)     | |
+|Ubuntu 14.04 LTS, 16.04 LTS and 18.04 LTS (x86/x64)      | |
 
 > [!NOTE]
 > To prevent updates from being applied outside a maintenance window on Ubuntu, reconfigure the Unattended-Upgrade package to disable automatic updates. For more information, see the [Automatic Updates topic in the Ubuntu Server Guide](https://help.ubuntu.com/lts/serverguide/automatic-updates.html).
 
-Linux agents must have access to an update repository.
-
-This solution doesn't support a Log Analytics Agent for Linux that's configured to report to multiple Azure Log Analytics workspaces.
-
 ## Enable Update Management for Azure virtual machines
 
 In the Azure portal, open your Automation account, and then select **Update management**.
@@ -63,9 +61,7 @@ When onboarding is finished, Update Management is enabled for your virtual machi
 
 ## Enable Update Management for non-Azure virtual machines and computers
 
-To learn how to enable Update Management for non-Azure Windows virtual machines and computers, see [Connect Windows computers to the Azure Monitor service in Azure](../log-analytics/log-analytics-windows-agent.md).
-
-To learn how to enable Update Management for non-Azure Linux virtual machines and computers, see [Connect your Linux computers to Azure Monitor logs](../log-analytics/log-analytics-agent-linux.md).
+The Log Analytics agent for Windows and Linux needs to be installed on the VMs that are running on your corporate network or other cloud environment in order to enable them with Update Management. To learn the system requirements and supported methods to deploy the agent to machines hosted outside of Azure, see [Overview of the Log Analytics agent](../azure-monitor/platform/log-analytics-agent.md).
 
 ## View computers attached to your Automation account
 
@@ -124,8 +120,13 @@ In the **New update deployment** pane, specify the following information:
 
 - **Name**: Enter a unique name to identify the update deployment.
 - **Operating system**: Select **Windows** or **Linux**.
-- **Groups to update (preview)**: Define a query based on a combination of subscription, resource groups, locations, and tags to build a dynamic group of Azure VMs to include in your deployment. To learn more see, [Dynamic Groups](automation-update-management-groups.md)
-- **Machines to update**: Select a Saved Search, Imported group, or select Machines, to choose the machines that you want to update. If you choose **Machines**, the readiness of the machine is shown in the **UPDATE AGENT READINESS** column. You can see the health state of the machine before you schedule the update deployment. To learn about the different methods of creating computer groups in Azure Monitor logs, see [Computer groups in Azure Monitor logs](../azure-monitor/platform/computer-groups.md)
+- **Groups to update**: Define a query based on a combination of subscription, resource groups, locations, and tags to build a dynamic group of Azure VMs to include in your deployment. For non-Azure VMs, saved searches are used to create a dynamic group to include in your deployment. To learn more see, [Dynamic Groups](automation-update-management-groups.md).
+- **Machines to update**: Select a Saved Search, Imported group, or select Machines, to choose the machines that you want to update.
+
+   >[!NOTE]
+   >Selecting the Saved Search option does not return machine identities, only their names. If you have several VMs with the same name across multiple resource groups, they are returned in the results. Using the **Groups to update** option is recommended to ensure you include unique VMs matching your criteria.
+
+   If you choose **Machines**, the readiness of the machine is shown in the **UPDATE AGENT READINESS** column. You can see the health state of the machine before you schedule the update deployment. To learn about the different methods of creating computer groups in Azure Monitor logs, see [Computer groups in Azure Monitor logs](../azure-monitor/platform/computer-groups.md)
 
   ![New update deployment pane](./media/manage-update-multi/update-select-computers.png)
 
@@ -190,5 +191,5 @@ To see detailed information about any errors from the deployment, select **Error
 
 ## Next steps
 
-- To learn more about Update Management, including logs, output, and errors, see [Update Management solution in Azure](../operations-management-suite/oms-solution-update-management.md).
+To learn more about Update Management, including logs, output, and errors, see [Update Management solution in Azure](../operations-management-suite/oms-solution-update-management.md).