Merge pull request #233601 from paulth1/service-limits

ShawnJackson · web-flow · commit 54e126d8ba04 · 2023-04-12T18:06:54.000-05:00
[AQ] edit pass: service-limits
diff --git a/articles/azure-monitor/service-limits.md b/articles/azure-monitor/service-limits.md
@@ -1,6 +1,6 @@
 ---
 title: Azure Monitor service limits | Microsoft Docs
-description: Lists limits in different areas of Azure Monitor.
+description: This article lists limits in different areas of Azure Monitor.
 ms.topic: conceptual
 ms.custom: ignite-2022
 author: bwren
@@ -28,19 +28,18 @@ This article lists limits in different areas of Azure Monitor.
 
 [!INCLUDE [monitoring-limits-metrics](../../includes/azure-monitor-limits-metrics.md)]
 
-## Logs ingestion API
+## Logs Ingestion API
 
 [!INCLUDE [monitoring-limits-custom-logs](../../includes/azure-monitor-limits-custom-logs.md)]
 
 ## Data collection rules
 
 [!INCLUDE [monitoring-limits-data-collection-rules](../../includes/azure-monitor-limits-data-collection-rules.md)]
 
-## Diagnostic Settings
+## Diagnostic settings
 
 [!INCLUDE [monitoring-limits-diagnostic-settings](../../includes/azure-monitor-limits-diagnostic-settings.md)]
 
-
 ## Log queries and language
 
 [!INCLUDE [monitoring-limits-log-queries](../../includes/azure-monitor-limits-log-queries.md)]
@@ -53,7 +52,7 @@ This article lists limits in different areas of Azure Monitor.
 
 [!INCLUDE [monitoring-limits-application-insights](../../includes/application-insights-limits.md)]
 
