Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into yelevin/import-export-automation-rules

Author: yelevin

articles/ai-services/openai/includes/batch/batch-python.md

@@ -266,7 +266,7 @@ Observe that there's both `error_file_id` and a separate `output_file_id`. Use t
 ```python
 import json
 
-response = client.files.content(batch_response.output_file_id)
+file_response = client.files.content(batch_response.output_file_id)
 raw_responses = file_response.text.strip().split('\n')  
 
 for raw_response in raw_responses:  

articles/ai-services/speech-service/language-learning-with-pronunciation-assessment.md

@@ -75,3 +75,4 @@ To get started with language learning through chatting, follow these steps:
 
 - Use [pronunciation assessment with the Speech SDK](how-to-pronunciation-assessment.md)
 - Try [pronunciation assessment in the studio](pronunciation-assessment-tool.md).
+- Read our [pronunciation assessment blog](https://techcommunity.microsoft.com/t5/ai-azure-ai-services-blog/speech-pronunciation-assessment-is-generally-available/ba-p/3740894) to learn more speech scenarios.

articles/ai-services/speech-service/media/pronunciation-assessment/language-learning-assess-report.png

@@ -347,8 +347,7 @@ Looks like we scored 5 for coherence and fluency of the LLM responses on this co
 For more information on how to use prompt flow evaluators, including how to make your own custom evaluators and log evaluation results to AI Studio, be sure to check out [Evaluate your app using the prompt flow SDK](../how-to/develop/flow-evaluate-sdk.md).
 
 
-## Related content
+## Next step
 
-- [Quickstart: Create a project and use the chat playground in Azure AI Studio](./get-started-playground.md)
-- [Work with projects in VS Code](../how-to/develop/vscode.md)
-- [Overview of the Azure AI SDKs](../how-to/develop/sdk-overview.md)
+> [!div class="nextstepaction"]
+> [Augment the model with data for retrieval augmented generation (RAG)](../tutorials/copilot-sdk-build-rag.md)

articles/ai-services/speech-service/media/pronunciation-assessment/language-learning-feedback-improve.png

@@ -1,9 +1,9 @@
 ---
 title: 'IT Service Management Connector: Secure Webhook in Azure Monitor - Azure configurations'
 description: This article shows you how to configure Azure to connect your ITSM products or services with Secure Webhook in Azure Monitor to centrally monitor and manage ITSM work items.
-ms.author: abbyweisberg
+ms.author: nolavime
 ms.topic: conceptual
-ms.date: 06/19/2023
+ms.date: 07/30/2024
 ms.reviewer: nolavime
 ---
 

articles/ai-studio/quickstarts/get-started-code.md

@@ -13,16 +13,17 @@ ms.reviewer: orens
 
 The Azure Monitor Activity Log is a platform log that provides insight into subscription-level events. The Activity Log includes information like when a resource is modified or a virtual machine is started. You can view the Activity Log in the Azure portal or retrieve entries with PowerShell and the Azure CLI. This article provides information on how to view the Activity Log and send it to different destinations.
 
-For more functionality, create a diagnostic setting to send the Activity Log to one or more of these locations for the following reasons:
+Create a diagnostic setting to send the Activity Log to one or more of these locations:
+ - [Log Analytics workspace](#send-to-log-analytics-workspace) for more complex querying and alerting
+ - [Azure Event Hubs](#send-to-azure-event-hubs) to forwarding logs outside of Azure.
+ - [Azure Storage](#send-to-azure-storage) for cheaper, long-term archiving.
 
-- Send to [Azure Monitor Logs](../logs/data-platform-logs.md) for more complex querying and alerting and for [longer retention of up to 12 years](../logs/data-retention-configure.md).
-- Send to Azure Event Hubs to forward outside of Azure.
-- Send to Azure Storage for cheaper, long-term archiving.
 
 For details on how to create a diagnostic setting, see [Create diagnostic settings to send platform logs and metrics to different destinations](./diagnostic-settings.md).
 > [!TIP]
-> * Sending logs to Log Analytics workspace if free of charge for the default retention period.
-> * Send to Azure Monitor Logs for more complex querying and alerting and for longer retention of up to 12 years.
+> Send Activity Logs to a Log Analytics workspace for the following benefits:
+> * Sending logs to a Log Analytics workspace is free of charge for the default retention period.
+> * Send logs to a Log Analytics workspace for [longer retention of up to 12 years](../logs/data-retention-configure.md).
 > * Logs exported to a Log Analytics workspace can be [shown in Power BI](/power-bi/transform-model/log-analytics/desktop-log-analytics-overview)
 > * [Insights](./activity-log-insights.md) are provided for Activity Logs exported to Log Analytics.
 
@@ -248,12 +249,12 @@ If a log profile already exists, you first must remove the existing log profile,
    ```
     | Property | Required | Description |
     | --- | --- | --- |
