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

Author: Learn Build Service GitHub App

data-explorer/ingest-data-cosmos-db-queries.md

@@ -3,7 +3,7 @@ title: Get latest versions of Azure Cosmos DB documents - Azure Data Explorer
 description: Learn about how to get latest versions of Azure Cosmos DB documents in Azure Data Explorer.
 ms.reviewer: vplauzon
 ms.topic: how-to
-ms.date: 06/13/2023
+ms.date: 01/07/2025
 ---
 
 # Get latest versions of Azure Cosmos DB documents
@@ -33,7 +33,7 @@ TestTable
 | summarize arg_max(_timestamp, *) by Id
 ```
 
-If you used soft markers to mark deleted documents, you can filter them out with the following query:
+If you use [soft markers to indicate deleted documents](/azure/cosmos-db/nosql/change-feed-design-patterns?tabs=latest-version#deletes), you can filter out these documents with a query. For example, if you use a Boolean property called `IsDeleted` that indicates deleted documents, you can use the following query to filter out the soft deleted documents:
 
 ```kusto
 TestTable

data-explorer/kusto/management/alter-merge-mirroring-policy-command.md

@@ -3,7 +3,7 @@ title: .alter-merge table policy mirroring command
 description: Learn how to use the `.alter-merge table policy mirroring` command to create a logical copy of tables of your database.
 ms.reviewer: sharmaanshul
 ms.topic: reference
-ms.date: 09/23/2024
+ms.date: 01/12/2025
 monikerRange: "microsoft-fabric"
 ---
 
@@ -16,9 +16,9 @@ Changes the tables's [mirroring policy](mirroring-policy.md). The mirroring poli
 ## Syntax
 
 (`.alter` | `.alter-merge`) `table` *TableName* `policy mirroring`
-[`partition` `by` (*Partitions*)] 
-`dataformat` = `parquet`  
-[`with` (`IsEnabled`=`IsEnabledValue`)]
+[`partition` `by` (*Partitions*)]
+`dataformat` = `parquet`
+[`with` `(` *propertyName* `=` *propertyValue* [`,` ...]`)`]
 
 [!INCLUDE [syntax-conventions-note](../includes/syntax-conventions-note.md)]
 
@@ -28,17 +28,19 @@ Changes the tables's [mirroring policy](mirroring-policy.md). The mirroring poli
 |--|--|--|--|
 |*TableName*| string| :heavy_check_mark:|A table name that adheres to the [Entity names](../query/schema-entities/entity-names.md) rules.|
 |*Partitions*| string| | A comma-separated list of columns used to divide the data into smaller partitions. See [Partitions formatting](#partitions-formatting). |
+| *propertyName*, *propertyValue* | `string` | | A comma-separated list of key-value property pairs. See [supported properties](#supported-properties).|
 
 [!INCLUDE [partitions-formatting](../includes/partitions-formatting.md)]
 
 > [!NOTE]
 > Each partition is represented as a separate column using the *PartitionName* listed in the *Partitions* list. *PartitionName* must be a case insensitive unique string, both among other partition names and the column names of the mirrored table.
 
-## Properties
+## Supported properties
 
 |Name|Type|Description|
 |--|--|--|
 |`IsEnabled`| `bool`| A Boolean value that determines whether the mirroring policy is enabled. Default is `true`. When the mirroring policy is disabled and set to `false`, the underlying mirroring data is soft-deleted and retained in the database. |
+|`TargetLatencyInMinutes`| `int`| The write operation delay in minites. By default, the write operation can take up to 3 hours or until there's 256 MB of data available. You can adjust the delay to a value between 5 minutes and 3 hours. |
 
 [!INCLUDE [mirroring-note](../includes/mirroring-note.md)]
 
@@ -60,4 +62,3 @@ In the following example, a table called *myTable* is mirrored. The data is part
 
 * To check mirroring operations, see [.show table mirroring operations command](show-table-mirroring-operations-command.md).
 * To delete mirroring operations, see [.delete table policy mirroring command](delete-table-mirroring-policy-command.md).
-

data-explorer/kusto/query/scalar-data-types/index.md

@@ -3,16 +3,16 @@ title:  Scalar data types
 description:  This article describes Scalar data types.
 ms.reviewer: alexans
 ms.topic: reference
-ms.date: 08/11/2024
+ms.date: 01/07/2025
 ---
 # Scalar data types
 
 > [!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)] [!INCLUDE [monitor](../../includes/applies-to-version/monitor.md)] [!INCLUDE [sentinel](../../includes/applies-to-version/sentinel.md)]
 
-Every data value, like the value of an expression or a function parameter, has a *data type*. A data type is either a *scalar data type*, which is one of the built-in predefined types listed below, or a *user-defined record*, which is an ordered sequence of name and scalar-data-type pairs, like the data type of a row in a table.
+Every data value, like the value of an expression or a function parameter, has a *data type* which is either a *scalar data type* or a *user-defined record*. A *scalar data type* is one of the built-in predefined types in [Supported data types](#supported-data-types). A *user-defined record* is an ordered sequence of name and scalar-data-type pairs, like the data type of a row in a table.
 
 > [!NOTE]
-> User-defined data types are not supported in Kusto.
+> While user-defined records are supported in Kusto, user-defined data types aren't.
 
 ## Supported data types
 
@@ -32,7 +32,7 @@ The following data types are supported:
 | [timespan](timespan.md) (`time`) | A time interval. |
 
 > [!TIP]
-> To check the data type of a value, use the the [gettype()](../gettype-function.md) function.
+> To check the data type of a value, use the [gettype()](../gettype-function.md) function.
 
 ## Null values
 

data-explorer/start-for-free.md

@@ -22,7 +22,7 @@ The following table describes specifications and quotas for a free cluster.
 
 | Item | Value |
 |--|--|
-| Storage (uncompressed) | ~100 GB |
+| Storage (uncompressed) | ~100 GB (20 GB compressed) |
 | Databases | Up to 10 |
 | Tables per database | Up to 100 |
 | Columns per table | Up to 200 |

data-explorer/toc.yml

@@ -507,6 +507,8 @@ items:
           - name: Monitor Azure Data Explorer
             displayName: health, performance
             href: monitor-data-explorer.md
+          - name: Monitoring data reference
+            href: monitor-data-explorer-reference.md
           - name: Use resource health to monitor cluster health
             href: monitor-with-resource-health.md
           - name: Use Azure Data Explorer Clusters Insights
@@ -656,8 +658,6 @@ items:
         href: policy-reference.md
       - name: Bicep and ARM template resource types
         href: /azure/templates/microsoft.kusto/allversions
-      - name: Monitoring data reference
-        href: monitor-data-explorer-reference.md
       - name: PowerShell Az.Kusto
         items:
           - name: Use Kusto cmdlets in Azure PowerShell