Merge pull request #2739 from MicrosoftDocs/main638940493657534218sync_temp

For protected branch, push strategy should use PR and merge to target branch method to work around git push error

Author: learn-build-service-prod[bot]

data-explorer/ingest-data-overview.md

@@ -1,9 +1,10 @@
 ---
 title: Azure Data Explorer data ingestion overview
-description: Learn about the different ways you can ingest (load) data in Azure Data Explorer
+description: Discover Azure Data Explorer's data ingestion options, including streaming, batch queues, and direct ingestion, for real-time analytics and historical data needs.
 ms.reviewer: akshay.dixit
 ms.topic: conceptual
-ms.date: 05/29/2025
+ms.date: 09/10/2025
+Search Keywords: Azure Data Explorer, Kusto, data ingestion, streaming ingestion, queued ingestion, batched ingestion, direct ingestion, data formats, ingestion methods, data pipelines, real-time analytics, historical data
 ---
 
 # Azure Data Explorer data ingestion overview
@@ -13,7 +14,9 @@ Data ingestion involves loading data into a table in your cluster. Azure Data Ex
 Azure Data Explorer offers one-time ingestion or the establishment of a continuous ingestion pipeline, using either streaming or queued ingestion. To determine which is right for you, see [One-time data ingestion](#one-time-data-ingestion) and [Continuous data ingestion](#continuous-data-ingestion).
 
 > [!NOTE]
-> Data is persisted in storage according to the set [retention policy](/kusto/management/retention-policy?view=azure-data-explorer&preserve-view=true).
+>
+> * Data is persisted in storage according to the set [retention policy](/kusto/management/retention-policy?view=azure-data-explorer&preserve-view=true).
+> * If a single string value in a record, or the entire record, exceeds the allowed data limit of 64MB, ingestion fails.
 
 ## One-time data ingestion
 

data-explorer/kusto/management/batching-policy.md

@@ -3,12 +3,11 @@ title: IngestionBatching policy
 description: Learn how to use the IngestionBatching policy to optimize batching for ingestion.
 ms.reviewer: orspodek
 ms.topic: reference
-ms.date: 08/21/2024
+ms.date: 09/21/2025
+Search Keywords: IngestionBatching, ingestion batching, batching policy, ingestion optimization, data ingestion settings, Azure Data Explorer ingestion, Kusto ingestion, data batching, ingestion performance 
 ---
 # Ingestion batching policy
 
-## Overview
-
 > [!INCLUDE [applies](../includes/applies-to-version/applies.md)] [!INCLUDE [fabric](../includes/applies-to-version/fabric.md)] [!INCLUDE [azure-data-explorer](../includes/applies-to-version/azure-data-explorer.md)]
 
 During the queued ingestion process, the service optimizes for throughput by batching small ingress data chunks together before ingestion. Batching reduces the resources consumed by the queued ingestion process and doesn't require post-ingestion resources to optimize the small data shards produced by non-batched ingestion.

data-explorer/kusto/query/ai-chat-completion-prompt-plugin.md

@@ -153,7 +153,10 @@ The following example sends a separate prompt for each row to the Azure OpenAI c
 let connectionString = 'https://myaccount.openai.azure.com/openai/deployments/gpt4o/chat/completion?api-version=2024-06-01;managed_identity=system';
 let options = dynamic({
   "RetriesOnThrottling": 1,
-  "GlobalTimeout": 2m
+  "GlobalTimeout": 2m,
+  "ModelParameters": {
+    "temperature: 0.7
+  }
 });
 datatable(Prompt: string)
 [
@@ -171,7 +174,10 @@ datatable(Prompt: string)
 let connectionString = 'https://myaccount.openai.azure.com/openai/deployments/gpt4o/chat/completions?api-version=2024-06-01;impersonate';
 let options = dynamic({
   "RetriesOnThrottling": 1,
-  "GlobalTimeout": 2m
+  "GlobalTimeout": 2m,
+  "ModelParameters": {
+    "temperature: 0.7
+  }
 });
 datatable(Prompt: string)
 [
@@ -189,3 +195,4 @@ datatable(Prompt: string)
 
 * [ai_embeddings()](ai-embeddings-plugin.md)
 * [ai_chat_completion()](ai-chat-completion-plugin.md)
+