-    | name |Yes |Name of your log profile. |
-    | storage-account-id |Yes |Resource ID of the storage account to which activity logs should be saved. |
-    | locations |Yes |Space-separated list of regions for which you want to collect activity log events. View a list of all regions for your subscription by using `az account list-locations --query [].name`. |
-    | days |Yes |Number of days for which events should be retained, from 1 through 365. A value of zero stores the logs indefinitely (forever). If zero, then the enabled parameter should be set to False. |
-    |enabled | Yes |True or False. Used to enable or disable the retention policy. If True, then the `days` parameter must be a value greater than zero.
-    | categories |Yes |Space-separated list of event categories that should be collected. Possible values are Write, Delete, and Action. |
+    | `name` |Yes |Name of your log profile. |
+    | `storage-account-id` |Yes |Resource ID of the storage account to which activity logs should be saved. |
+    | `locations` |Yes |Space-separated list of regions for which you want to collect activity log events. View a list of all regions for your subscription by using `az account list-locations --query [].name`. |
+    | `days` |Yes |Number of days for which events should be retained, from 1 through 365. A value of zero stores the logs indefinitely (forever). If zero, then the enabled parameter should be set to False. |
+    |`enabled` | Yes |True or False. Used to enable or disable the retention policy. If True, then the `days` parameter must be a value greater than zero.
+    | `categories` |Yes |Space-separated list of event categories that should be collected. Possible values are Write, Delete, and Action. |
 
 
 ---
@@ -262,7 +263,7 @@ If a log profile already exists, you first must remove the existing log profile,
 
 The Export activity logs experience sends the same data as the legacy method used to send the activity log with some changes to the structure of the `AzureActivity` table.
 
-The columns in the following table have been deprecated in the updated schema. They still exist in `AzureActivity`, but they have no data. The replacements for these columns aren't new, but they contain the same data as the deprecated column. They're in a different format, so you might need to modify log queries that use them.
+The columns in the following table are deprecated in the updated schema. They still exist in `AzureActivity`, but they have no data. The replacements for these columns aren't new, but they contain the same data as the deprecated column. They're in a different format, so you might need to modify log queries that use them.
 
 |Activity log JSON | 	Log Analytics column name<br/>*(older deprecated)*	| New Log Analytics column name |	Notes |
 |:---------|:---------|:---------|:---------|

articles/azure-monitor/alerts/itsm-connector-secure-webhook-connections-azure-configuration.md

@@ -2,16 +2,21 @@
 title: Troubleshoot why data is no longer being collected in Azure Monitor
 description: Steps to take if data is no longer being collected in Log Analytics workspace in Azure Monitor.
 ms.topic: conceptual
-ms.date: 07/25/2023
+ms.date: 08/06/2024
 ---
 
 # Troubleshoot why data is no longer being collected in Azure Monitor
-This article provides guidance to detect when data collection in Azure Monitor stops and steps you can take to determine and correct the causes.
+This article explains how to detect when data collection in Azure Monitor stops and details steps you can take to address data collection issues.
 
 > [!IMPORTANT]
 > If you're troubleshooting data collection for a scenario that uses a data collection rule (DCR) such as Azure Monitor agent or Logs ingestion API, see [Monitor and troubleshoot DCR data collection in Azure Monitor](../essentials/data-collection-monitor.md) for additional troubleshooting information.
 
