Repo sync for protected branch

data-explorer/create-event-grid-connection.md

@@ -2,7 +2,7 @@
 title: Create an Event Grid data connection - Azure Data Explorer
 description: Learn how to create an Event Grid data connection to ingest data into Azure Data Explorer.
 ms.topic: how-to
-ms.date: 06/10/2025
+ms.date: 02/08/2026
 ms.custom: sfi-ropc-nochange
 ---
 
@@ -74,7 +74,6 @@ In this section, you establish a connection between Event Grid and your Azure Da
         | Table name | *TestTable* | The table you created in **TestDatabase**. |
         | Data format | *JSON* | Supported formats are APACHEAVRO, Avro, CSV, JSON, ORC, PARQUET, PSV, RAW, SCSV, SOHSV, TSV, TSVE, TXT, and W3CLOG. Supported compression options are zip and gzip. |
         | Mapping name | *TestTable_mapping* | The mapping you created in **TestDatabase**, which maps incoming data to the column names and data types of **TestTable**. If not specified, an [identity data mapping](/kusto/management/mappings?view=azure-data-explorer&preserve-view=true#identity-mapping) derived from the table's schema is autogenerated. |
-        | Ignore format errors | *Ignore* | Toggle on this option if you want to ignore format errors for JSON data format.|
 
         > [!NOTE]
         > Table and mapping names are case-sensitive.

data-explorer/create-iot-hub-connection.md

@@ -2,7 +2,7 @@
 title: 'Create an IoT Hub data connection - Azure Data Explorer'
 description: 'In this article, you learn how to ingest data into Azure Data Explorer from IoT Hub.'
 ms.topic: how-to
-ms.date: 07/16/2023
+ms.date: 02/08/2026
 ---
 
 # Create an IoT Hub data connection for Azure Data Explorer
@@ -15,7 +15,7 @@ For general information about ingesting into Azure Data Explorer from IoT Hub, s
 
 > [!NOTE]
 > Only events enqueued after you create the data connection are ingested.
-
+>
 > For code samples based on previous SDK versions, see the [archived article](/previous-versions/azure/data-explorer/create-iot-hub-connection).
 
 ## Prerequisites
@@ -75,7 +75,7 @@ In this section, you'll establish a connection between the IoT Hub and your Azur
 
     > [!NOTE]
     >
-    > * JSON data is parsed as multijson by default. Select **Ignore format errors** to ingest the data in strict JSON format.
+    > * JSON data is parsed as multijson by default.
     > * If you selected **Event system properties**, you must include [system properties](ingest-data-iot-hub-overview.md#system-properties) in the table schema and mapping.
 
 1. Select **Create**.

data-explorer/get-data-file.md

@@ -3,7 +3,7 @@ title: Get data from a file
 description: Learn how to get data from a local file in Azure Data Explorer.
 ms.reviewer: sharmaanshul
 ms.topic: how-to
-ms.date: 12/04/2023
+ms.date: 02/08/2026
 ms.custom: sfi-image-nochange
 ---
 # Get data from file

data-explorer/includes/get-data-advanced-options.md

@@ -1,20 +1,18 @@
 ---
 ms.service: azure
 ms.topic: include
-ms.date: 08/07/2023
+ms.date: 02/08/2026
 ---
 ### Advanced options based on data type
 
 **Tabular (CSV, TSV, PSV)**:
 
-* If you're ingesting tabular formats in an *existing table*, you can select **Advanced** > **Keep current table schema**. Tabular data doesn't necessarily include the column names that are used to map source data to the existing columns. When this option is checked, mapping is done by-order, and the table schema remains the same. If this option is unchecked, new columns are created for incoming data, regardless of data structure.
-* To use the first row as column names, select  **Advanced** > **First row is column header**.
+* If you're ingesting tabular formats in an *existing table*, you can select the table mapping drop-down and select **Use exixting mapping**. Tabular data doesn't necessarily include the column names that are used to map source data to the existing columns. When this option is checked, mapping is done by-order, and the table schema remains the same. 
+* Otherwise, create a new mapping.
+* To use the first row as column names, select **First row header**.
 
-    :::image type="content" source="../media/get-data-file/advanced-csv.png" alt-text="Screenshot of advanced CSV options.":::
+    :::image type="content" source="../media/get-data-file/add-mapping.png" alt-text="Screenshot of mapping options.":::
 
 **JSON**:
 
-* To determine column division of JSON data, select **Advanced** > **Nested levels**, from 1 to 100. 
-* If you select **Advanced** > **Ignore data format errors**, the data is ingested in JSON format. If you leave this check box unselected, the data is ingested in multijson format.
-
-    :::image type="content" source="../media/get-data-file/advanced-json.png" alt-text="Screenshot of advanced JSON options.":::
+* To determine column division of JSON data, select **Nested levels**, from 1 to 100.