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

Author: Learn Build Service GitHub App

data-explorer/ingest-data-overview.md

@@ -3,7 +3,7 @@ title: Azure Data Explorer data ingestion overview
 description: Learn about the different ways you can ingest (load) data in Azure Data Explorer
 ms.reviewer: akshay.dixit
 ms.topic: conceptual
-ms.date: 02/16/2024
+ms.date: 04/07/2025
 ---
 
 # Azure Data Explorer data ingestion overview
@@ -79,8 +79,7 @@ Azure Data Explorer offers the following ingestion management commands, which in
 * **Ingest from storage**: The [.ingest into command](/kusto/management/data-ingestion/ingest-from-storage?view=azure-data-explorer&preserve-view=true) gets the data to ingest from external storage, such as Azure Blob Storage, accessible by your cluster and pointed-to by the command.
 
 > [!NOTE]
-> In the event of a failure, ingestion is performed again and is retried for up to 48 hours using the exponential backoff method for wait time between tries.
-
+> In the event of a failure, ingestion is performed again, and is retried for up to 48 hours using the exponential backoff method for wait time between tries.
 
 ## Compare ingestion methods
 
@@ -89,7 +88,7 @@ The following table compares the main ingestion methods:
 | Ingestion name | Data type | Maximum file size | Streaming, queued, direct | Most common scenarios | Considerations |
 |--|--|--|--|--|--|
 | [Apache Spark connector](spark-connector.md) | Every format supported by the Spark environment | Unlimited | Queued | Existing pipeline, preprocessing on Spark before ingestion, fast way to create a safe (Spark) streaming pipeline from the various sources the Spark environment supports. | Consider cost of Spark cluster. For batch write, compare with Azure Data Explorer data connection for Event Grid. For Spark streaming, compare with the data connection for event hub. |
-| [Azure Data Factory (ADF)](data-factory-integration.md) | [Supported data formats](/azure/data-factory/copy-activity-overview#supported-data-stores-and-formats) | Unlimited. Inherits ADF restrictions. | Queued or per ADF trigger | Supports formats that are unsupported, such as Excel and XML, and can copy large files from over 90 sources, from on perm to cloud | This method takes relatively more time until data is ingested. ADF uploads all data to memory and then begins ingestion. |
+| [Azure Data Factory (ADF)](data-factory-integration.md) | [Supported data formats](/azure/data-factory/copy-activity-overview#supported-data-stores-and-formats) | Unlimited. Inherits ADF restrictions. | Queued or per ADF trigger | Supports formats that are unsupported, such as Excel and XML, and can copy large files from over 90 sources, from on-premises to cloud | This method takes relatively more time until data is ingested. ADF uploads all data to memory and then begins ingestion. |
 | [Event Grid](ingest-data-event-grid-overview.md) | [Supported data formats](ingest-data-event-grid-overview.md#data-format) | 1 GB uncompressed | Queued | Continuous ingestion from Azure storage, external data in Azure storage | Ingestion can be triggered by blob renaming or blob creation actions |
 | [Event Hub](ingest-data-event-hub-overview.md) | [Supported data formats](ingest-data-event-hub-overview.md#data-format) | N/A | Queued, streaming | Messages, events |  |
 | [Get data experience](get-data-file.md) | *SV, JSON | 1 GB uncompressed | Queued or direct ingestion | One-off, create table schema, definition of continuous ingestion with Event Grid, bulk ingestion with container (up to 5,000 blobs; no limit when using historical ingestion) |  |
@@ -105,11 +104,22 @@ For information on other connectors, see [Connectors overview](integrate-data-ov
 
 ## Permissions
 
-The following list describes the permissions required for various ingestion scenarios:
+The following list describes the [permissions](/kusto/access-control/role-based-access-control?view=azure-data-explorer&preserve-view=true) required for various ingestion scenarios:
+
+* To create a new table, you must have at least Database User permissions.
+* To ingest data into an existing table, without changing its schema, you must have at least Table Ingestor permissions.
+* To change the schema of an existing table, you must have at least Table Admin or Database Admin permissions.
 
-* To create a new table requires at least Database User permissions.
-* To ingest data into an existing table, without changing its schema, requires at least Database Ingestor permissions.
-* To change the schema of an existing table requires at least Table Admin or Database Admin permissions.
+The following table describes the permissions required for each ingestion method:
+
+| Ingestion method | Permissions |
+|--|--|
+| [One-time ingestion](#one-time-data-ingestion) | At least Table Ingestor |
+| [Continuous streaming ingestion](#continuous-data-ingestion) | At least Table Ingestor |
+| [Continuous queued ingestion](#continuous-data-ingestion) | At least Table Ingestor |
+| [Direct inline ingestion](#direct-ingestion-with-management-commands) | At least Table Ingestor and also Database Viewer |
+| [Direct ingestion from query](#direct-ingestion-with-management-commands) | At least Table Ingestor and also Database Viewer |
+| [Direct ingestion from storage](#direct-ingestion-with-management-commands) | At least Table Ingestor |
 
 For more information, see [Kusto role-based access control](/kusto/access-control/role-based-access-control?view=azure-data-explorer&preserve-view=true).
 

data-explorer/kusto/management/query-consistency-policy.md

@@ -34,6 +34,8 @@ The following limits are configurable:
 
 ## Example
 
+This policy configuration sets query consistency to weak and the maximum age for cached results to 5 minutes.
+
 ```json
 "QueryConsistencyPolicy": {
   "QueryConsistency": {
@@ -42,7 +44,7 @@ The following limits are configurable:
   },
   "CachedResultsMaxAge": {
     "IsRelaxable": true,
-    "Value": "05:00:00"
+    "Value": "00:05:00"
   }
 }
 ```