Merge pull request #294186 from SnehaSudhirG/06Feb-MigrateDocEdits

Removed the date and redundant section

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: 02/05/2025
+ms.date: 02/06/2025
 ms.custom: engagement-fy24
 ---
 
@@ -232,18 +232,6 @@ If you use performance-based sizing in an Azure VM assessment, the assessment ma
 - If you don't want to use the performance data, reset the sizing criteria to as-is on-premises, as described in the previous section.
 
 
-#### Calculate storage sizing
-
-For storage sizing in an Azure VM assessment, Azure Migrate tries to map each disk that is attached to the server to an Azure disk. Sizing works as follows:
-
-1. Assessment adds the read and write IOPS of a disk to get the total IOPS required. Similarly, it adds the read and write throughput values to get the total throughput of each disk. In the case of import-based assessments, you have the option to provide the total IOPS, total throughput and total no. of disks in the imported file without specifying individual disk settings. If you do this, individual disk sizing is skipped and the supplied data is used directly to compute sizing, and select an appropriate VM SKU.
-
-1. Disks are selected as follows:
-    - If assessment can't find a disk with the required IOPS and throughput, it marks the server as unsuitable for Azure.
-    - If assessment finds a set of suitable disks, it selects the disks that support the location specified in the assessment settings.
-    - 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:
@@ -259,7 +247,7 @@ Azure Migrate maps each disk attached to a server to an Azure disk. The sizing p
    - 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. 
+   >- For all the new assessments if Premium disks are selected during assessment creation, 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.