Merge pull request #245165 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: Taojunshen

articles/active-directory/cloud-infrastructure-entitlement-management/product-rule-based-anomalies.md

@@ -60,7 +60,7 @@ Rule-based anomalies identify recent activity in Permissions Management that is
 1. Select one of the following conditions:
       - **Any Resource Accessed for the First Time**: The identity accesses a resource for the first time during the specified time interval.
       - **Identity Performs a Particular Task for the First Time**: The identity does a specific task for the first time during the specified time interval.
-       - **Identity Performs a Task for the First Time**: The identity performs any task for the first time during the specified time interval
+      - **Identity Performs a Task for the First Time**: The identity performs any task for the first time during the specified time interval.
 1. Select **Next**.
 1. On the **Authorization Systems** tab, select the available authorization systems and folders, or select **All**.
 

articles/aks/operator-best-practices-cluster-security.md

@@ -53,6 +53,10 @@ For more information about Azure AD integration, Kubernetes RBAC, and Azure RBAC
 >
 > Add a network policy in all user namespaces to block pod egress to the metadata endpoint.
 
+> [!NOTE]
+> To implement Network Policy, include the attribute `--network-policy azure` when creating the AKS cluster. Use the following command to create the cluster:
+> `az aks create -g myResourceGroup -n myManagedCluster --enable-managed-identity --network-plugin azure --network-policy azure`
+
 ```yaml
 apiVersion: networking.k8s.io/v1
 kind: NetworkPolicy

articles/sentinel/dynamics-365/deploy-dynamics-365-finance-operations-solution.md

@@ -44,8 +44,8 @@ Before you begin, verify that:
 ## Deploy the solution and enable the data connector
 
 1. Navigate to the **Microsoft Sentinel** service.
-1. Select **Content hub**, and in the search bar, search for *Dynamics 365 F&O*.
-1. Select **Dynamics 365 F&O**.
+1. Select **Content hub**, and in the search bar, search for *Dynamics 365 Finance and Operations*.
+1. Select **Dynamics 365 Finance and Operations**.
 1. Select **Install**.
 
     For more information about how to manage the solution components, see [Discover and deploy out-of-the-box content](../sentinel-solutions-deploy.md).

articles/sentinel/normalization-develop-parsers.md

@@ -425,7 +425,7 @@ Handle the results as follows:
 To make sure that your parser produces valid values, use the ASIM data tester by running the following query in the Microsoft Sentinel **Logs** page:
 
   ```KQL
-  <parser name> | limit <X> | invoke ASimDataTester ( ['<schema>'] )
+  <parser name> | limit <X> | invoke ASimDataTester ('<schema>')
   ```
 
 Specifying a schema is optional. If a schema is not specified, the `EventSchema` field is used to identify the schema the event should adhere to. Ig an event does not include an `EventSchema` field, only common fields will be verified. If a schema is specified as a parameter, this schema will be used to test all records. This is useful for older parsers that do not set the `EventSchema` field. 

articles/virtual-machines/maintenance-configurations.md

@@ -59,7 +59,7 @@ This scope is integrated with [update management center](../update-center/overvi
 
 - The upper maintenance window is 3 hours 55 mins.
 - A minimum of 1 hour and 30 minutes is required for the maintenance window.
-- There is no limit to the recurrence of your schedule.
+- The value of **Repeat** should be at least 6 hours.
 
 To learn more about this topic, checkout [update management center and scheduled patching](../update-center/scheduled-patching.md)
 
@@ -80,6 +80,27 @@ You can create and manage maintenance configurations using any of the following
 
 For an Azure Functions sample, see [Scheduling Maintenance Updates with Maintenance Configurations and Azure Functions](https://github.com/Azure/azure-docs-powershell-samples/tree/master/maintenance-auto-scheduler).
 
+## 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  |
+
+The following are the Dynamic Scope Limits for **each dynamic scope**
+
+| Resource    | Limit          |
+|----------|----------------------------|
+| Resource associations     | 1000  |
+| Number of tag filters | 50 |
+| Number of Resource Group filters    | 50 |
+
+**Please note that the above limits are for the Dynamic Scoping in the Guest scope only.**
+
 ## Next steps
 
 To learn more, see [Maintenance and updates](maintenance-and-updates.md).