Merge pull request #116698 from BethWilke/branch205

GitHubber17 · web-flow · commit b7518da93e03 · 2020-05-27T13:52:45.000-07:00
Multiple file changes
diff --git a/articles/automation/automation-create-standalone-account.md b/articles/automation/automation-create-standalone-account.md
@@ -25,7 +25,7 @@ With this account created for you, you can quickly start building and deploying
 To create or update an Automation account, and to complete the tasks described in this article, you must have the following privileges and permissions:
 
 * To create an Automation account, your Azure AD user account must be added to a role with permissions equivalent to the Owner role for `Microsoft.Automation` resources. For more information, see [Role-Based Access Control in Azure Automation](automation-role-based-access-control.md).
-* In the Azure portal, under **Azure Active Directory** > **MANAGE** > **User settings**, if **App registrations** is set to **Yes**, non-administrator users in your Azure AD tenant can [register Active Directory applications](../active-directory/develop/howto-create-service-principal-portal.md#check-azure-subscription-permissions). If **App registrations** is set to **No**, the user who performs this action must be a global administrator in Azure AD.
+* In the Azure portal, under **Azure Active Directory** > **MANAGE** > **User settings**, if **App registrations** is set to **Yes**, non-administrator users in your Azure AD tenant can [register Active Directory applications](../active-directory/develop/howto-create-service-principal-portal.md#check-azure-subscription-permissions). If **App registrations** is set to **No**, the user who performs this action must have at least an Application Developer role in Azure AD.
 
 If you aren't a member of the subscription's Active Directory instance before you're added to the subscription's global Administrator/Coadministrator role, you're added to Active Directory as a guest. In this scenario, you see this message on the Add Automation Account pane: `You do not have permissions to create.`
 
diff --git a/articles/automation/automation-enable-changes-from-auto-acct.md b/articles/automation/automation-enable-changes-from-auto-acct.md
@@ -31,17 +31,17 @@ Sign in to Azure at https://portal.azure.com.
 
     ![Enable Change Tracking and Inventory](media/automation-enable-changes-from-auto-acct/onboardsolutions.png)
 
-## <a name="scope-configuration"></a>Check the scope configuration
+## <a name="scope-configuration"></a>Limit the scope for the deployment
 
-Change Tracking and Inventory uses a scope configuration within the workspace to target the computers to receive changes. The scope configuration is a group of one or more saved searches that is used to limit the scope of the feature to specific computers. For more information, see [Work with scope configurations for Change Tracking and Inventory](automation-scope-configurations-change-tracking.md).
+Change Tracking and Inventory uses a scope configuration within the workspace to target the computers to receive changes. For more information, see [Limit Change Tracking and Inventory deployment scope](automation-scope-configurations-change-tracking.md).
 
 ## Enable Azure VMs
 
 1. From your Automation account, select **Inventory** or **Change tracking** under **Configuration Management**.
 
 2. Click **+ Add Azure VMs** and select one or more VMs from the list. Virtual machines that can't be enabled are grayed out and unable to be selected. Azure VMs can exist in any region no matter the location of your Automation account. 
 
-3. Click **Enable** to add the selected VMs to the computer group saved search for the feature. For more information, see [Work with scope configurations for Change Tracking and Inventory](automation-scope-configurations-change-tracking.md).
+3. Click **Enable** to add the selected VMs to the computer group saved search for the feature. For more information, see [Limit Change Tracking and Inventory deployment scope](automation-scope-configurations-change-tracking.md).
 
     ![Enable Azure VMs](media/automation-enable-changes-from-auto-acct/enable-azure-vms.png)
 
@@ -74,7 +74,7 @@ Manually installed machines or machines already reporting to your workspace must
 ## Next steps
 
 * For details of the feature, see [Manage Change Tracking and Inventory](change-tracking-file-contents.md).
-* For information about scope configurations, see [Work with scope configurations for Change Tracking and Inventory](automation-scope-configurations-change-tracking.md).
+* For information about scope configurations, see [Limit Change Tracking and Inventory deployment scope](automation-scope-configurations-change-tracking.md).
 * To learn how to use the feature to identify software installed in your environment, see [Discover what software is installed on your VMs](automation-tutorial-installed-software.md).
 * If you don't want to integrate your Automation account with a Log Analytics workspace when enabling the feature, see [Unlink workspace from Automation account](automation-unlink-workspace-change-tracking.md).
 * When finished deploying changes to VMs, you can remove them as described in [Remove VMs from Change Tracking and Inventory](automation-remove-vms-from-change-tracking.md).
diff --git a/articles/automation/automation-enable-changes-from-browse.md b/articles/automation/automation-enable-changes-from-browse.md
@@ -55,7 +55,6 @@ Sign in to Azure at https://portal.azure.com.
 ## Next steps
 
 * For details of working with the feature, see [Manage Change Tracking and Inventory](change-tracking-file-contents.md).
-* For information about scope configurations, see [Work with scope configurations for Change Tracking and Inventory](automation-scope-configurations-change-tracking.md).
 * To learn how to use the feature to identify software installed in your environment, see [Discover what software is installed on your VMs](automation-tutorial-installed-software.md).
 * If you don't want to integrate your Automation account with a Log Analytics workspace when enabling the feature, see [Unlink workspace from Automation account](automation-unlink-workspace-change-tracking.md).
 * When finished deploying changes to VMs, you can remove them as described in [Remove VMs from Change Tracking and Inventory](automation-remove-vms-from-change-tracking.md).
diff --git a/articles/automation/automation-enable-changes-from-runbook.md b/articles/automation/automation-enable-changes-from-runbook.md
@@ -98,7 +98,6 @@ You must have enabled Change Tracking and Inventory for an Azure VM to start thi
 
 * To schedule a runbook, see [Manage schedules in Azure Automation](shared-resources/schedules.md).
 * For details of working with the feature, see [Manage Change Tracking and Inventory](change-tracking-file-contents.md).
-* For information about scope configurations, see [Work with scope configurations for Change Tracking and Inventory](automation-scope-configurations-change-tracking.md).
 * To learn how to use the feature to identify software installed in your environment, see [Discover what software is installed on your VMs](automation-tutorial-installed-software.md).
 * If you don't want to integrate your Automation account with a Log Analytics workspace when enabling the feature, see [Unlink workspace from Automation account](automation-unlink-workspace-change-tracking.md).
 * When finished deploying changes to VMs, you can remove them as described in [Remove VMs from Change Tracking and Inventory](automation-remove-vms-from-change-tracking.md).
diff --git a/articles/automation/automation-enable-changes-from-vm.md b/articles/automation/automation-enable-changes-from-vm.md
@@ -36,14 +36,14 @@ Sign in to the Azure portal at https://portal.azure.com.
 
 5. Choose the Log Analytics workspace and Automation account, and click **Enable** to enable Change Tracking and Inventory for the VM. The setup takes up to 15 minutes to complete. 
 
-## <a name="scope-configuration"></a>Check the scope configuration
+## <a name="scope-configuration"></a>Limit the scope for the deployment
 
-Change Tracking and Inventory uses a scope configuration within the workspace to target the computers to enable for the feature. The scope configuration is a group of one or more saved searches that is used to limit the scope of the feature to specific computers. For more information, see [Work with scope configurations for Change Tracking and Inventory](automation-scope-configurations-change-tracking.md).
+Change Tracking and Inventory uses a scope configuration within the workspace to target the computers to receive changes. For more information, see [Limit Change Tracking and Inventory deployment scope](automation-scope-configurations-change-tracking.md).
 
 ## Next steps
 
 * For details of working with the feature, see [Manage Change Tracking and Inventory](change-tracking-file-contents.md).
-* For information about scope configurations, see [Work with scope configurations for Change Tracking and Inventory](automation-scope-configurations-change-tracking.md).
+* For information about scope configurations, see [Limit Change Tracking and Inventory deployment scope](automation-scope-configurations-change-tracking.md).
 * To learn how to use the feature to identify software installed in your environment, see [Discover what software is installed on your VMs](automation-tutorial-installed-software.md).
 * If you don't want to integrate your Automation account with a Log Analytics workspace when enabling the feature, see [Unlink workspace from Automation account](automation-unlink-workspace-change-tracking.md).
 * When finished deploying changes to VMs, you can remove them as described in [Remove VMs from Change Tracking and Inventory](automation-remove-vms-from-change-tracking.md).
diff --git a/articles/automation/automation-onboard-solutions-from-automation-account.md b/articles/automation/automation-onboard-solutions-from-automation-account.md
@@ -31,9 +31,9 @@ Sign in to Azure at https://portal.azure.com.
 
     ![Enable Update Management](media/automation-onboard-solutions-from-automation-account/onboardsolutions2.png)
 
-## <a name="scope-configuration"></a>Check the scope configuration
+## <a name="scope-configuration"></a>Limit the scope for the deployment
 
-Update Management uses a scope configuration within the workspace to target the computers to enable for the feature. The scope configuration is a group of one or more saved searches that is used to limit the scope of the feature to specific computers. For more information, see [Work with scope configurations for Update Management](automation-scope-configurations-update-management.md).
+Update Management uses a scope configuration within the workspace to target the computers to receive updates. For more information, see [Limit Update Management deployment scope](automation-scope-configurations-update-management.md).
 
 ## Enable Azure VMs
 
@@ -74,7 +74,7 @@ Manually installed machines or machines already reporting to your workspace must
 ## Next steps
 
 * To use Update Management for VMs, see [Manage updates and patches for your Azure VMs](automation-tutorial-update-management.md).
-* For scope configurations, see [Work with scope configurations for Update Management](automation-scope-configurations-update-management.md).
+* For scope configurations, see [Limit Update Management deployment scope](automation-scope-configurations-update-management.md).
 * If you no longer need the Log Analytics workspace, see instructions in [Unlink workspace from Automation account for Update Management](automation-unlink-workspace-update-management.md).
 * To delete VMs from Update Management, see [Remove VMs from Update Management](automation-remove-vms-from-update-management.md).
 * To troubleshoot general Update Management errors, see [Troubleshoot Update Management issues](troubleshoot/update-management.md).
diff --git a/articles/automation/automation-onboard-solutions-from-browse.md b/articles/automation/automation-onboard-solutions-from-browse.md
@@ -57,7 +57,6 @@ Sign in to Azure at https://portal.azure.com.
 ## Next steps
 
 * To use Update Management for VMs, see [Manage updates and patches for your Azure VMs](automation-tutorial-update-management.md).
-* For scope configurations, see [Work with scope configurations for Update Management](automation-scope-configurations-update-management.md).
 * If you no longer need the Log Analytics workspace, see instructions in [Unlink workspace from Automation account for Update Management](automation-unlink-workspace-update-management.md).
 * To delete VMs from Update Management, see [Remove VMs from Update Management](automation-remove-vms-from-update-management.md).
 * To troubleshoot general Update Management errors, see [Troubleshoot Update Management issues](troubleshoot/update-management.md).
diff --git a/articles/automation/automation-onboard-solutions-from-vm.md b/articles/automation/automation-onboard-solutions-from-vm.md
@@ -38,14 +38,14 @@ Sign in to the Azure portal at https://portal.azure.com.
 
     ![Enable Update Management](media/automation-tutorial-update-management/manageupdates-update-enable.png)
 
-## <a name="scope-configuration"></a>Check the scope configuration
+## <a name="scope-configuration"></a>Limit the scope for the deployment
 
-Update Management uses a scope configuration within the workspace to target the computers to enable for the feature. The scope configuration is a group of one or more saved searches that is used to limit the scope of the feature to specific computers. For more information, see [Work with scope configurations for Update Management](automation-scope-configurations-update-management.md).
+Update Management uses a scope configuration within the workspace to target the computers to receive updates. For more information, see [Limit Update Management deployment scope](automation-scope-configurations-update-management.md).
 
 ## Next steps
 
 * To use Update Management for VMs, see [Manage updates and patches for your Azure VMs](automation-tutorial-update-management.md).
-* For scope configurations, see [Work with scope configurations for Update Management](automation-scope-configurations-update-management.md).
+* For scope configurations, see [Limit Update Management deployment scope](automation-scope-configurations-update-management.md).
 * If you no longer need the Log Analytics workspace, see instructions in [Unlink workspace from Automation account for Update Management](automation-unlink-workspace-update-management.md).
 * To delete VMs from Update Management, see [Remove VMs from Update Management](automation-remove-vms-from-update-management.md).
 * To troubleshoot general Update Management errors, see [Troubleshoot Update Management issues](troubleshoot/update-management.md).
diff --git a/articles/automation/automation-onboard-solutions.md b/articles/automation/automation-onboard-solutions.md
@@ -97,7 +97,6 @@ You must have enabled Update Management for an Azure VM to start this runbook. I
 
 * To schedule a runbook, see [Manage schedules in Azure Automation](shared-resources/schedules.md).
 * To use Update Management for VMs, see [Manage updates and patches for your Azure VMs](automation-tutorial-update-management.md).
-* For scope configurations, see [Work with scope configurations](automation-scope-configurations-update-management.md).
 * If you no longer need the Log Analytics workspace, see instructions in [Unlink workspace from Automation account for Update Management](automation-unlink-workspace-update-management.md).
 * To delete VMs from Update Management, see [Remove VMs from Update Management](automation-remove-vms-from-update-management.md).
 * To troubleshoot general Update Management errors, see [Troubleshoot Update Management issues](troubleshoot/update-management.md).
diff --git a/articles/automation/automation-remove-vms-from-change-tracking.md b/articles/automation/automation-remove-vms-from-change-tracking.md
@@ -18,7 +18,7 @@ When you're finished deploying changes to VMs in your environment, you can remov
     az vm show -g MyResourceGroup -n MyVm -d
     ```
 
-3. In your Log Analytics workspace under **General**, access the saved searches.
+3. In your Log Analytics workspace under **General**, access the saved searches for the scope configuration `MicrosoftDefaultScopeConfig-ChangeTracking`.
 
 4. For the saved search `MicrosoftDefaultComputerGroup`, click the ellipsis to the right and select **Edit**. 
 
diff --git a/articles/automation/automation-remove-vms-from-update-management.md b/articles/automation/automation-remove-vms-from-update-management.md
@@ -8,10 +8,6 @@ ms.custom: mvc
 ---
 # Remove VMs from Update Management
 
-## Sign in to Azure
-
-Sign in to the Azure portal at https://portal.azure.com.
-
 When you're finished deploying updates to VMs in your environment, you can remove them from the [Update Management](automation-update-management.md) feature.
 
 1. From your Automation account, select **Update management** under **Update management**.
@@ -22,7 +18,7 @@ When you're finished deploying updates to VMs in your environment, you can remov
     az vm show -g MyResourceGroup -n MyVm -d
     ```
 
-3. In your Log Analytics workspace under **General**, access the saved searches.
+3. In your Log Analytics workspace under **General**, access the saved searches for the scope configuration `MicrosoftDefaultScopeConfig-Updates`.
 
 4. For the saved search `MicrosoftDefaultComputerGroup`, click the ellipsis to the right and select **Edit**. 
 
diff --git a/articles/automation/automation-scope-configurations-change-tracking.md b/articles/automation/automation-scope-configurations-change-tracking.md
@@ -1,47 +1,39 @@
 ---
-title: Work with scope configurations for Azure Automation Change Tracking and Inventory
-description: This article tells how to work with scope configurations when you're using Change Tracking and Inventory.
+title: Limit Azure Automation Change Tracking and Inventory deployment scope
+description: This article tells how to work with scope configurations to limit the scope of a Change Tracking and Inventory deployment.
 services: automation
 ms.date: 03/04/2020
 ms.topic: conceptual
 ms.custom: mvc
 ---
 
-# Work with scope configurations for Change Tracking and Inventory
+# Limit Change Tracking and Inventory deployment scope
 
-This article describes how you can work with scope configurations when enabling the [Update Management](automation-update-management.md) feature on VMs. 
+This article describes how to work with scope configurations when using the [Change Tracking and Inventory](change-tracking.md) feature to deploy changes to your VMs. For more information, see [Targeting monitoring solutions in Azure Monitor (Preview)](https://docs.microsoft.com/azure/azure-monitor/insights/solution-targeting). 
 
-## Sign in to Azure
+## About scope configurations
 
-Sign in to the Azure portal at https://portal.azure.com.
+A scope configuration is a group of one or more saved searches (queries) used to limit the scope of Change Tracking and Inventory to specific computers. The scope configuration is used within the Log Analytics workspace to target the computers to enable. When you add a computer to changes from the feature, the computer is also added to a saved search in the workspace.
 
-## <a name="scope-configuration"></a>Check the scope configuration
+## Set the scope limit
 
-Update Management uses a scope configuration within the Log Analytics workspace to target the computers to enable for Update Management. The scope configuration is a group of one or more saved searches that is used to limit the scope of the feature to specific computers. To access the scope configurations:
+To limit the scope for your Change Tracking and Inventory deployment:
 
-1. In your Automation account under **Related resources**, select **Workspace**. 
+1. In your Automation account, select **Linked Workspace** under **Related resources**.
 
-2. Choose the workspace under **Workspace data sources**, and select **Scope Configurations**.
+2. Click **Go to workspace**.
 
-3. If the selected workspace doesn't have the Update Management feature enabled yet, it creates the `MicrosoftDefaultScopeConfig-ChangeTracking` scope configuration. 
+3. Select **Scope Configurations (Preview)** under **Workspace Data Sources**.
 
-4. If the selected workspace already has the feature enabled, it isn't redeployed, and the scope configuration isn't added to it. 
+4. Select the ellipsis to the right of the  `MicrosoftDefaultScopeConfig-ChangeTracking` scope configuration, and click **Edit**. 
 
-5. Select the ellipsis on any of the scope configurations, and then click **Edit**. 
-
-6. In the editing pane, select **Select Computer Groups**. The Computer Groups pane shows the saved searches that are used to create the scope configuration.
-
-## View a saved search
-
-When a computer is added to Change Tracking and Inventory, it's also added to a saved search in your workspace. The saved search is a query that contains the targeted computers.
-
-1. Navigate to your Log Analytics workspace and select **Saved searches** under **General**. The saved search used by Update Management is:
+5. In the editing pane, select **Select Computer Groups**. The Computer Groups pane shows the saved searches that are used to create the scope configuration. The saved search used by Change Tracking and Inventory is:
 
     |Name     |Category  |Alias  |
     |---------|---------|---------|
     |MicrosoftDefaultComputerGroup     |  ChangeTracking       | ChangeTracking__MicrosoftDefaultComputerGroup        |
 
-2. Select the saved search to view the query used to populate the group. The following image shows the query and its results:
+6. Select the saved search to view and edit the query used to populate the group. The following image shows the query and its results:
 
     ![Saved searches](media/automation-scope-configurations-change-tracking/logsearch.png)
 
diff --git a/articles/automation/automation-scope-configurations-update-management.md b/articles/automation/automation-scope-configurations-update-management.md
diff --git a/articles/automation/automation-tutorial-update-management.md b/articles/automation/automation-tutorial-update-management.md
diff --git a/articles/automation/change-tracking-file-contents.md b/articles/automation/change-tracking-file-contents.md
diff --git a/articles/automation/change-tracking.md b/articles/automation/change-tracking.md
