review-draft-1

Author: EdB-MSFT

articles/azure-monitor/essentials/azure-monitor-workspace-scaling-best-practice.md

@@ -30,8 +30,8 @@ The following are scenarios that require splitting an Azure Monitor workspace in
 | Compliance or regulatory requirements.|   If you're subject to regulations that mandate the storage of data in specific regions. Create an Azure Monitor workspace per region as per your requirements. |
 | Regional scaling. |   When you're managing metrics for regionally diverse organizations such as large services or financial institutions with regional accounts, create an Azure Monitor workspace per region.
 | Azure tenants.|   For multiple Azure tenants, create an Azure Monitor workspace in each tenant. Querying data across tenants isn't supported.
-| Deployment environments. |   Create a separate workspace for each of your deployment environments to maintain discrete metrics for development, test, preproduction, and production environments.|
-| Service limits and quotas. |  **Azure Monitor workspaces are built for hyperscale. There's no reduction in performance in terms of availability and efficiency due to the amount of data in your Azure Monitor workspace. Multiple services, apps, and clusters can send data to the same workspace simultaneously. Azure Monitor workspaces start with default limits and quotas, but these limits can be increased via support tickets to support your scale needs as you grow. For customers operating at large scale, such as 100Mn+ events/min or time series, we recommend you contact your Azure representative.    Duplicated below - rework**|
+| Deployment environments. |   Create a separate workspace for each of your deployment environments to maintain discrete metrics for development, test, pre-production, and production environments.|
+| Service limits and quotas. |  Azure Monitor workspaces are built for hyperscale. There's no reduction in performance in terms of availability and efficiency due to the amount of data in your Azure Monitor workspace. Multiple services, apps, and clusters can send data to the same workspace simultaneously. Azure Monitor workspaces have default ingestion limits.If you are approaching the limit, or estimate that you will exceed the ingestion limit, consider splitting your workspace into two or more workspaces. Alternatively, these limits can be increase by opening a support ticket.|
 
 ## Service limits and quotas