Merge pull request #275882 from richagaur/richagaur/change-capacity-mode

Richagaur/change capacity mode

Author: denrea

articles/cosmos-db/nosql/how-to-change-capacity-mode.md

@@ -6,8 +6,6 @@ author: richagaur
 ms.author: richagaur
 ms.service: cosmos-db
 ms.subservice: nosql
-ms.custom:
-  - build-2024
 ms.topic: how-to
 ms.date: 05/08/2024
 #Customer Intent: As an administrator, I want to change the capacity mode, so that I can migrate from serverless to provisioned capacity.
@@ -17,7 +15,8 @@ ms.date: 05/08/2024
 
 [!INCLUDE[NoSQL](../includes/appliesto-nosql.md)]
 
-Azure Cosmos DB for NoSQL accounts in serverless capacity mode can be changed to provisioned capacity mode. Changing from serverless to provisioned capacity mode converts all containers within the account to manual provisioned throughput containers in-place. The containers' throughput is determined according to the following formula: `Throughput(RU/s) = max(5000, StorageInGB * 10)`.
+Azure Cosmos DB for NoSQL accounts in serverless capacity mode can be changed to provisioned capacity mode. Changing from serverless to provisioned capacity mode converts all containers within the account to manual provisioned throughput containers in-place. The containers' throughput is determined according to the following formula: 
+            `Throughput(RU/s) = max(5000, number of partitions * 1000)`.
 
 You can also change the throughput or provisioning mode from manual to autoscale once the migration is complete.
 
@@ -33,26 +32,33 @@ You can also change the throughput or provisioning mode from manual to autoscale
 
 ## Register for preview
 
-To enable this feature, register for the preview feature **Change capacity mode (preview)** in your subscription. For more information, see [register for an Azure Cosmos DB preview feature](../access-previews.md).
+
+To enable this feature, register for the preview feature **Change capacity mode from serverless to provisioned throughput** in your subscription. For more information, see [register for an Azure Cosmos DB preview feature](../access-previews.md).
 
 ## Change capacity mode
 
 Follow these steps to change the capacity mode using Azure portal.
 
 1. In the Azure portal, navigate to your API for NoSQL account.
 
-1. Select the **Change** option associated with the **capacity mode** field in the **Overview** section of the account page.
+1. Select the **Change capacity mode to provisioned throughput** option in the **Overview** section of the account page.
 
 1. Review the changes and select **Confirm** to start the migration.
 
 1. Monitor the status using the **state** field in the **Overview** section. The status indicates that the account is **updating** while the migration is in progress.
 
-1. Once the migration is complete, the **capacity mode** field is now set to **provisioned capacity**.
+1. Once the migration is complete, the **capacity mode** field is now set to **provisioned throughput**.
+
+## Limitations
 
-> [!IMPORTANT]
-> There are no service level agreements (SLAs) associated with the duration of the capacity mode change. You cannot execute any management operation while the migration is in progress. However, the containers can be accessed as usual by any client application.
+- This is one time migration that is; the account can't be reversed to serverless capacity mode again.
+- There's no SLA associated with the duration of migration. 
+- Any management operation can't be executed while the migration is in progress.
+- In cases where you need to restore a deleted Cosmos DB account, the account is restored to provisioned throughput if the capacity mode was changed from serverless to provisioned, irrespective of the backup timestamp. 
+- In cases where you need to restore a deleted serverless container within an existing account, which was migrated from serverless to provisioned throughput, contact Microsoft support.
 
 ## Related content
 
 - [Chose between autoscale and manual throughput](../how-to-choose-offer.md).
 - [Choose between serverless and provisioned throughput](../throughput-serverless.md).
+