Merge pull request #113549 from BethWilke/branch130

Fixing tasks 1714563, 1712624

Author: garycentric

articles/automation/TOC.yml

@@ -230,7 +230,7 @@
           href: updatemgmt-mecmintegration.md
         - name: Configure Windows Update client
           href: automation-configure-windows-update.md
-        - name: Using dynamic groups
+        - name: Use dynamic groups
           href: automation-update-management-groups.md
         - name: Query Update Management logs
           href: automation-update-management-query-logs.md

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

@@ -6,13 +6,25 @@ ms.subservice: update-management
 ms.date: 11/20/2019
 ms.topic: conceptual
 ---
+
 # Use dynamic groups with Update Management
 
-Update Management allows you to target a dynamic group of Azure or non-Azure VMs for update deployments. These groups, defined by queries, are evaluated at deployment time so that you don't have to edit your deployment to add machines.
+Update Management allows you to target a dynamic group of Azure or non-Azure VMs for update deployments. Using a dynamic group keeps you from having to edit your deployment to update machines.
+
+> [!NOTE]
+> Dynamic groups do not work with classic VMs.
+
+You can define dynamic groups for Azure or non-Azure machines from **Update management** in the Azure portal. See 
+[Manage updates for multiple Azure virtual machines](manage-update-multi.md).
+
+A dynamic group is defined by a query that Azure Automation evaluates at deployment time. Even if a dynamic group query retrieves a large number of machines, Azure Automation can process only a maximum of 1000 machines at a time. See [Azure subscription and service limits, quotas, and constraints](https://docs.microsoft.com/azure/azure-resource-manager/management/azure-subscription-service-limits#update-management). 
+
+> [!NOTE]
+> If you expect to update more than 1000 machines, we recommend that you split up the updates among multiple update schedules. 
 
-## Azure machines
+## Define dynamic groups for Azure machines
 
-Dynamic groups do not work with classic VMs. When defining your query, the following items can be used together to populate a dynamic group:
+When defining a dynamic group query for Azure machines, you can use the following items to populate the dynamic group:
 
 * Subscription
 * Resource groups
@@ -21,16 +33,16 @@ Dynamic groups do not work with classic VMs. When defining your query, the follo
 
 ![Select groups](./media/automation-update-management/select-groups.png)
 
-To preview the results of a dynamic group, click **Preview**. The preview shows the group membership at the current time. In the example, we're searching for machines having the tag `Role` for the group **BackendServer**. If more machines have this tag added, they are added to any future deployments against that group.
+To preview the results of your dynamic group query, click **Preview**. The preview shows the group membership at the current time. In the example, we're searching for machines having the tag `Role` for the group **BackendServer**. If more machines have this tag added, they are added to any future deployments against that group.
 
 ![preview groups](./media/automation-update-management/preview-groups.png)
 
-## Non-Azure machines
+## Define dynamic groups for 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.
+A dynamic group for non-Azure machines uses saved searches, also called computer groups. 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 saved search is created, you can select it from the list of saved searches in **Update management** in the Azure portal. Click **Preview** to preview the computers in the saved search.
 
 ![Select groups](./media/automation-update-management/select-groups-2.png)
 
 ## Next steps
 
-After creating a dynamic group, you can [Create an Update Deployment](automation-tutorial-update-management.md).
+After creating a dynamic group, you can [Create an update deployment](automation-tutorial-update-management.md).

articles/automation/graphical-runbook-sdk.md

@@ -13,7 +13,7 @@ ms.topic: conceptual
 
 ## Prerequisites
 
-Import the [Microsoft.Azure.Management.Automation.Models](https://docs.microsoft.com/dotnet/api/microsoft.azure.management.automation.models?view=azure-dotnet) package into your project.
+Import the `Orchestrator.GraphRunbook.Model.dll` package into your project.
 
 ## Create a runbook object instance