Merge pull request #286120 from SnehaSudhirG/04Sep-ARMUpdate

Updated the heading and info to the V2 of Update Management

Author: v-ccolin

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

@@ -3,7 +3,7 @@ title: Use dynamic groups with Azure Automation Update Management
 description: This article tells how to use dynamic groups with Azure Automation Update Management.
 services: automation
 ms.subservice: update-management
-ms.date: 07/15/2024
+ms.date: 09/05/2024
 ms.topic: conceptual
 ms.service: azure-automation
 ---
@@ -17,7 +17,7 @@ Update Management allows you to target a dynamic group of Azure or non-Azure VMs
 
 You can define dynamic groups for Azure or non-Azure machines from **Update management** in the Azure portal. See [Manage updates for VMs](manage-updates-for-vm.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](../../azure-resource-manager/management/azure-subscription-service-limits.md#update-management).
+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.
 
 > [!NOTE]
 > If you expect to update more than 1000 machines, we recommend that you split up the updates among multiple update schedules. 

articles/automation/update-management/overview.md

@@ -66,7 +66,12 @@ At the date and time specified in the update deployment, the target machines exe
 
 ## Limits
 
-For limits that apply to Update Management, see [Azure Automation service limits](../../azure-resource-manager/management/azure-subscription-service-limits.md#update-management).
+Following are limits that apply to Update Management:
+
+| **Resource** | **Limit**| **Notes** |
+|---|---|---|
+|Number of machines per update deployment|1000||
+|Number of dynamic groups per update deployment |500 ||
 
 ## Permissions
 

includes/azure-automation-service-limits.md

@@ -56,11 +56,24 @@ The following table shows the tracked item limits per machine for change trackin
 |Services|250||
 |Daemon|250||
 
-#### Update Management
+#### Azure Update Manager
 
-The following table shows the limits for Update Management.
+The following are the Dynamic scope recommended limits for **each dynamic scope**:
 
-| **Resource** | **Limit**| **Notes** |
-|---|---|---|
-|Number of machines per update deployment|1000||
-|Number of dynamic groups per update deployment |500 ||
+| Resource    | Limit          |
+|----------|----------------------------|
+| Resource associations     | 1000  |
+| Number of tag filters | 50 |
+| Number of Resource Group filters    | 50 |
+
+
+The following are the limits for schedule patching:
+
+| Indicator    | Limit          |
+|----------|----------------------------|
+| Number of schedules per subscription per region     | 250  |
+| Total number of resource associations to a schedule | 3,000 |
+| Resource associations on each dynamic scope    | 1,000 |
+| Number of dynamic scopes per resource group or subscription per region     | 250  |
+| Number of dynamic scopes per schedule   | 30  |
+| Total number of subscriptions attached to all dynamic scopes per schedule   | 30  |