Merge pull request #261942 from richagaur/richagaur/pk-delete-enrol-update

added self-serve capability to enable feature

Author: prmerger-automator[bot]

articles/cosmos-db/nosql/how-to-delete-by-partition-key.md

@@ -17,7 +17,7 @@ This article explains how to use the Azure Cosmos DB SDKs to delete all items by
 
 > [!IMPORTANT]
 > Delete items by partition key value is in public preview.
-> This feature is provided without a service level agreement, and it's not recommended for production workloads.
+> This feature is provided without a service level agreement.
 > For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
 
 ## Feature overview
@@ -30,9 +30,34 @@ The delete by partition key operation is constrained to consume at most 10% of t
 
 ## Getting started
 
-To use the feature, your Azure Cosmos DB account must be enrolled in the preview. To enroll, submit a request for the **DeleteAllItemsByPartitionKey** feature via the [**Preview Features** page](../../azure-resource-manager/management/preview-features.md) in your Azure Subscription overview page. 
-
-:::image type="content" source="media/how-to-delete-by-partition-key/preview-enrollment-delete-by-partition-key.png" alt-text="Screenshot that shows the enroll in Delete All Items By Partition Key in Preview Features blade.":::
+Update your Azure Cosmos DB account to enable "Delete by partition key" feature using Azure CLI.
+
+- Step 1: Set shell variables 
+    ```azurecli-interactive
+        $resourceGroupName = <azure_resource_group>
+        $accountName = <azure_cosmos_db_account_name>
+        $DeleteByPk = "DeleteAllItemsByPartitionKey"
+    ```
+- Step 2: List down existing capabilities of your account.
+    ```azurecli-interactive
+       $cosmosdb = az cosmosdb show \
+        --resource-group $resourceGroupName \
+        --name $accountName
+       $capabilities = ($cosmosdb | ConvertFrom-Json).capabilities 
+    ```
+- Step 3: Add "Delete items by partition key" capability in the list of capabilities if it doesn't exist already. 
+    >!Note 
+    The list of capabilities must always specify all capabilities that you want to enable, inclusively. This includes capabilities that are already enabled for the account that you want to keep. 
+
+    ```azurecli-interactive
+       $capabilities += $DeleteByPk
+    ```
+
+- Step 4: Update Cosmos DB account to enable "Delete items by partition key" feature
+     ```azurecli-interactive
+        az cosmosdb update --capabilities $capabilities \
+         -n $accountName -g $resourceGroupName
+    ```
 
 #### [.NET](#tab/dotnet-example)
 
@@ -87,22 +112,22 @@ Yes, once the delete by partition key operation starts, the documents to be dele
 See [Known issues](#known-issues) for exceptions. 
 
 #### What happens if I issue a delete by partition key operation, and then immediately write a new document with the same partition key?
-When the delete by partition key operation is issued, only the documents that exist in the container at that point in time with the partition key value will be deleted. Any new documents that come in won't be in scope for the deletion. 
+When the delete by partition key operation is issued, only the documents that exist in the container then with the partition key value will be deleted. Any new documents that come in won't be in scope for the deletion. 
 
 ### How is the delete by partition key operation prioritized among other operations against the container?
-By default, the delete by partition key value operation can consume up to a reserved fraction - 0.1, or 10% - of the overall RU/s on the resource. Any Request Units (RUs) in this bucket that are unused will be available for other non-background operations, such as reads, writes, and queries. 
+By default, the delete by partition key value operation can consume up to a reserved fraction - 0.1, or 10% - of the overall RU/s on the resource. Any Request Units (RUs) in this bucket that are unused will be available for other nonbackground operations, such as reads, writes, and queries. 
 
-For example, suppose you've provisioned 1000 RU/s on a container. There's an ongoing delete by partition key operation that consumes 100 RUs each second for 5 seconds. During each of these 5 seconds, there are 900 RUs available for non-background database operations. Once the delete operation is complete, all 1000 RU/s are now available again. 
+For example, suppose you've provisioned 1000 RU/s on a container. There's an ongoing delete by partition key operation that consumes 100 RUs each second for 5 seconds. During each of these 5 seconds, there are 900 RUs available for nonbackground database operations. Once the delete operation is complete, all 1000 RU/s are now available again. 
 
 ### Known issues
-For certain scenarios, the effects of a delete by partition key operation isn't guaranteed to be immediately reflected. The effect may be partially seen as the operation progresses. 
+In some scenarios, a delete by partition key operation may not immediately guarantee its effects, and partial visibility may occur during the operation. 
 
 - Aggregate queries that use the index - for example, COUNT queries - that are issued during an ongoing delete by partition key operation may contain the results of the documents to be deleted. This may occur until the delete operation is fully complete.
 - Queries issued against the [analytical store](../analytical-store-introduction.md) during an ongoing delete by partition key operation may contain the results of the documents to be deleted. This may occur until the delete operation is fully complete.
 - [Continuous backup (point in time restore)](../continuous-backup-restore-introduction.md) - a restore that is triggered during an ongoing delete by partition key operation may contain the results of the documents to be deleted in the restored collection. It isn't recommended to use this preview feature if you have a scenario that requires continuous backup.
 
 ### Limitations
-- [Hierarchical partition keys](../hierarchical-partition-keys.md) deletion is not supported. This feature permits the deletion of items solely based on the last level of partition keys. For example, consider a scenario where a partition key consists of three hierarchical levels: country, state, and city. In this context, the delete by partition keys functionality can be employed effectively by specifying the complete partition key, encompassing all levels, namely country/state/city. Attempting to delete using intermediate partition keys, such as country/state or solely country, will result in an error.
+- [Hierarchical partition keys](../hierarchical-partition-keys.md) deletion isn't supported. This feature permits the deletion of items solely based on the last level of partition keys. For example, consider a scenario where a partition key consists of three hierarchical levels: country, state, and city. In this context, the delete by partition keys functionality can be employed effectively by specifying the complete partition key, encompassing all levels, namely country/state/city. Attempting to delete using intermediate partition keys, such as country/state or solely country, will result in an error.
 
 ## How to give feedback or report an issue/bug
 * Email [email protected] with questions or feedback.