Merge pull request #4720 from MicrosoftDocs/main

Auto Publish – main to live - 2026-04-08 11:00 UTC

Author: learn-build-service-prod[bot]

articles/documentdb/how-to-assess-plan-migration-readiness.md

@@ -38,8 +38,10 @@ Use the **Azure DocumentDB Migration extension** in VS Code to assess the [compa
 1. Add the MongoDB server you want to assess for migration to the **Document DB Connections** list.
 1. Expand the selected connection, then Right-click and choose **Data Migration...**.
 :::image type="content" source="media/how-to-assess-plan-migration-readiness/documentdb-connections.png" alt-text="Screenshot of the Right Click menu in Document DB Connections.":::
-1. From the command palette, select **Pre-Migration Assessment for Azure DocumentDB**.
- :::image type="content" source="media/how-to-assess-plan-migration-readiness/command-palette.png" alt-text="Screenshot of the command palette in Visual Studio Code.":::
+1. From the command palette, select **Migration to Azure DocumentDB**.
+ :::image type="content" source="media/how-to-assess-plan-migration-readiness/command-palette-migration-tools.png" alt-text="Screenshot of the command palette listing migration tools in Visual Studio Code.":::
+1. Then select **Pre-Migration Assessment for Azure DocumentDB**.
+ :::image type="content" source="media/how-to-assess-plan-migration-readiness/command-palette-pre-migration-assessment.png" alt-text="Screenshot of the command palette showing pre-migration assessment option in Visual Studio Code.":::
 1. The assessment wizard guides you through three steps. In the **Start Validation** step, select **Run Validation** to verify credentials, prerequisites, and connectivity before proceeding. 
 :::image type="content" source="media/how-to-assess-plan-migration-readiness/start-validation.png" alt-text="Screenshot of the Start Validation step in the assessment wizard.":::
 

articles/documentdb/how-to-migrate-vs-code-extension.md

@@ -73,9 +73,11 @@ You can invoke the Migration Extension from the DocumentDB Connections.
 
     :::image type="content" source="media/how-to-migrate-vs-code-extension/context-menu.png" alt-text="Screenshot of the context menu in Visual Studio Code."  :::
 
-1. Select **Migrate to Azure DocumentDB** from the command palette. 
+1. From the command palette, select **Migration to Azure DocumentDB**.
+    :::image type="content" source="media/how-to-migrate-vs-code-extension/command-palette-migration-tools.png" alt-text="Screenshot of the command palette listing migration tools in Visual Studio Code.":::
 
-    :::image type="content" source="media/how-to-migrate-vs-code-extension/command-palette.png" alt-text="Screenshot of the command palette in Visual Studio Code." :::
+1. Then select **Migrate to Azure DocumentDB**.
+    :::image type="content" source="media/how-to-migrate-vs-code-extension/command-palette-migrate.png" alt-text="Screenshot of the command palette showing migration option in Visual Studio Code.":::
 
 1. A migration wizard guides you through the process.
 

articles/documentdb/media/how-to-assess-plan-migration-readiness/command-palette-migration-tools.png

@@ -86,7 +86,7 @@ This quickstart demonstrates how to use the Azure CLI commands to create a clust
 1. Create a datacenter for the cluster with three virtual machines (VMs). Use the following configuration:
 
    - **VM size**: Standard E8s v5
-   - **Data disks**: 4 P30 disks attached to each of the VMs deployed
+   - **Data disks**: 4 P30 disks attached to each of the VMs deployed, When calculating storage capacity, assume a maximum sustained usage of 50%. This buffer accounts for tombstones and disk consumption by system services. Additionally, backups temporarily consume disk space before data is persisted to Blob storage.
 
    After all the information is in place, use the [az managed-cassandra datacenter create](/cli/azure/managed-cassandra/datacenter#az-managed-cassandra-datacenter-create) command:
 

…-migration-readiness/command-palette.png …and-palette-pre-migration-assessment.pngarticles/documentdb/media/how-to-assess-plan-migration-readiness/command-palette.png renamed to articles/documentdb/media/how-to-assess-plan-migration-readiness/command-palette-pre-migration-assessment.png articles/documentdb/media/how-to-assess-plan-migration-readiness/command-palette.png renamed to articles/documentdb/media/how-to-assess-plan-migration-readiness/command-palette-pre-migration-assessment.png

@@ -79,7 +79,7 @@ If you don't have an Azure subscription, create a [free account](https://azure.m
    We introduced write-through caching (public preview) by using L-series VM product tiers. This implementation aims to minimize tail latencies and enhance read performance, particularly for read-intensive workloads. These specific product tiers are equipped with locally attached disks, which ensure increased IOPS for read operations and reduced tail latency.
 
    Write-through caching is provided without a service-level agreement (SLA). We don't recommend it for production workloads. For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
-   - **No. of disks**: Choose the number of p30 disks to be attached to each Cassandra node.
+   - **No. of disks**: Choose the number of p30 disks to be attached to each Cassandra node. When calculating storage capacity, assume a maximum sustained usage of 50%. This buffer accounts for tombstones and disk consumption by system services. Additionally, backups temporarily consume disk space before data is persisted to Blob storage.
    - **No. of nodes**: Choose the number of Cassandra nodes to deploy to this datacenter.
 
       :::image type="content" source="media/create-cluster-portal/create-datacenter-page.png" border="true" alt-text="Screenshot that shows the Data center tab where you can review the values." lightbox="media/create-cluster-portal/create-datacenter-page.png":::
@@ -146,7 +146,7 @@ Scaling is an online operation and works in the same manner as described for pat
    * **Availability zone**: Select if you want to enable availability zones in this datacenter.
    * **Location**: Location where your datacenter is deployed.
    * **SKU size**: Choose from the available VM product tier sizes.
-   * **No. of disks**: Choose the number of p30 disks to be attached to each Cassandra node.
+   * **No. of disks**: Choose the number of p30 disks to be attached to each Cassandra node. When calculating storage capacity, assume a maximum sustained usage of 50%. This buffer accounts for tombstones and disk consumption by system services. Additionally, backups temporarily consume disk space before data is persisted to Blob storage.
    * **No. of nodes**: Choose the number of Cassandra nodes to deploy to this datacenter.
    * **Virtual network**: Select an existing virtual network and subnet.