Merge pull request #294110 from SnehaSudhirG/05Feb-PV2DocUpdates

Updated about PV2 SSD

Author: prmerger-automator[bot]

articles/migrate/concepts-assessment-calculation.md

@@ -6,7 +6,7 @@ ms.author: rajosh
 ms.manager: abhemraj
 ms.service: azure-migrate
 ms.topic: conceptual
-ms.date: 09/28/2024
+ms.date: 02/05/2025
 ms.custom: engagement-fy24
 ---
 
@@ -244,6 +244,26 @@ For storage sizing in an Azure VM assessment, Azure Migrate tries to map each di
     - If there are multiple eligible disks, assessment selects the disk with the lowest cost.
     - If performance data for any disk is unavailable, the configuration disk size is used to find a Standard SSD disk in Azure.
 
+#### Storage sizing in Azure VM Assessment
+
+Azure Migrate maps each disk attached to a server to an Azure disk. The sizing process is as follows:
+
+1. **IOPS and Throughput Calculation**
+    - The assessment calculates total IOPS and throughput by adding the read and write IOPS and throughput values of each disk.
+1. **Import-based assessments**
+    - You can provide the total IOPS, total throughput, and total number of disks in the imported file without specifying individual disk settings.
+    - If this option is used, individual disk sizing is skipped and the supplied data is used directly to compute sizing and select an appropriate VM SKU.
+1. **Disk selection criteria and recommendations**
+   - If there is no disk that meets the required IOPS and throughput, the server is marked as unsuitable for Azure.
+   - If suitable disks are found, the assessment selects disks that support the specified location in the assessment settings.
+   - Among multiple eligible disks, the assessment selects the disk with the lowest cost.
+   - If the performance data for any disk is unavailable, the configured disk size is used to find a disk based on your preference.
+   > [!NOTE]
+   >- For all the new assessments that are created after **February 3rd, 2025**, and if Premium disks are selected while creating assessments, we recommend using Premium managed disks for your OS disks and Premium V2 SSD (preview) for your data disks. 
+   >- If you don't see Premium V2 SSD (preview) recommendations for data disks, recalculate your assessment and check the assessment settings for Storage type. 
+   >- Currently, the Premium V2 SSD (preview) migration is applicable only for VMware environments even though, the assessments are previewed for all environments.
+
+
 ##### Ultra disk sizing
 
 For Ultra disks, there is a range of IOPS and throughput that is allowed for a particular disk size, and thus the logic used in sizing is different from Standard and Premium disks:

articles/migrate/vmware/migrate-support-matrix-vmware-migration.md

@@ -6,7 +6,7 @@ ms.author: piyushdhore
 ms.manager: vijain
 ms.topic: conceptual
 ms.service: azure-migrate
-ms.date: 01/27/2025
+ms.date: 02/05/2025
 ms.custom: vmware-scenario-422, engagement-fy25
 ---
 
@@ -85,7 +85,7 @@ The table summarizes agentless migration requirements for VMware vSphere VMs.
 **Teamed NICs** | Not supported.
 **IPv6** | Not supported.
 **NVMe disks** | Not supported.
-**Target disk** | VMs can be migrated only to managed disks (standard HDD, standard SSD, premium SSD) in Azure.
+**Target disk** | VMs can be migrated only to managed disks (standard HDD, standard SSD, Premium V2 SSD (preview) for data disks) in Azure.
 **Simultaneous replication** | Up to 300 simultaneously replicating VMs per vCenter Server with one appliance. Up to 500 simultaneously replicating VMs per vCenter Server when an additional [scale-out appliance](../how-to-scale-out-for-migration.md) is deployed.
 **Automatic installation of Azure VM agent (Windows and Linux Agent)** | Windows: <br/>Supported for Windows Server 2008 R2 onwards. <br/><br/>Linux: <br/>- Red Hat Enterprise Linux 9.x, 8.x, 7.9, 7.8, 7.7, 7.6, 7.5, 7.4, 7.0, 6.x<br/>- CentOS Stream<br/>- SUSE Linux Enterprise Server 15 SP6, 15 SP5, 15 SP4, 15 SP3, 15 SP2, 15 SP1, 15 SP0, 12, 11 SP4, 11 SP3<br/>- Ubuntu 22.04, 21.04, 20.04, 19.04, 19.10, 18.04LTS, 16.04LTS, 14.04LTS<br/>- Debian 11, 10, 9, 8, 7<br/>- Oracle Linux 9, 8, 7.7-CI, 7.7, 6<br/>- Kali Linux (2016, 2017, 2018, 2019, 2020, 2021, 2022)<br/>
 

articles/migrate/vmware/tutorial-migrate-vmware.md

@@ -6,7 +6,7 @@ ms.author: piyushdhore
 ms.manager: vijain
 ms.topic: tutorial
 ms.service: azure-migrate
-ms.date: 11/16/2024
+ms.date: 02/05/2025
 ms.custom: vmware-scenario-422, mvc, engagement-fy24
 ---
 
@@ -129,12 +129,13 @@ Enable replication as follows:
     > [!NOTE]
     > If you want to select a different availability option for a sets of virtual machines, go to step 1 and repeat the steps by selecting different availability options after starting replication for one set of virtual machines.
 
-
-
-12. In **Disks**, specify whether the VM disks should be replicated to Azure, and select the disk type (standard SSD/HDD or premium-managed disks) in Azure. Then select **Next**.
+12. In **Disks**, indicate whether the VM disks should be replicated to Azure, and specify the disk type (standard SSD/HDD or Premium-managed disks) in Azure. Then select **Next**.
 
     :::image type="content" source="../media/tutorial-migrate-vmware/disks-inline.png" alt-text="Screenshot shows the Disks tab of the Replicate dialog box." lightbox="../media/tutorial-migrate-vmware/disks-expanded.png":::
 
+    > [!NOTE]
+    > To optimize costs and enhance performance, you can now migrate to Premium managed disks for OS disks and Premium V2 SSD (preview) for data disks exclusively on VMware environment.
+
 13. In **Tags**, choose to add tags to your Virtual machines, Disks, and NICs.
 
     :::image type="content" source="../media/tutorial-migrate-vmware/tags-inline.png" alt-text="Screenshot shows the tags tab of the Replicate dialog box." lightbox="../media/tutorial-migrate-vmware/tags-expanded.png":::