-## Next Steps
+## Next steps
 
 - [Azure Monitor pricing](https://azure.microsoft.com/pricing/details/monitor/)
 - [Monitoring usage and estimated costs in Azure Monitor](./usage-estimated-costs.md)
diff --git a/includes/application-insights-limits.md b/includes/application-insights-limits.md
@@ -14,9 +14,9 @@ There are some limits on the number of metrics and events per application, that
 
 | Resource | Default limit| Maximum limit | Notes |
 |---|---|---|---|
-| Total data per day | 100 GB | [Contact support.](https://azure.microsoft.com/support/options/) | You can reduce data by setting a cap. If you need more data, you can increase the limit in the portal, up to 1,000 GB. For capacities greater than 1,000 GB, send email to AIDataCap@microsoft.com.
+| Total data per day | 100 GB | [Contact support.](https://azure.microsoft.com/support/options/) | You can set a cap to reduce data. If you need more data, you can increase the limit in the portal, up to 1,000 GB. For capacities greater than 1,000 GB, send email to AIDataCap@microsoft.com.
 | Throttling | 32,000 events/second | [Contact support.](https://azure.microsoft.com/support/options/) | The limit is measured over a minute.
-| Data retention logs | [30 to 730 days](../articles/azure-monitor/logs/data-retention-archive.md)  | 730 days | This resource is for [Logs](../articles/azure-monitor/logs/log-query-overview.md).
+| Data retention logs | [30 to 730 days](../articles/azure-monitor/logs/data-retention-archive.md) | 730 days | This resource is for [Logs](../articles/azure-monitor/logs/log-query-overview.md).
 | Data retention metrics | 90 days | 90 days | This resource is for [Metrics Explorer](../articles/azure-monitor/essentials/metrics-charts.md).
 | [Availability multistep test](/previous-versions/azure/azure-monitor/app/availability-multistep) detailed results retention | 90 days | 90 days | This resource provides detailed results of each step.
 | Maximum telemetry item size | 64 KB | 64 KB | |
@@ -26,7 +26,7 @@ There are some limits on the number of metrics and events per application, that
 | Trace and exception message length | 32,768 | 32,768 | See [type schemas](../articles/azure-monitor/app/data-model.md).
 | [Availability tests](/previous-versions/azure/azure-monitor/app/monitor-web-app-availability) count per app | 100 | 100 | |
 | [Profiler](../articles/azure-monitor/app/profiler.md) and [Snapshot](../articles/azure-monitor/app/snapshot-debugger.md) data retention | Two weeks | [Contact support.](https://azure.microsoft.com/support/options/) Maximum retention limit is six months. | |
-| [Profiler](../articles/azure-monitor/app/profiler.md) data sent per day | No limit | No limit | |
-| [Snapshot](../articles/azure-monitor/app/snapshot-debugger.md) data sent per day | 30 snapshots per day per monitored app | No limit | The number of snapshots collected per application can be modified through [configuration](../articles/azure-monitor/app/snapshot-debugger-vm.md). |
+| [Profiler](../articles/azure-monitor/app/profiler.md) data sent per day | No limit | No limit. | |
+| [Snapshot](../articles/azure-monitor/app/snapshot-debugger.md) data sent per day | 30 snapshots per day per monitored app | No limit. | The number of snapshots collected per application can be modified through [configuration](../articles/azure-monitor/app/snapshot-debugger-vm.md). |
 
 For more information about pricing and quotas, see [Application Insights billing](../articles/azure-monitor/logs/cost-logs.md#application-insights-billing).
diff --git a/includes/azure-monitor-limits-action-groups.md b/includes/azure-monitor-limits-action-groups.md
@@ -9,18 +9,18 @@ ms.date: 2/14/2021
 ms.author: dukek
 ms.custom: "include file"
 ---
-You may have an unlimited number of action groups in a subscription.
+You can have an unlimited number of action groups in a subscription.
 
 | Resource | Default limit | Maximum limit |
 | --- | --- | --- |
-| Azure app push | 10 Azure app actions per action group. | Same as Default |
-| Email | 1,000 email actions in an action group.<br>No more than 100 emails in an hour.<br>Also see the [rate limiting information](../articles/azure-monitor/alerts/alerts-rate-limiting.md). | Same as Default |
-| Email ARM role | 10 Email ARM role actions per action group. | Same as Default |
-| Event Hub | 10 Event Hub actions per action group. | Same as Default |
-| ITSM | 10 ITSM actions in an action group. | Same as Default | 
-| Logic app | 10 logic app actions in an action group. | Same as Default |
-| Runbook | 10 runbook actions in an action group. | Same as Default |
-| Secure Webhook | 10 secure webhook actions in an action group.  Maximum number of webhook calls is 1500 per minute per subscription. Other limits are available at [action-specific information](../articles/azure-monitor/alerts/action-groups.md#action-specific-information).  | Same as Default |
-| SMS | 10 SMS actions in an action group.<br>No more than 1 SMS message every 5 minutes.<br>Also see the [rate limiting information](../articles/azure-monitor/alerts/alerts-rate-limiting.md). | Same as Default |
-| Voice | 10 voice actions in an action group.<br>No more than 1 voice call every 5 minutes.<br>Also see the [rate limiting information](../articles/azure-monitor/alerts/alerts-rate-limiting.md). | Same as Default |
-| Webhook | 10 webhook actions in an action group.  Maximum number of webhook calls is 1500 per minute per subscription. Other limits are available at [action-specific information](../articles/azure-monitor/alerts/action-groups.md#action-specific-information).  | Same as Default |
+| Azure app push | 10 Azure app actions per action group. | Same as default |
+| Email | 1,000 email actions in an action group.<br>No more than 100 emails in an hour.<br>Also see the [rate limiting information](../articles/azure-monitor/alerts/alerts-rate-limiting.md). | Same as default |
+| Email Azure Resource Manager role | 10 email Resource Manager role actions per action group. | Same as default |
+| Event hub | 10 event hub actions per action group. | Same as default |
+| IT Service Management (ITSM) | 10 ITSM actions in an action group. | Same as default | 
+| Logic app | 10 logic app actions in an action group. | Same as default |
+| Runbook | 10 runbook actions in an action group. | Same as default |
+| Secure Webhook | 10 Secure Webhook actions in an action group. Maximum number of webhook calls is 1,500 per minute per subscription. Other limits are available at [action-specific information](../articles/azure-monitor/alerts/action-groups.md#action-specific-information). | Same as default |
+| SMS | 10 SMS actions in an action group.<br>No more than one SMS message every 5 minutes.<br>Also see the [rate limiting information](../articles/azure-monitor/alerts/alerts-rate-limiting.md). | Same as default |
+| Voice | 10 voice actions in an action group.<br>No more than one voice call every 5 minutes.<br>Also see the [rate limiting information](../articles/azure-monitor/alerts/alerts-rate-limiting.md). | Same as default |
+| Webhook | 10 webhook actions in an action group. Maximum number of webhook calls is 1,500 per minute per subscription. Other limits are available at [action-specific information](../articles/azure-monitor/alerts/action-groups.md#action-specific-information). | Same as default |
diff --git a/includes/azure-monitor-limits-alerts.md b/includes/azure-monitor-limits-alerts.md
@@ -12,19 +12,19 @@ ms.custom: "include file"
 
 | Resource | Default limit | Maximum limit |
 | --- | --- | --- |
-| Metric alerts (classic) |100 active alert rules per subscription. | Call support |
-| Metric alerts |5,000 active alert rules per subscription in Azure public, Azure China 21Vianet and Azure Government clouds. If you are hitting this limit, explore if you can use [same type multi-resource alerts](../articles/azure-monitor/alerts/alerts-metric-overview.md#monitoring-at-scale-using-metric-alerts-in-azure-monitor).<br/>5,000 metric time-series per alert rule. | Call support. |
-| Activity log alerts | 100 active alert rules per subscription (cannot be increased). | Same as default |
-| Log alerts | 5000 active alert rules per subscription. Out of which 100 active alert rules with 1-minute frequency. <br/>1000 active alert rules per resource. <br/>6000 time series per alert rule. | Call support |
-| Alert processing rules | 1000 active rules per subscription. | Call support |
-| Alert rules and alert processing rules description length| Log search alerts 4096 characters<br/>All other 2048 characters | Same as default |
+| Metric alerts (classic) |100 active alert rules per subscription. | Call support. |
+| Metric alerts |5,000 active alert rules per subscription in Azure public, Azure China 21Vianet, and Azure Government clouds. If you're hitting this limit, explore if you can use the [same type multi-resource alerts](../articles/azure-monitor/alerts/alerts-metric-overview.md#monitoring-at-scale-using-metric-alerts-in-azure-monitor).<br/>5,000 metric time-series per alert rule. | Call support. |
+| Activity log alerts | 100 active alert rules per subscription (can't be increased). | Same as default. |
+| Log alerts | 5,000 active alert rules per subscription. Out of which, 100 active alert rules with 1-minute frequency. <br/>1,000 active alert rules per resource. <br/>6,000 time series per alert rule. | Call support. |
+| Alert processing rules | 1,000 active rules per subscription. | Call support. |
+| Alert rules and alert processing rules description length| Log search alerts 4,096 characters.<br/>All others are 2,048 characters. | Same as default. |
 
 ### Alerts API
-Azure Monitor Alerts have several throttling limits to protect against users making an excessive number of calls. Such behavior can potentially overload the system backend resources and jeopardize service responsiveness. The following limits are designed to protect customers from interruptions and ensure consistent service level. The user throttling and limits are designed to impact only extreme usage scenario and should not be relevant for typical usage.
+Azure Monitor alerts have several throttling limits to protect against users making an excessive number of calls. Such behavior can potentially overload the system back-end resources and jeopardize service responsiveness. The following limits are designed to protect customers from interruptions and ensure a consistent service level. The user throttling and limits are designed to affect only extreme usage scenarios. They shouldn't be relevant for typical usage.
 
 | Resource | Default limit | Maximum limit |
 | --- | --- | --- |
 | [Alerts - Get Summary](/rest/api/monitor/alertsmanagement/alerts/get-summary) | 50 calls per minute per subscription | Same as default | 
 |	[Alerts - Get All](/rest/api/monitor/alertsmanagement/alerts/get-all) (not "Get By Id") | 100 calls per minute per subscription | Same as default | 
-|	[All other alerts calls](/rest/api/monitor/alertsmanagement/alerts) | 1000 calls per minute per subscription | Same as default | 
+|	[All other alerts calls](/rest/api/monitor/alertsmanagement/alerts) | 1,000 calls per minute per subscription | Same as default | 
 
diff --git a/includes/azure-monitor-limits-custom-logs.md b/includes/azure-monitor-limits-custom-logs.md
@@ -12,7 +12,6 @@ ms.custom: "include file"
 
 | Limit | Value |
 |:---|:---|
-| Maximum size of API call | 1MB for both compressed and uncompressed data |
-| Maximum data/minute per DCR | 2 GB for both compressed and uncompressed data. Retry after the duration listed in the `Retry-After` header in the response.  |
+| Maximum size of API call | 1 MB for both compressed and uncompressed data. |
+| Maximum data/minute per DCR | 2 GB for both compressed and uncompressed data. Retry after the duration listed in the `Retry-After` header in the response. |
 | Maximum requests/minute per DCR | 12,000. Retry after the duration listed in the `Retry-After` header in the response. |
-
diff --git a/includes/azure-monitor-limits-log-queries.md b/includes/azure-monitor-limits-log-queries.md
@@ -14,22 +14,21 @@ ms.custom: "include file"
 
 | Limit | Description |
 |:---|:---|
-| Query language | Azure Monitor uses the same [Kusto query language](/azure/kusto/query/) as Azure Data Explorer. See [Azure Monitor log query language differences](/azure/data-explorer/kusto/query/) for KQL language elements not supported in Azure Monitor. |
+| Query language | Azure Monitor uses the same [Kusto Query Language (KQL)](/azure/kusto/query/) as Azure Data Explorer. See [Azure Monitor log query language differences](/azure/data-explorer/kusto/query/) for KQL language elements not supported in Azure Monitor. |
 | Azure regions | Log queries can experience excessive overhead when data spans Log Analytics workspaces in multiple Azure regions. See [Query limits](../articles/azure-monitor/logs/scope.md#query-scope-limits) for details. |
 | Cross resource queries | Maximum number of Application Insights resources and Log Analytics workspaces in a single query limited to 100.<br>Cross-resource query isn't supported in View Designer.<br>Cross-resource query in log alerts is supported in the new scheduledQueryRules API.<br>See [Cross-resource query limits](../articles/azure-monitor/logs/cross-workspace-query.md#cross-resource-query-limits) for details. |
-| Log Analytics dashboard queries | Maximum number of records returned in a single Log Analytics dashboard query is 2000. |
+| Log Analytics dashboard queries | Maximum number of records returned in a single Log Analytics dashboard query is 2,000. |
 
 ### User query throttling
-Azure Monitor has several throttling limits to protect against users sending an excessive number of queries. Such behavior can potentially overload the system backend resources and jeopardize service responsiveness. The following limits are designed to protect customers from interruptions and ensure consistent service level. The user throttling and limits are designed to impact only extreme usage scenario and shouldn't be relevant for typical usage.
-
+Azure Monitor has several throttling limits to protect against users sending an excessive number of queries. Such behavior can potentially overload the system back-end resources and jeopardize service responsiveness. The following limits are designed to protect customers from interruptions and ensure consistent service level. The user throttling and limits are designed to affect only extreme usage scenarios and shouldn't be relevant for typical usage.
 
 | Measure | Limit per user | Description |
 |:---|:---|:---|
-| Concurrent queries | 5 | A user can run up to five concurrent queries, any additional query will be added to a queue. When one of the running queries finishes, the first query in the queue is pulled from the queue and starts running. Note: Alerts queries aren't part of this limit.
-| Time in concurrency queue | 3 minutes | If a query sits in the queue for more than 3 minutes without being started, it will be terminated with an HTTP error response with code 429. |
-| Total queries in concurrency queue | 200 | Once the number of queries in the queue reach 200, the next query will be rejected with an HTTP error code 429. This number is in addition to the five queries that can be running simultaneously. |
+| Concurrent queries | 5 | A user can run up to five concurrent queries. Any other query is added to a queue. When one of the running queries finishes, the first query in the queue is pulled from the queue and starts running. Alert queries aren't part of this limit.
+| Time in concurrency queue | 3 minutes | If a query sits in the queue for more than 3 minutes without being started, it's terminated with an HTTP error response with code 429. |
+| Total queries in concurrency queue | 200 | When the number of queries in the queue reaches 200, the next query is rejected with an HTTP error code 429. This number is in addition to the five queries that can be running simultaneously. |
 | Query rate | 200 queries per 30 seconds | Overall rate of queries that can be submitted by a single user to all workspaces. This limit applies to programmatic queries or queries initiated by visualization parts such as Azure dashboards and the Log Analytics workspace summary (deprecated) page. |
 
 - Optimize your queries as described in [Optimize log queries in Azure Monitor](../articles/azure-monitor/logs/query-optimization.md).
-- Dashboards and workbooks can contain multiple queries in a single view that generate a burst of queries every time they load or refresh. Consider breaking them up into multiple views that load on demand. 
+- Dashboards and workbooks can contain multiple queries in a single view that generate a burst of queries every time they load or refresh. Consider breaking them up into multiple views that load on demand.
 - In Power BI, consider extracting only aggregated results rather than raw logs.
diff --git a/includes/azure-monitor-limits-metrics.md b/includes/azure-monitor-limits-metrics.md
diff --git a/includes/azure-monitor-limits-workspaces.md b/includes/azure-monitor-limits-workspaces.md
