Merge pull request #106491 from MGoedtel/task1665806e

updated articles to fix image and steps

Author: PRMerger14

articles/automation/automation-onboard-solutions-from-automation-account.md

@@ -16,7 +16,7 @@ Sign in to Azure at https://portal.azure.com
 
 ## Enable solutions
 
-Navigate to your Automation account and select either **Inventory** or **Change tracking** under **CONFIGURATION MANAGEMENT**.
+Navigate to your Automation account and select either **Inventory** or **Change tracking** under **Configuration Management**.
 
 Choose the Log Analytics workspace and Automation account and click **Enable** to enable the solution. The solution takes up to 15 minutes to enable.
 
@@ -29,17 +29,17 @@ Choose the Log Analytics workspace and Automation account and click **Enable** t
 
 The Change Tracking and Inventory solution provides the ability to [track changes](automation-vm-change-tracking.md) and [inventory](automation-vm-inventory.md) on your virtual machines. In this step, you enable the solution on a virtual machine.
 
-When the change tracking and inventory solution onboarding notification completes, click on **Update Management** under **CONFIGURATION MANAGEMENT**.
+When the change tracking and inventory solution onboarding notification completes, select **Update management** under **Update management**.
 
-The Update Management solution allows you to manage updates and patches for your Azure Windows VMs. You can assess the status of available updates, schedule installation of required updates, and review deployment results to verify updates were applied successfully to the VM. This action enabled the solution for your VM.
+The Update Management solution allows you to manage updates and patches for your Azure and hybrid VMs. You can assess the status of available updates, schedule installation of required updates, and review deployment results to verify updates were applied successfully to them.
 
-Select **Update management** under **UPDATE MANAGEMENT**. The Log Analytics workspace selected is the same workspace used in the preceding step. Click **Enable** to onboard the Update management solution. The solution takes up to 15 minutes to enable.
+On the enable solution page, the Log Analytics workspace selected is the same workspace used in the preceding step. Click **Enable** to onboard the Update Management solution. The solution takes up to 15 minutes to enable.
 
 ![Onboard update solution](media/automation-onboard-solutions-from-automation-account/onboardsolutions2.png)
 
 ## Scope Configuration
 
-Each solution uses a Scope Configuration within the workspace to target the computers that get the solution. The Scope Configuration is a group of one or more saved searches that is used to limit the scope of the solution to specific computers. To access the Scope Configurations, in your Automation account under **RELATED RESOURCES**, select **Workspace**. Then in the workspace under **WORKSPACE DATA SOURCES**, select **Scope Configurations**.
+Each solution uses a Scope Configuration within the workspace to target the computers that get the solution. The Scope Configuration is a group of one or more saved searches that is used to limit the scope of the solution to specific computers. To access the Scope Configurations, in your Automation account under **Related resources**, select **Workspace**. Then in the workspace under **Workspace data sources**, select **Scope Configurations**.
 
 If the selected workspace doesn't have the Update Management or Change Tracking solutions yet, the following scope configurations are created:
 
@@ -66,21 +66,21 @@ Select either saved search to view the query used to populate the group. The fol
 
 ## Onboard Azure VMs
 
-From your Automation account select **Inventory** or **Change tracking** under **CONFIGURATION MANAGEMENT**, or **Update management** under **UPDATE MANAGEMENT**.
+From your Automation account select **Inventory** or **Change tracking** under **Configuration Management**, or **Update management** under **Update management**.
 
 Click **+ Add Azure VMs**, select one or more VMs from the list. Virtual machines that can't be enabled are greyed out and unable to be selected. Azure VMs can exist in any region no matter the location of your Automation Account. On the **Enable Update Management** page, click **Enable**. This action adds the selected VMs to the computer group saved search for the solution.
 
 ![Enable Azure VMs](media/automation-onboard-solutions-from-automation-account/enable-azure-vms.png)
 
 ## Onboard a non-Azure machine
 
-Machines not in Azure need to be added manually. From your Automation account select **Inventory** or **Change tracking** under **CONFIGURATION MANAGEMENT**, or **Update management** under **UPDATE MANAGEMENT**.
+Machines not in Azure need to be added manually. From your Automation account select **Inventory** or **Change tracking** under **Configuration Management**, or **Update management** under **Update management**.
 
 Click **Add non-Azure machine**. This action opens up a new browser window with the [instructions on how to install and configure the Microsoft Monitoring Agent on the machine](../azure-monitor/platform/log-analytics-agent.md) so the machine can begin reporting to the solution. If you're onboarding a machine that currently managed by System Center Operations Manager, a new agent isn't required, the workspace information is entered into the existing agent.
 
 ## Onboard machines in the workspace
 
-Manually installed machines or machines already reporting to your workspace must to be added to Azure Automation for the solution to be enabled. From your Automation account select **Inventory** or **Change tracking** under **CONFIGURATION MANAGEMENT**, or **Update management** under **UPDATE MANAGEMENT**.
+Manually installed machines or machines already reporting to your workspace must to be added to Azure Automation for the solution to be enabled. From your Automation account select **Inventory** or **Change tracking** under **Configuration Management**, or **Update management** under **Update management**.
 
 Select **Manage machines**. This action opens up the **Manage Machines** page. This page allows you to enable the solution on a select set of machines, all available machines, or enable the solution for all current machines and enable it on all future machines. The **Manage machines** button may be greyed out if you previously chose the option **Enable on all available and future machines**.
 
@@ -98,7 +98,7 @@ You can add the Scope Configurations back by adding the initial saved searches b
 
 ### Selected machines
 
-To enable the solution for one or more machines, select **Enable on selected machines** and click **add** next to each machine you want to add to the solution. This task adds the selected machine names to the computer group saved search query for the solution.
+To enable the solution for one or more machines, select **Enable on selected machines** and click **Add** next to each machine you want to add to the solution. This task adds the selected machine names to the computer group saved search query for the solution.
 
 ## Unlink workspace
 
