add autoscale migrate script to articles

Author: markjbrown

articles/cosmos-db/autoscale-faq.yml

@@ -6,7 +6,7 @@ metadata:
   ms.author: dech
   ms.service: cosmos-db
   ms.topic: faq
-  ms.date: 04/01/2022
+  ms.date: 07/26/2024
 title: Frequently asked questions about autoscale provisioned throughput in Azure Cosmos DB
 summary: |
   [!INCLUDE[NoSQL, MongoDB, Cassandra, Gremlin, Table](includes/appliesto-nosql-mongodb-cassandra-gremlin-table.md)]
@@ -110,6 +110,8 @@ sections:
           The initial manual provisioned throughput is equal to the current autoscale maximum RU/s. 
           
           Example: You have an autoscale database or container that has a maximum RU/s of 20,000 RU/s (scales between 2,000 RU/s and 20,000 RU/s). When you update to use manual provisioned throughput, the initial throughput is 20,000 RU/s. 
+
+          If you need to migrate a large number of throughput resources, consider using this [Azure CLI script - Convert to Autoscale](./scripts/cli/common/convert-to-autoscale.md)
           
       - question: |
           Can I use the Azure CLI, PowerShell, or Azure Resource Manager to manage databases or containers that use autoscale?

articles/cosmos-db/how-to-choose-offer.md

@@ -4,7 +4,7 @@ description: Learn how to choose between standard (manual) provisioned throughpu
 author: deborahc
 ms.service: cosmos-db
 ms.topic: conceptual
-ms.date: 04/01/2022
+ms.date: 07/26/2024
 ms.author: dech
 ---
 
@@ -131,6 +131,10 @@ When using autoscale, use Azure Monitor to see the provisioned autoscale max RU/
 > [!NOTE]
 > When you use standard (manual) provisioned throughput, the **Provisioned Throughput** metric refers to what you as a user have set. When you use autoscale throughput, this metric refers to the RU/s the system is currently scaled to.
 
+## Migrate standard provisioned throughput to autoscale
+
+Users that want to migrate a large number of resources from standard provisioned throughput to autoscale can use an Azure CLI script that will migrate every throughput resource in an Azure subscription to autoscale. For more details see, [Convert to Autoscale](./scripts/cli/common/convert-to-autoscale.md)
+
 ## Next steps
 * Use [RU calculator](https://cosmos.azure.com/capacitycalculator/) to estimate throughput for new workloads.
 * Use [Azure Monitor](monitor.md#view-operation-level-metrics-for-azure-cosmos-db) to monitor your existing workloads.

articles/cosmos-db/provision-throughput-autoscale.md

@@ -5,7 +5,7 @@ author: kirillg
 ms.author: kirillg
 ms.service: cosmos-db
 ms.topic: conceptual
-ms.date: 04/01/2022
+ms.date: 07/26/2024
 ---
 
 # Create Azure Cosmos DB containers and databases with autoscale throughput
@@ -74,6 +74,10 @@ For more detail, see this [documentation](how-to-choose-offer.md) on how to choo
 | **Pricing** | You pay for the manually provisioned RU/s per hour, using the [standard (manual) RU/s per hour rate](https://azure.microsoft.com/pricing/details/cosmos-db/). | You pay per hour for the highest RU/s the system scaled up to within the hour. <br/><br/> For single write region accounts, you pay for the RU/s used on an hourly basis, using the [autoscale RU/s per hour rate](https://azure.microsoft.com/pricing/details/cosmos-db/). <br/><br/>For accounts with multiple write regions, there's no extra charge for autoscale. You pay for the throughput used on hourly basis using the same [multi-region write RU/s per hour rate](https://azure.microsoft.com/pricing/details/cosmos-db/). |
 | **Best suited for workload types** |  Predictable and stable workloads|   Unpredictable and variable workloads  |
 
+## Migrate standard provisioned throughput to autoscale
+
+Users that want to migrate a large number of resources from standard provisioned throughput to autoscale can use an Azure CLI script that will migrate every throughput resource in an Azure subscription to autoscale. For more details see, [Convert to Autoscale](./scripts/cli/common/convert-to-autoscale.md)
+
 ## Next steps
 
 * Review the [autoscale FAQ](autoscale-faq.yml).