Merge pull request #115829 from MGoedtel/task1722886

Task1722886

Author: PRMerger18

articles/automation/automation-update-management.md

@@ -1,9 +1,9 @@
 ---
 title: Azure Automation Update Management overview
-description: Overview of the Update Management feature that manages updates for your Windows and Linux machines
+description: Overview of the Update Management feature that manages updates for your Windows and Linux machines.
 services: automation
 ms.subservice: update-management
-ms.date: 05/04/2020
+ms.date: 05/20/2020
 ms.topic: conceptual
 ---
 # Update Management overview
@@ -68,7 +68,7 @@ Having a machine registered for Update Management in more than one Log Analytics
 
 ### Supported client types
 
-The following table lists the supported operating systems for update assessments. Patching requires a Hybrid Runbook Worker. For information on Hybrid Runbook Worker requirements, see [Deploy a Windows Hybrid Runbook Worker](automation-windows-hrw-install.md) and a [Deploy a Linux Hybrid Runbook Worker](automation-linux-hrw-install.md).
+The following table lists the supported operating systems for update assessments. Patching requires a Hybrid Runbook Worker. For information on Hybrid Runbook Worker requirements, see [Deploy a Windows Hybrid Runbook Worker](automation-windows-hrw-install.md) and [Deploy a Linux Hybrid Runbook Worker](automation-linux-hrw-install.md).
 
 > [!NOTE]
 > Update assessment of Linux machines is only supported in certain regions as listed in the Automation account and Log Analytics workspace [mappings table](https://docs.microsoft.com/azure/automation/how-to/region-mappings#supported-mappings). 
@@ -92,10 +92,12 @@ The following table lists unsupported operating systems:
 
 |Operating system  |Notes  |
 |---------|---------|
-|Windows client     | Client operating systems (such as Windows 7 and Windows 10) aren't supported.        |
+|Windows client     | Client operating systems (such as Windows 7 and Windows 10) aren't supported.<br> For Azure Windows Virtual Desktop (WVD), the recommended method<br> to manage updates is [Windows Update for Business](https://docs.microsoft.com/windows/deployment/update/waas-manage-updates-wufb) for Windows 10 client machine patch management. |
 |Windows Server 2016 Nano Server     | Not supported.       |
 |Azure Kubernetes Service Nodes | Not supported. Use the patching process described in [Apply security and kernel updates to Linux nodes in Azure Kubernetes Service (AKS)](../aks/node-updates-kured.md)|
 
+
+
 ### Client requirements
 
 The following information describes operating system-specific client requirements. For additional guidance, see [Network planning](#ports).

articles/automation/how-to/move-account.md

@@ -22,16 +22,16 @@ The Automation account is one of the resources that you can move. In this articl
 4. Delete and re-create the Run As accounts.
 5. Re-enable your features.
 
-## Disable features
+## Remove features
 
-To unlink your workspace from your Automation account, you must disable the feature resources in your workspace:
+To unlink your workspace from your Automation account, you must remove the feature resources in your workspace:
 
 - Change Tracking and Inventory
 - Update Management
 - Start/Stop VMs during off-hours
 
 1. In the Azure portal, locate your resource group.
-2. Find each feature, and select **Delete** on the Delete Resources page.
+2. Find each feature, and select **Delete** on the **Delete Resources** page.
 
     ![Screenshot of deleting feature resources from the Azure portal](../media/move-account/delete-solutions.png)
 
@@ -121,7 +121,7 @@ You can now move your Automation account and its runbooks.
 
 ## Enable features
 
-After you re-create the Run As accounts, you must re-enable the features that you disabled before the move: 
+After you re-create the Run As accounts, you must re-enable the features that you removed before the move:
 
 1. To turn on Change Tracking and Inventory, select **Change Tracking and Inventory** in your Automation account. Choose the Log Analytics workspace that you moved over, and select **Enable**.
 

articles/automation/how-to/region-mappings.md

@@ -1,6 +1,6 @@
 ---
-title: Support regions for linked Log Analytics workspace
-description: This article tells how to support region mappings between an Automation account and a Log Analytics workspace.
+title: Supported regions for linked Log Analytics workspace
+description: This article describes the supported region mappings between an Automation account and a Log Analytics workspace.
 services: automation
 ms.service: automation
 ms.subservice: process-automation
@@ -11,7 +11,7 @@ ms.topic: conceptual
 manager: carmonm
 ---
 
-# Support regions for linked Log Analytics workspace
+# Supported regions for linked Log Analytics workspace
 
 In Azure Automation, you can enable the Update Management, Change Tracking and Inventory, and Start/Stop VMs during off-hours features for your VMs. However, only certain regions are supported for linking a Log Analytics workspace and an Automation account in your subscription. The region mappings only apply to the Automation account and the Log Analytics workspace. The Log Analytics workspace and Automation account must be in the same subscription, but can be in different resource groups deployed to the same region. For further information, see [Log Analytics workspace and Automation account](../../azure-monitor/insights/solutions.md#log-analytics-workspace-and-automation-account).
 
@@ -44,9 +44,9 @@ The following table shows the supported mappings:
 
 ## Unlink a workspace
 
-If you decide that you no longer want to integrate your Automation account with a Log Analytics workspace, you can unlink your account directly from the Azure portal. Before proceeding, you first need to [disable](move-account.md#disable-features) Update Management, Change Tracking and Inventory, and Start/Stop VMs during off-hours if you are using them. If you don't disable the features, you can't complete the unlinking operation. 
+If you decide that you no longer want to integrate your Automation account with a Log Analytics workspace, you can unlink your account directly from the Azure portal. Before proceeding, you first need to [remove](move-account.md#remove-features) Update Management, Change Tracking and Inventory, and Start/Stop VMs during off-hours if you are using them. If you don't remove them, you can't complete the unlinking operation. 
 
-With the features disabled, you can follow the steps below to unlink your Automation account.
+With the features removed, you can follow the steps below to unlink your Automation account.
 
 > [!NOTE]
 > Some features, including earlier versions of the Azure SQL monitoring solution, might have created Automation assets that need to be removed prior to unlinking the workspace.