Merge pull request #262004 from richagaur/richagaur/burst-capacity-update

cli/ps version update

Author: v-ccolin

articles/cosmos-db/burst-capacity-faq.yml

@@ -51,19 +51,14 @@ sections:
       - question: |
           How can I enable burst capacity on an account programatically?
         answer: |
-          You can use the [Azure Cosmos DB Resource Provider REST API version `2023-03-15-preview`](/rest/api/cosmos-db-resource-provider/2023-03-15-preview/database-accounts/create-or-update) or a [Resource Manager template with API version `2023-03-01-preview`](/azure/templates/microsoft.documentdb/2023-03-01-preview/databaseaccounts) to set the property `enableBurstCapacity` to true.
+          You can use the [Azure Cosmos DB Resource Provider REST API version `2023-09-15`](/rest/api/cosmos-db-resource-provider/2023-09-15/database-accounts/create-or-update) or a [Resource Manager template with API version `2023-03-01-preview`](/azure/templates/microsoft.documentdb/2023-03-01-preview/databaseaccounts) to set the property `enableBurstCapacity` to true.
           You can also use the Azure CLI or PowerShell.
 
           #### [PowerShell](#tab/azure-powershell)
 
           ```azurepowershell
-          // Add the preview extension 2.0.5-preview or higher
-          $installParameters = @{
-              Name = "Az.CosmosDB"
-              AllowPrerelease = $true
-              Force = $true
-          }
-          Install-Module @installParameters
+          // Add Azure Cosmos DB extension 1.13.0 or higher
+          Install-Module -Name Az.CosmosDB -RequiredVersion 1.13.0
 
           // Enable burst capacity on an account
           $parameters = @{
@@ -77,9 +72,6 @@ sections:
           #### [Azure CLI](#tab/azure-cli)
 
           ```azurecli
-          // Add the preview extension version 0.24.0 or higher
-          az extension add --name cosmosdb-preview --version 0.24.0
-
           // Enable burst capacity on an account
           az cosmosdb update  \
           --resource-group '<resource-group-name>' \

articles/cosmos-db/burst-capacity.md

@@ -22,7 +22,7 @@ Burst capacity applies only to Azure Cosmos DB accounts using provisioned throug
 ## How burst capacity works
 
 > [!NOTE]
-> The current implementation of burst capacity is subject to change in the future. Usage of burst capacity is subject to system resource availability and is not guaranteed. Azure Cosmos DB may also use burst capacity for background maintenance tasks. If your workload requires consistent throughput beyond what you have provisioned, it's recommended to provision your RU/s accordingly without relying on burst capacity. Before enabling burst capacity, it is also recommended to evaluate if your partition layout can be [merged](merge.md) to permanently give more RU/s per physical partition without relying on burst capacity.
+> The current implementation of burst capacity is subject to change in the future. Usage of burst capacity is subject to system resource availability and is **not guaranteed**. Azure Cosmos DB may also use burst capacity for background maintenance tasks. If your workload requires consistent throughput beyond what you have provisioned, it's recommended to provision your RU/s accordingly without relying on burst capacity. Before enabling burst capacity, it is also recommended to evaluate if your partition layout can be [merged](merge.md) to permanently give more RU/s per physical partition without relying on burst capacity.
 
 Let's take an example of a physical partition that has 100 RU/s of provisioned throughput and is idle for 5 minutes. With burst capacity, it can accumulate a maximum of 100 RU/s * 300 seconds = 30,000 RU of burst capacity. The capacity can be consumed at a maximum rate of 3000 RU/s, so if there's a sudden spike in request volume, the partition can burst up to 3000 RU/s for up 30,000 RU / 3000 RU/s = 10 seconds. Without burst capacity, any requests that are consumed beyond the provisioned 100 RU/s would have been rate limited (429).