Merging changes synced from https://github.com/MicrosoftDocs/azure-docs-pr (branch live)

Author: Learn Build Service GitHub App

articles/azure-monitor/alerts/alerts-types.md

@@ -31,7 +31,7 @@ The information in this table can help you decide when to use each type of alert
 |Metric alert|Metric data is stored in the system already pre-computed. Metric alerts are useful when you want to be alerted about data that requires little or no manipulation. Use metric alerts if the data you want to monitor is available in metric data.|Each metric alert rule is charged based on the number of time series that are monitored. |
 |Log alert|You can use log alerts to perform advanced logic operations on your data. If the data you want to monitor is available in logs, or requires advanced logic, you can use the robust features of Kusto Query Language (KQL) for data manipulation by using log alerts.|Each log alert rule is billed based on the interval at which the log query is evaluated. More frequent query evaluation results in a higher cost. For log alerts configured for [at-scale monitoring](#splitting-by-dimensions-in-log-alert-rules), the cost also depends on the number of time series created by the dimensions resulting from your query. |
 |Activity log alert|Activity logs provide auditing of all actions that occurred on resources. Use activity log alerts to be alerted when a specific event happens to a resource like a restart, a shutdown, or the creation or deletion of a resource. Service Health alerts and Resource Health alerts let you know when there's an issue with one of your services or resources.|For more information, see the [pricing page](https://azure.microsoft.com/pricing/details/monitor/).|
-|Prometheus alerts|Prometheus alerts are primarily used for alerting on performance and health of Kubernetes clusters, including Azure Kubernetes Service. The alert rules are based on PromQL, which is an open-source query language. |Prometheus alert rules are only charged on the data queried by the rules.  For more information, see the [pricing page](https://azure.microsoft.com/pricing/details/monitor/). |
+|Prometheus alerts|Prometheus alerts are used for alerting on Prometheus metrics stored in [Azure Monitor managed services for Prometheus](../essentials/prometheus-metrics-overview.md). The alert rules are based on the PromQL open-source query language. |Prometheus alert rules are only charged on the data queried by the rules.  For more information, see the [pricing page](https://azure.microsoft.com/pricing/details/monitor/). |
 
 ## Metric alerts
 
@@ -207,7 +207,7 @@ Smart detection works for web apps hosted in the cloud or on your own servers th
 
 ## Prometheus alerts
 
-Prometheus alerts are based on Prometheus metric values stored in [Azure Monitor managed services for Prometheus](../essentials/prometheus-metrics-overview.md). Prometheus alert rules are configured as part of [Prometheus rule groups](/azure/azure-monitor/essentials/prometheus-rule-groups). They fire when the result of a PromQL expression resolves to true. Fired Prometheus alerts are displayed and managed like other alert types.
+Prometheus alerts are used to monitor metrics stored in [Azure Monitor managed services for Prometheus](../essentials/prometheus-metrics-overview.md). Prometheus alert rules are configured as part of [Prometheus rule groups](/azure/azure-monitor/essentials/prometheus-rule-groups). They fire when the result of a PromQL expression resolves to true. Fired Prometheus alerts are displayed and managed like other alert types.
 
 ## Next steps
 - Get an [overview of alerts](alerts-overview.md).
@@ -216,3 +216,4 @@ Prometheus alerts are based on Prometheus metric values stored in [Azure Monitor
 
 
 
+

articles/azure-monitor/essentials/data-platform-metrics.md

@@ -64,6 +64,11 @@ Azure Monitor provides REST APIs that allow you to get data in and out of Azure
 - **Azure Monitor Metrics REST API** - Allows you to access Azure Monitor platform metrics definitions and values. For more information, see [Azure Monitor REST API](/rest/api/monitor/).  For information on how to use the API, see the [Azure monitoring REST API walkthrough](./rest-api-walkthrough.md).
 - **Azure Monitor Metrics Data plane REST API**  - [Azure Monitor Metrics data plane API](/rest/api/monitor/metrics-data-plane/) is a high-volume API designed for customers with large volume metrics queries. It's similar to the existing standard Azure Monitor Metrics REST API, but provides the capability to retrieve metric data for up to 50 resource IDs in the same subscription and region in a single batch API call. This improves query throughput and reduces the risk of throttling.   
 
+## Security
+
+All communication between connected systems and the Azure Monitor service is encrypted using the TLS 1.2 (HTTPS) protocol. The Microsoft SDL process is followed to ensure all Azure services are up-to-date with the most recent advances in cryptographic protocols.  
+
+Secure connection is established between the agent and the Azure Monitor service using certificate-based authentication and TLS with port 443. Azure Monitor uses a secret store to generate and maintain keys. Private keys are rotated every 90 days and are stored in Azure and are managed by the Azure operations who follow strict regulatory and compliance practices. For more information on security, see  [Encryption of data in transit](../../security/fundamentals/encryption-overview.md#encryption-of-data-in-transit), [Encryption of data at rest](../../security/fundamentals/encryption-atrest.md), and [Azure Monitor Logs data security](../logs/data-security.md)
 
 ## Metrics Explorer
 
@@ -75,7 +80,7 @@ For more information, see [Getting started with Azure Monitor Metrics Explorer](
 
 ## Data structure
 
-Data that Azure Monitor Metrics collects is stored in a time-series database that's optimized for analyzing time-stamped data. Each set of metric values is a time series with the following properties:
+Data that Azure Monitor Metrics collects, is stored in a time-series database that's optimized for analyzing time-stamped data. Each set of metric values is a time series with the following properties:
 
 * The time when the value was collected.
 * The resource that the value is associated with.

articles/azure-monitor/logs/change-pricing-tier.md

@@ -2,6 +2,9 @@
 title: Change pricing tier for Log Analytics workspace
 description: Details on how to change pricing tier for Log Analytics workspace in Azure Monitor.
 ms.topic: conceptual
+author: guywild
+ms.author: guywild
+ms.reviewer: Dale.Koetke
 ms.date: 03/25/2022
 ---
 

articles/azure-monitor/logs/data-security.md

@@ -5,7 +5,7 @@ ms.topic: conceptual
 author: guywild
 ms.author: guywild
 ms.reviewer: MeirMen
-ms.date: 03/21/2022
+ms.date: 07/02/2023
 
 ---
 

articles/azure-monitor/logs/logs-export-logic-app.md

@@ -4,7 +4,7 @@ description: This article describes a method to use Azure Logic Apps to query da
 ms.service: azure-monitor
 ms.topic: conceptual
 ms.reviewer: yossiy
-ms.date: 05/01/2023
+ms.date: 07/02/2023
 ---
 
 

articles/azure-monitor/logs/move-workspace-region.md

@@ -3,7 +3,7 @@ title: Move a Log Analytics workspace to another Azure region by using the Azure
 description: Use an Azure Resource Manager template to move a Log Analytics workspace from one Azure region to another by using the Azure portal.
 ms.topic: how-to
 ms.custom: devx-track-arm-template
-ms.date: 08/17/2021
+ms.date: 07/02/2023
 ms.reviewer: yossiy
 ---
 

articles/azure-monitor/logs/powershell-workspace-configuration.md

@@ -4,7 +4,7 @@ description: PowerShell samples show how to configure a Log Analytics workspace
 ms.topic: conceptual
 author: guywi-ms
 ms.author: guywild
-ms.date: 03/28/2022
+ms.date: 07/02/2023
 ms.reviewer: yossiy
 ms.custom: devx-track-azurepowershell
 

articles/azure-monitor/logs/quick-create-workspace.md

@@ -4,7 +4,7 @@ description: Learn how to create a Log Analytics workspace to enable management
 ms.topic: conceptual
 author: guywi-ms
 ms.author: guywild
-ms.date: 03/28/2022
+ms.date: 07/02/2023
 ms.reviewer: yossiy
 
 # Customer intent: As a DevOps engineer or IT expert, I want to set up a workspace to collect logs from multiple data sources from Azure, on-premises, and third-party cloud deployments.