Repo sync for protected branch

data-explorer/base-query.md

@@ -3,7 +3,7 @@ title: Create a dashboard base query
 description: Learn how to create a base query for an Azure Data Explorer dashboard.
 ms.reviewer: gabil
 ms.topic: how-to
-ms.date: 08/26/2025
+ms.date: 01/12/2026
 ---
 # Create a dashboard base query
 
@@ -43,7 +43,7 @@ To interactively explore sample dashboards, see [Quickstart: Visualize sample da
     > [!NOTE]
     > We suggest starting each base query name with an underscore (_) for easy use later, and so as not to conflict with Kusto-defined names. For more information, see [naming your entities](/kusto/query/schema-entities/entity-names?view=azure-data-explorer&preserve-view=true)
 
-    :::image type="content" source="media/base-query/create-base-query.png" alt-text="Screenshot of create base query in Azure Data Explorer dashboards.":::
+    :::image type="content" source="media/base-query/create-base-query.png" alt-text="Screenshot of create base query in Azure Data Explorer dashboards." lightbox="media/base-query/create-base-query-small.png":::
 
 1. Select a data **Source** from the dropdown.
 1. Enter the KQL query that will be used as the base query. This query can optionally contain other base queries.

data-explorer/kusto/includes/materialized-view-create-properties.md

@@ -1,7 +1,7 @@
 ---
 ms.service: azure
 ms.topic: include
-ms.date: 02/03/2025
+ms.date: 01/12/2026
 ---
 
 | Name | Type | Description |
@@ -15,4 +15,4 @@ ms.date: 02/03/2025
 | dimensionTables | array | A dynamic argument that includes an array of dimension tables in the view. See [Query parameter](../management/materialized-views/materialized-view-create.md#query-parameter). |
 | folder | `string` | The materialized view's folder. |
 | docString | `string` | A string that documents the materialized view. |
-| allowMaterializedViewsWithoutRowLevelSecurity | `bool` | Allows creating a materialized view over a table with row level security policy enabled. |
+| allowMaterializedViewsWithoutRowLevelSecurity | `bool` | Allows creating a materialized view over a table with row level security policy enabled. Only required for views of type `arg_min`/`arg_max`/`arg_any`. See [Row level security policy](../management/materialized-views/materialized-view-policies.md#row-level-security-policy) for more information. |

data-explorer/kusto/management/alter-capacity-policy-command.md

@@ -10,6 +10,8 @@ monikerRange: "azure-data-explorer"
 
 > [!INCLUDE [applies](../includes/applies-to-version/applies.md)] [!INCLUDE [azure-data-explorer](../includes/applies-to-version/azure-data-explorer.md)]
 
+> [!WARNING]
+> This command is deprecated and will be disabled soon. Use [alter-merge](alter-merge-capacity-policy-command.md) instead.
 
 Changes the cluster's [capacity policy](capacity-policy.md). A capacity policy controls the computational resources for data management operations on the cluster.
 

data-explorer/kusto/query/scan-operator.md

@@ -484,7 +484,7 @@ This section follows the [matching logic](#matching-logic) through each record o
 **Record evaluation at each step:**
 
 * `s3`: **Check 1** isn't passed because the record doesn't meet the condition of `Event == "Stop"`, and **Check 2** isn't passed because `s3` lacks an active sequence.
-* `s2`: **Check 1** isn't passed because the state of `s1` is empty. it passes **Check 2** because it meets the condition of `Ts - s1.Ts < 5m`. **Record 4** and its `m_id` (`0`) are added to the state and the output. The values from this record overwrite the previous state values for `s2.Ts` and `s2.Event`.
+* `s2`: **Check 1** isn't passed because the state of `s1` is empty. It passes **Check 2** because it meets the condition of `Ts - s1.Ts < 5m`. **Record 4** and its `m_id` (`0`) are added to the state and the output. The values from this record overwrite the previous state values for `s2.Ts` and `s2.Event`.
 * `s1`: **Check 1** is irrelevant because there's no previous step, and **Check 2** isn't passed because the record doesn't meet the condition of `Event == "Start"`.
 
 **State:**
@@ -545,7 +545,7 @@ This section follows the [matching logic](#matching-logic) through each record o
 
 * `s3`: **Check 1** isn't passed because the state of `s2` is empty, and **Check 2** isn't passed because it doesn't meet the condition of `Event == "Stop"`.
 * `s2`: **Check 1** isn't passed because the state of `s1` is empty, and **Check 2** isn't passed because `s2` lacks an active sequence.
-* `s1`: **Check 1** isn't passed because there's no previous step. it passes **Check 2** because it meets the condition of `Event == "Start"`. This match initiates a new sequence in `s1` with a new `m_id`. **Record 7** and its `m_id` (`1`) are added to the state and the output.
+* `s1`: **Check 1** isn't passed because there's no previous step. It passes **Check 2** because it meets the condition of `Event == "Start"`. This match initiates a new sequence in `s1` with a new `m_id`. **Record 7** and its `m_id` (`1`) are added to the state and the output.
 
 **State:**
 
@@ -588,7 +588,7 @@ This section follows the [matching logic](#matching-logic) through each record o
 
 * `s3`: **Check 1** is passed because `s2` is nonempty and it meets the `s3` condition of `Event == "Stop"`. This match causes the state of `s2` to be cleared and the sequence in `s2` to be promoted to `s3`. **Record 9** and its `m_id` (`1`) are added to the state and the output.
 * `s2`: **Check 1** isn't passed because the state of `s1` is empty, and **Check 2** isn't passed because `s2` lacks an active sequence.
-* `s1`: **Check 1** isn't passed because there's no previous step. it passes **Check 2** because it meets the condition of `Event == "Start"`. This match initiates a new sequence in `s1` with a new `m_id`.
+* `s1`: **Check 1** isn't passed because there's no previous step, and **Check 2** isn't passed because the record doesn't meet the condition of Event == "Start".
 
 **State:**