Repo sync for protected branch

data-explorer/kusto/management/create-or-alter-workload-group-command.md

@@ -93,10 +93,6 @@ Create **MyWorkloadGroup** workload group with a full definition of its request
     "MaxExecutionTime": {
       "IsRelaxable": true,
       "Value": "00:04:00"
-    },
-    "QueryResultsCacheMaxAge": {
-      "IsRelaxable": true,
-      "Value": "00:05:00"
     }
   }
 } ```
@@ -147,10 +143,6 @@ Create **My Workload Group** workload group with a full definition of its reques
     "MaxExecutionTime": {
       "IsRelaxable": true,
       "Value": "00:04:00"
-    },
-    "QueryResultsCacheMaxAge": {
-      "IsRelaxable": true,
-      "Value": "00:05:00"
     }
   },
   "RequestRateLimitPolicies": [

data-explorer/kusto/management/data-export/continuous-data-export.md

@@ -3,7 +3,7 @@ title:  Continuous data export
 description:  This article describes Continuous data export.
 ms.reviewer: yifats
 ms.topic: reference
-ms.date: 02/09/2026
+ms.date: 08/25/2026
 ---
 # Continuous data export overview
 
@@ -117,11 +117,81 @@ To create a continuous export job with a query that references a table with [Row
 
 ## Continuous export to delta table
 
-
 > [!IMPORTANT]
 > Delta table partitioning isn't supported in continuous data export.
 >
-> Kusto won't write to existing delta tables if the [delta protocol writer version](https://github.com/delta-io/delta/blob/master/PROTOCOL.md#schema-serialization-format) is higher than 1.
+> Kusto won't write to existing delta tables if the [delta protocol writer version](https://github.com/delta-io/delta/blob/master/PROTOCOL.md#schema-serialization-format) is higher than 1. The destination Delta table must use minimum reader version 1 and minimum writer version 1.
+
+::: moniker range="microsoft-fabric"
+
+Features such as `NOT NULL` constraints can increase the minimum Delta writer version and cause continuous export to fail with the following error:
+
+```text
+Unsupported minimum writer version: 2
+```
+
+In this example scenario, you have a `Customers` table that receives customer records from several departments. You want to continuously export new records for customers associated with the Sales department to a Delta table in a Lakehouse. The continuous export query filters the source table by department name and projects the columns that match the destination table schema.
+
+If you receive this error:
+
+1. Create a new Delta table in a Lakehouse notebook. Omit `NOT NULL` constraints and explicitly set both protocol versions to 1.
+
+    ```sql
+    %%sql
+    CREATE TABLE CustomersExportV1 (
+        CustomerId STRING,
+        Name STRING,
+        Address STRING,
+        City STRING,
+        DepartmentName STRING
+    )
+    USING DELTA
+    TBLPROPERTIES (
+        'delta.minReaderVersion' = '1',
+        'delta.minWriterVersion' = '1'
+    );
+    ```
+
+1. Create or recreate the Eventhouse shortcut so that it targets the new Delta table. Name the shortcut `customers`. The shortcut is exposed in the Eventhouse database as an external table.
+
+    :::image type="content" source="../../media/continuous-export/create-eventhouse-shortcut.png" alt-text="Screenshot of the Eventhouse database explorer with the New shortcut menu selected and existing shortcuts listed." lightbox="../../media/continuous-export/create-eventhouse-shortcut.png":::
+
+1. Create the source table and a continuous export that targets the external table. Then add sample records so that the continuous export processes them:
+
+    ```kusto
+    // Creates the source table.
+    .create table Customers (
+        customerId:string,
+        Name:string,
+        address:string,
+        City:string,
+        departmentName:string
+    )
+
+    // Continuously exports customers associated with the Sales department.
+    .create-or-alter continuous-export CustomersSalesExport
+    over (Customers)
+    to table customers
+    with (
+        intervalBetweenRuns=10m,
+        managedIdentity="system"
+    )
+    <| Customers
+    | where departmentName == "Sales"
+    | project customerId, Name, address, City, departmentName
+
+    // Adds sample customers after the continuous export is created.
+    .ingest inline into table Customers <|
+    C001,Contoso Madrid,Calle de Alcala 10,Madrid,Sales
+    C002,Fabrikam Barcelona,Avinguda Diagonal 20,Barcelona,Sales
+    C003,Northwind London,10 King Street,London,Marketing
+    C004,Adventure Works Paris,25 Rue de Rivoli,Paris,Finance
+    C005,Wide World Berlin,40 Friedrichstrasse,Berlin,Operations
+    ```
+
+Use a new table name if the protocol of an existing Delta table was upgraded. Changing table properties doesn't safely downgrade the Delta protocol of an existing table. For a noncontinuous export example, see [Export to a Delta table in Eventhouse](export-data-to-an-external-table.md#export-to-a-delta-table-in-eventhouse).
+
+::: moniker-end
 
 To define continuous export to a delta table, do the following steps:
 

data-explorer/kusto/management/data-export/export-data-to-an-external-table.md

@@ -3,7 +3,7 @@ title:  .export to table
 description:  This article describes Export data to an external table.
 ms.reviewer: alexans
 ms.topic: reference
-ms.date: 12/01/2024
+ms.date: 08/25/2026
 ---
 # .export to table
 
@@ -90,6 +90,75 @@ In order to export to an external table, you must set up write permissions. For
 
 * Parquet native export is a more performant, resource light export mechanism. An exported `datetime` column is currently unsupported by Synapse SQL `COPY`.
 
+::: moniker range="microsoft-fabric"
+
+### Export to a Delta table in Eventhouse
+
+The destination Delta table must use minimum reader version 1 and minimum writer version 1. Features such as `NOT NULL` constraints can increase the minimum writer version and cause the export to fail with the following error:
+
+```text
+Unsupported minimum writer version: 2
+```
+
+In this example scenario, you have a `Customers` table that contains customers associated with several departments. You want to export only the customers associated with the Sales department to a Delta table in a Lakehouse. The export query filters the source table by department name and projects the columns that match the destination table schema.
+
+To resolve this error:
+
+1. Create a new Delta table in a Lakehouse notebook. Omit `NOT NULL` constraints and explicitly set both protocol versions to 1.
+
+    ```sql
+    %%sql
+    CREATE TABLE CustomersExportV1 (
+        CustomerId STRING,
+        Name STRING,
+        Address STRING,
+        City STRING,
+        DepartmentName STRING
+    )
+    USING DELTA
+    TBLPROPERTIES (
+        'delta.minReaderVersion' = '1',
+        'delta.minWriterVersion' = '1'
+    );
+    ```
+
+1. Create or recreate the Eventhouse shortcut so that it targets the new Delta table. Name the shortcut `customers`. The shortcut is exposed in the Eventhouse database as an external table.
+
+    :::image type="content" source="../../media/continuous-export/create-eventhouse-shortcut.png" alt-text="Screenshot of the Eventhouse database explorer with the New shortcut menu selected and existing shortcuts listed." lightbox="../../media/continuous-export/create-eventhouse-shortcut.png":::
+
+1. Create the source table, add sample records, and export the customers associated with the Sales department to the external table:
+
+    ```kusto
+    // Creates the source table.
+    .create table Customers (
+        customerId:string,
+        Name:string,
+        address:string,
+        City:string,
+        departmentName:string
+    )
+
+    // Adds sample customers associated with several departments.
+    .ingest inline into table Customers <|
+    C001,Contoso Madrid,Calle de Alcala 10,Madrid,Sales
+    C002,Fabrikam Barcelona,Avinguda Diagonal 20,Barcelona,Sales
+    C003,Northwind London,10 King Street,London,Marketing
+    C004,Adventure Works Paris,25 Rue de Rivoli,Paris,Finance
+    C005,Wide World Berlin,40 Friedrichstrasse,Berlin,Operations
+
+    // Exports customers associated with the Sales department.
+    .export to table customers
+    <| Customers
+    | where departmentName == "Sales"
+    | project customerId, Name, address, City, departmentName
+    ```
+
+Use a new table name if the protocol of an existing Delta table was upgraded. Changing table properties doesn't safely downgrade the Delta protocol of an existing table.
+
+This protocol requirement also applies to [continuous export](continuous-data-export.md#continuous-export-to-delta-table).
+
+::: moniker-end
+
 ### Number of files
 
 The number of files written per partition depends on the [distribution settings](#distribution-settings) of the export operation:

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

@@ -34,20 +34,38 @@ 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": {
-    "IsRelaxable": true,
-    "Value": "Weak"
-  },
-  "CachedResultsMaxAge": {
-    "IsRelaxable": true,
-    "Value": "00:05:00"
-  }
+This policy configuration sets query consistency to weak.
+
+````kusto
+.alter-merge workload_group ['<my workload group>'] ```
+{
+  "QueryConsistencyPolicy": 
+  {
+    "QueryConsistency": {
+      "IsRelaxable": true,
+      "Value": "Weak"
+    }
+  } 
+}
+```
+````
+
+This policy configuration sets the maximum age for cached results to 5 minutes.
+
+````kusto
+.alter-merge workload_group ['<my workload group>'] ```
+{
+  "QueryConsistencyPolicy": 
+  {
+    "CachedResultsMaxAge": {
+      "IsRelaxable": true,
+      "Value": "00:05:00"
+    }
+  } 
 }
+
 ```
+````
 
 ::: moniker range="azure-data-explorer"
 ## Monitoring