Merge pull request MicrosoftDocs#2417 from MicrosoftDocs/main63864090…

…0491560215sync_temp

For protected branch, push strategy should use PR and merge to target branch method to work around git push error

data-explorer/delete-cluster.md

@@ -2,12 +2,14 @@
 title: Delete an Azure Data Explorer cluster
 description: Learn how to delete an Azure Data Explorer cluster.
 ms.topic: how-to
-ms.date: 08/27/2023
+ms.date: 10/08/2024
 ---
 
 # Delete an Azure Data Explorer cluster
 
-This article explains how to delete an Azure Data Explorer cluster. If you delete a cluster that has been active for more than 14 days, it enters a soft delete period for 14 days. During this soft delete time period, the cluster is recoverable and can be restored, and you can't create another cluster with the same name. After 14 days, the cluster is permanently deleted and can't be restored. 
+This article explains how to delete an Azure Data Explorer cluster. If you delete a cluster that was active for more than 14 days, it enters a soft delete period for 14 days. During this soft delete time period, the cluster is recoverable and can be restored, and you can't create another cluster with the same name. After 14 days, the cluster is permanently deleted and can't be restored. 
+
+You can opt out of the soft delete period by setting a tag on your cluster. See [Opt out of soft delete](#opt-out-of-soft-delete).
 
 To delete only table records, see [Soft delete overview](/kusto/concepts/data-soft-delete?view=azure-data-explorer&preserve-view=true)
 
@@ -32,6 +34,13 @@ To delete your Azure Data Explorer cluster:
     > [!CAUTION]
     > Deleting a cluster is a permanent action and cannot be undone. All cluster content will be lost. To recover the cluster in the initial 14 days soft-delete period, please open a support ticket.
 
+## Opt out of soft delete
+
+You can opt out of the soft delete period by setting a tag on your cluster. Once you've set the tag, a deleted cluster won't enter the soft delete period and is permanently deleted immediately.
+
+Tags can be set on Azure resources through the portal, PowerShell, Azure CLI, or ARM templates. For more information on these different methods, see [Use tags to organize your Azure resources](/azure/azure-resource-manager/management/tag-resources).
+
+The key for the tag is `opt-out-of-soft-delete` and the value is `true`.
 
 ## Related content
 

data-explorer/kusto/management/partitioning-policy.md

@@ -3,7 +3,7 @@ title: Partitioning policy
 description: Learn how to use the partitioning policy to improve query performance.
 ms.reviewer: orspodek
 ms.topic: reference
-ms.date: 08/11/2024
+ms.date: 09/10/2024
 ---
 # Partitioning policy
 
@@ -23,7 +23,7 @@ The primary objective of the partitioning policy is to enhance query performance
 The following are the only scenarios in which setting a data partitioning policy is recommended. In all other scenarios, setting the policy isn't advised.
 
 * **Frequent filters on a medium or high cardinality `string` or `guid` column**:
-  * For example: multi-tenant solutions, or a metrics table where most or all queries filter on a column of type `string` or `guid`, such as the `TenantId` or the `MetricId`.
+  * For example: multitenant solutions, or a metrics table where most or all queries filter on a column of type `string` or `guid`, such as the `TenantId` or the `MetricId`.
   * Medium cardinality is at least 10,000 distinct values.
   * Set the [hash partition key](#hash-partition-key) to be the `string` or `guid` column, and set the [`PartitionAssignmentMode` property](#partition-properties) to `uniform`.
 * **Frequent aggregations or joins on a high cardinality `string` or `guid` column**:
@@ -209,7 +209,7 @@ The following properties can be defined as part of the policy. These properties
 * Data partitioning runs only on hot extents, regardless of the value of the `EffectiveDateTime` property in the policy.
   * If partitioning cold extents is required, you need to temporarily adjust the [caching policy](cache-policy.md).
 
-You can monitor the partitioning status of tables with defined policies in a database by using the [.show database extents partitioning statistics](show-database-extents-partitioning-statistics.md) command.
+You can monitor the partitioning status of tables with defined policies in a database by using the [.show database extents partitioning statistics](show-database-extents-partitioning-statistics.md) command and [partitioning metrics](/azure/data-explorer/using-metrics#partitioning-metrics).
 
 ### Partitioning capacity