Merge pull request #246584 from SnehaSudhirG/28Jul-DSDocUpdate

Added info on prereqs and service limits

Author: ShannonLeavitt

articles/update-center/dynamic-scope-overview.md

@@ -29,22 +29,46 @@ The criteria will be evaluated at the scheduled run time, which will be the fina
   > [!NOTE]
   > You can associate one dynamic scope to one schedule.
 
+## Prerequisites
+
+#### [Azure VMs](#tab/avms)
+
+- Patch Orchestration must be set to Customer Managed Schedules (Preview). This sets patch mode to AutomaticByPlatform and the **BypassPlatformSafetyChecksOnUserSchedule** = *True*.
+- Associate a Schedule with the VM.
+- Ensure to register the preview feature in your Azure subscription by following these steps:
+
+  1. Sign in to the [Azure portal](https://portal.azure.com).
+  1. In search, enter and select **Subscriptions**.
+  1. In **Subscriptions** home page, select your subscription from the list.
+  1. In the **Subscription | Preview features** page, under **Settings**, select **Preview features**.
+  1. Search for **Dynamic Scope (preview)**. 
+  1. Select **Register** and then select **OK** to get started with Dynamic scope (preview).
+             
+#### [Arc-enabled VMs](#tab/arcvms)
+
+There are no pre-requisities for patch orchestration. However, you must associate a schedule with the VM for Schedule patching. For more information, see [Configure schedule patching on Azure VMs to ensure business continuity](prerequsite-for-schedule-patching.md).
+
+---
+
 ## Permissions
 
 For dynamic scoping (preview) and configuration assignment, ensure that you have the following permissions:
 
 - Write permissions to create or modify a schedule.
 - Read permissions to assign or read a schedule.
 
+## Service limits
 
-## Prerequisites for Azure VMs
+The following are the Dynamic scope (preview) limits for **each dynamic scope**.
 
-- Patch Orchestration must be set to Customer Managed Schedules (Preview). This sets patch mode to AutomaticByPlatform and the **BypassPlatformSafetyChecksOnUserSchedule** = *True*.
-- Associate a Schedule with the VM.
+| Resource    | Limit          |
+|----------|----------------------------|
+| Resource associations     | 1000  |
+| Number of tag filters | 50 |
+| Number of Resource Group filters    | 50 |
 
 > [!NOTE]
-> For Arc VMs, there are no patch orchestration pre-requisites. However, you must associate a schedule with the VM for Schedule patching. For more information, see [Configure schedule patching on Azure VMs to ensure business continuity](prerequsite-for-schedule-patching.md).
-
+> The above limits are for Dynamic scope (preview) in the Guest scope only.
 
 ## Next steps
 

articles/update-center/scheduled-patching.md

@@ -33,6 +33,18 @@ Update management center (preview) uses maintenance control schedule instead of
 1. All VMs in a common [availability set](../virtual-machines/availability-set-overview.md) aren't updated concurrently.
 1. VMs in a common availability set are updated within Update Domain boundaries and, VMs across multiple Update Domains aren't updated concurrently.
 
+## Service limits
+
+The following are the recommended limits for the mentioned indicators:
+
+| Indicator    | Limit          |
+|----------|----------------------------|
+| Number of schedules per Subscription per Region     | 250  |
+| Total number of Resource associations to a schedule | 3000 |
+| Resource associations on each dynamic scope    | 1000 |
+| Number of dynamic scopes per Resource Group or Subscription per Region     | 250  |
+
+
 ## Schedule recurring updates on single VM
 
 >[!NOTE]