@@ -127,9 +127,9 @@ After you remove these solutions, you can complete the following steps to unlink
 
 If you used the Update Management solution, optionally you may want to remove the following items that are no longer needed after you remove the solution.
 
-* Update schedules - Each will have names that match the update deployments you created)
+* Update schedules - Each will have names that match the update deployments you created.
 
-* Hybrid worker groups created for the solution -  Each will be named similarly to  machine1.contoso.com_9ceb8108-26c9-4051-b6b3-227600d715c8).
+* Hybrid worker groups created for the solution -  Each will be named similarly to machine1.contoso.com_9ceb8108-26c9-4051-b6b3-227600d715c8).
 
 If you used the Start and Stop VMs during off-hours solution, optionally you may want to remove the following items that are no longer needed after you remove the solution.
 

articles/automation/automation-onboard-solutions-from-vm.md

@@ -2,7 +2,7 @@
 title: Onboard Update Management, Change Tracking, and Inventory solutions from an Azure VM
 description: Learn how to onboard an Azure virtual machine with Update Management, Change Tracking, and Inventory solutions that are part of Azure Automation.
 services: automation
-ms.date: 03/20/2019
+ms.date: 03/04/2020
 ms.topic: conceptual
 ms.custom: mvc
 ---
@@ -17,13 +17,17 @@ Sign in to the Azure portal at https://portal.azure.com.
 
 ## Enable the solutions
 
-Go to an existing virtual machine. Under **OPERATIONS**, select **Update management**, **Inventory**, or **Change tracking**. The virtual machine can exist in any region no matter the location of your Automation Account. When onboarding a solution from a VM you need to have the `Microsoft.OperationalInsights/workspaces/read` permission to determine if the VM is onboarded to a workspace. To learn about additional permissions that are needed in general, see [permissions needed to onboard machines](automation-role-based-access-control.md#onboarding).
+First, enable one or all three of the solutions on your VM:
 
-To enable the solution for the VM only, ensure that **Enable for this VM** is selected. To onboard multiple machines to the solution, select **Enable for VMs in this subscription**, and then select **Click to select machines to enable**. To learn how to onboard multiple machines at once, see [Onboard Update Management, Change Tracking, and Inventory solutions](automation-onboard-solutions-from-automation-account.md).
+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 a solution for.
+3. On the VM page, under **Operations**, select **Update management**, **Inventory**, or **Change tracking**. The virtual machine can exist in any region no matter the location of your Automation account. When onboarding a solution from a VM, you need to have the `Microsoft.OperationalInsights/workspaces/read` permission to determine if the VM is onboarded to a workspace. To learn about additional permissions that are required, see [permissions needed to onboard machines](automation-role-based-access-control.md#onboarding).
+
+To learn how to onboard multiple machines at once, see [Onboard Update Management, Change Tracking, and Inventory solutions](automation-onboard-solutions-from-automation-account.md).
 
 Select the Azure Log Analytics workspace and Automation account, and then select **Enable** to enable the solution. The solution takes up to 15 minutes to enable.
 
-![Onboard the Update Management solution](media/automation-onboard-solutions-from-vm/onboard-solution.png)
+![Onboard the Update Management solution](media/automation-tutorial-update-management/manageupdates-update-enable.png)
 
 Go to the other solutions, and then select **Enable**. The Log Analytics workspace and Automation account drop-down lists are disabled because these solutions use the same workspace and Automation account as the previously enabled solution.
 
@@ -32,7 +36,7 @@ Go to the other solutions, and then select **Enable**. The Log Analytics workspa
 
 ## Scope configuration
 
-Each solution uses a scope configuration in the workspace to target the computers that get the solution. The scope configuration is a group of one or more saved searches that are used to limit the scope of the solution to specific computers. To access the scope configurations, in your Automation account, under **RELATED RESOURCES**, select **Workspace**. In the workspace, under **WORKSPACE DATA SOURCES**, select **Scope Configurations**.
+Each solution uses a scope configuration in the workspace to target the computers that get the solution. The scope configuration is a group of one or more saved searches that are used to limit the scope of the solution to specific computers. To access the scope configurations, in your Automation account, under **Related resources**, select **Workspace**. In the workspace, under **Workspace data sources**, select **Scope Configurations**.
 
 If the selected workspace doesn't already have the Update Management or Change Tracking solutions, the following scope configurations are created:
 
@@ -86,9 +90,9 @@ After you remove these solutions, you can perform the following steps to unlink
 
 If you used the Update Management solution, optionally you may want to remove the following items that are no longer needed after you remove the solution.
 
-* Update schedules - Each will have names that match the update deployments you created)
+* Update schedules - Each will have names that match the update deployments you created.
 
-* Hybrid worker groups created for the solution -  Each will be named similarly to  machine1.contoso.com_9ceb8108-26c9-4051-b6b3-227600d715c8).
+* Hybrid worker groups created for the solution -  Each will be named similarly to machine1.contoso.com_9ceb8108-26c9-4051-b6b3-227600d715c8).
 
 If you used the Start/Stop VMs during off-hours solution, optionally you may want to remove the following items that are no longer needed after you remove the solution.
 
@@ -110,5 +114,7 @@ To remove a VM from Update Management:
 Continue to the tutorials for the solutions to learn how to use them:
 
 * [Tutorial - Manage updates for your VM](automation-tutorial-update-management.md)
+
 * [Tutorial - Identify software on a VM](automation-tutorial-installed-software.md)
+
 * [Tutorial - Troubleshoot changes on a VM](automation-tutorial-troubleshoot-changes.md)