-## Data collection status
+## Daily cap reached
+
+The [daily cap](daily-cap.md) limits the amount of data that a Log Analytics workspace can collect in a day. When the daily cap is reached, data collection stops until the reset time. You can either wait for collection to automatically restart, or increase the daily data volume limit.
+
+#### Check Log Analytics workspace data collection status
+
 When data collection in a Log Analytics workspace stops, an event with a type of **Operation** is created in the workspace. Run the following query to check whether you're reaching the daily limit and missing data: 
 
 ```kusto
@@ -22,38 +27,50 @@ When data collection stops, the **OperationStatus** is **Warning**. When data co
 
 To be notified when data collection stops, use the steps described in the [Alert when daily cap is reached](daily-cap.md#alert-when-daily-cap-is-reached) section. To configure an e-mail, webhook, or runbook action for the alert rule, use the steps described in [create an action group](../alerts/action-groups.md). 
 
-## Daily cap was reached
-The [daily cap](daily-cap.md) limits the amount of data that a Log Analytics workspace can collect in a day. If the daily cap is reached, then data collection will stop until the reset time. Either wait for collection to automatically restart, or increase the daily data volume limit.
-
+## Ingestion volume rate limit reached
+The [default ingestion volume rate limit](../service-limits.md#log-analytics-workspaces) for data sent from Azure resources using diagnostic settings is approximately 6 GB/min per workspace. This is an approximate value because the actual size can vary between data types, depending on the log length and its compression ratio. This limit doesn't apply to data that's sent from agents or the [Logs ingestion API](logs-ingestion-api-overview.md). 
 
-## Legacy free pricing tier
-If your Log Analytics workspace is on the [legacy Free pricing tier](cost-logs.md#legacy-pricing-tiers) and has collected more than 500 MB of data in a day, data collection stops for the rest of the day. Wait until the following day for collection to automatically restart, or change to a paid pricing tier.
+If you send data at a higher rate to a single workspace, some data is dropped, and an event is sent to the **Operation** table in your workspace every six hours while the threshold continues to be exceeded. If your ingestion volume continues to exceed the rate limit or you're expecting to reach it sometime soon, you can request an increase to your workspace by sending an email to [email protected] or by opening a support request. 
 
+#### Check whether your workspace reached its data ingestion rate limit
 
-## Workspace reached the data ingestion volume rate
-The [default ingestion volume rate limit](../service-limits.md#log-analytics-workspaces)  for data sent from Azure resources using diagnostic settings is approximately 6 GB/min per workspace. This is an approximate value because the actual size can vary between data types, depending on the log length and its compression ratio. This limit doesn't apply to data that's sent from agents or the [Data Collector API](data-collector-api.md). 
-
-If you send data at a higher rate to a single workspace, some data is dropped, and an event is sent to the **Operation** table in your workspace every 6 hours while the threshold continues to be exceeded. If your ingestion volume continues to exceed the rate limit or you are expecting to reach it sometime soon, you can request an increase to your workspace by sending an email to [email protected] or by opening a support request. 
-
-Use the following query to retrieve the record that indicates the data ingestion rate limit was reached.
+Use this query to retrieve the record that indicates the data ingestion rate limit was reached.
 
 ```kusto
 Operation 
 | where OperationCategory == "Ingestion" 
 | where Detail startswith "The rate of data crossed the threshold"
 ```
+## Legacy free pricing tier daily ingestion limit reached 
+If your Log Analytics workspace is in the [legacy Free pricing tier](cost-logs.md#legacy-pricing-tiers) and has collected more than 500 MB of data in a day, data collection stops for the rest of the day. Wait until the following day for collection to automatically restart, or change to a paid pricing tier.
+
+## Azure Monitor Agent not sending data
+
+[Azure Monitor Agent](../agents/azure-monitor-agent-overview.md) collects data from virtual machines and sends the data to Azure Monitor. An agent might stop sending data to your Log Analytics workspace in various scenarios. For example, when [Azure Site Recovery](/azure/site-recovery/site-recovery-overview) recovers a virtual machine in a disaster recovery scenario, the resource ID of the machine changes, requiring reinstallation of Azure Monitor Agent on the machine.
 
-## Azure subscription is in a suspended state 
+#### Check the health of agents sending data to your workspace
+
+Azure Monitor Agent instances installed on all virtual machines that send data to your Log Analytics workspace send a heartbeat to the [Heartbeat table](/azure/azure-monitor/reference/tables/heartbeat) every minute.
+
+Run this query to list VMs that haven't reported a heartbeat in the last five minutes:
+
+```kusto
+Heartbeat 
+| where TimeGenerated > ago(24h)
+| summarize LastCall = max(TimeGenerated) by Computer, _ResourceId
+| where LastCall < ago(5m)
+```
+
+## Azure subscription is suspended 
 Your Azure subscription could be in a suspended state for one of the following reasons:
 
 - Free trial ended
 - Azure pass expired
 - Monthly spending limit reached (such as on an MSDN or Visual Studio subscription)
 
+## Other Log Analytics workspace limits
 
-## Limits summary
-
-There are additional Log Analytics limits, some of which depend on the Log Analytics pricing tier. These are documented at [Azure subscription and service limits, quotas, and constraints](../service-limits.md#log-analytics-workspaces).
+There are other Log Analytics limits, some of which depend on the Log Analytics pricing tier. For more information, see [Azure subscription and service limits, quotas, and constraints](../service-limits.md#log-analytics-workspaces).
 
 
 ## Next steps