Merge pull request #218542 from v-ksreedevan/16Nov-CPUOnboarding

CPU benchmarking updates

Author: prmerger-automator[bot]

articles/migrate/common-questions-discovery-assessment.md

@@ -5,9 +5,8 @@ author: rashijoshi
 ms.author: rajosh
 ms.manager: abhemraj
 ms.topic: conceptual
-ms.date: 11/15/2022
+ms.date: 11/24/2022
 ms.custom: engagement-fy23
-
 ---
 
 # Discovery, assessment, and dependency analysis - Common questions
@@ -83,11 +82,27 @@ The confidence rating is calculated for "Performance-based" assessments based on
 
 By design, in Hyper-V if maximum memory provisioned is less than what is required by the VM, Assessment will show memory utilization to be more than 100%.
 
+## I see a banner on my assessment that the assessment now also considers processor parameters. What will be the impact of recalculating the assessment?
+
+The assessment now considers processor parameters such as number of operational cores, sockets, etc. and calculating its optimal performance over a period in a simulated environment. This is done to benchmark all processor-based available processor information. Recalculate your assessments to see the updated recommendations.
+
+The processor benchmark numbers are now considered along with the resource utilization to ensure, we match the processor performance of your on-premises VMware environment and recommend the target Azure SKU sizes accordingly. This is a way to further improve the assessment recommendations to match your performance needs more closely.
+
+Due to this, the target Azure VM cost can differ from your earlier assessments of the same target. Also, the number of cores allocated in the target Azure SKU could also vary if the processor performance of target is a match for your on-premises VMware environment.
+
+## For scenarios where customers choose "as on premises", is there any impact due to processor benchmarking?
+
+No, there will be no impact as we don't consider it for as on premises scenario.
+
+## I see an increase in my monthly costs after I recalculate my assessments? Is this the most optimized cost for me?
+
+If you've selected all available options for your “VM Series” in your assessment settings, you will get the most optimized cost recommendation for your VMs. However, if you choose only some of the available options for the VM series, the recommendation might skip the most optimized option for you while assigning you an Azure VM SKU while matching your processor performance numbers.
+
 ## Why can't I see all Azure VM families in the Azure VM assessment properties?
 
 There could be two reasons:
 - You've chosen an Azure region where a particular series isn't supported. Azure VM families shown in Azure VM assessment properties are dependent on the availability of the VM series in the chosen Azure location, storage type and Reserved Instance. 
-- The VM series isn't support in the assessment and isn't in the consideration logic of the assessment. We currently don't support B-series burstable, accelerated and high performance SKU series. We are trying to keep the VM series updated, and the ones mentioned are on our roadmap. 
+- The VM series isn't support in the assessment and isn't in the consideration logic of the assessment. We currently don't support B-series burstable, accelerated and high performance SKU series. We're trying to keep the VM series updated, and the ones mentioned are on our roadmap. 
 
 ## The number of Azure VM or AVS assessments on the Discovery and assessment tool are incorrect
 
@@ -185,7 +200,7 @@ You can create a single **Azure SQL** assessment consisting of desired SQL serve
 
 ## The storage cost in my Azure SQL assessment is zero
 
-For Azure SQL Managed Instance, there is no storage cost added for the first 32 GB/instance/month storage and additional storage cost is added for storage in 32 GB increments. [Learn More](https://azure.microsoft.com/pricing/details/azure-sql/sql-managed-instance/single/).
+For Azure SQL Managed Instance, there's no storage cost added for the first 32 GB/instance/month storage and additional storage cost is added for storage in 32 GB increments. [Learn More](https://azure.microsoft.com/pricing/details/azure-sql/sql-managed-instance/single/).
 
 ## I can't see some groups when I am creating an Azure VMware Solution (AVS) assessment
 

articles/migrate/concepts-assessment-calculation.md

@@ -5,7 +5,7 @@ author: rashi-ms
 ms.author: rajosh
 ms.manager: abhemraj
 ms.topic: conceptual
-ms.date: 06/13/2022
+ms.date: 11/24/2022
 ms.custom: engagement-fy23
 ---
 
@@ -120,7 +120,7 @@ Here's what's included in an Azure VM assessment:
 --- | ---
 **Target location** | The location to which you want to migrate. The assessment currently supports these target Azure regions:<br><br> Australia Central, Australia Central 2, Australia East, Australia Southeast, Brazil South, Canada Central, Canada East, Central India, Central US, China East, China East 2,  China North, China North 2, East Asia, East US, East US 2, France Central, France South, Germany North, Germany West Central, Japan East, Japan West, Korea Central, Korea South, North Central US, North Europe, Norway East, Norway West, South Africa North, South Africa West, South Central US, Southeast Asia, South India, Switzerland North, Switzerland West, UAE Central, UAE North, UK South, UK West, West Central US, West Europe, West India, West US, West US 2, JioIndiaCentral, JioIndiaWest, US Gov Arizona, US Gov Iowa, US Gov Texas, US Gov Virginia.
 **Target storage disk (as-is sizing)** | The type of disk to use for storage in Azure. <br><br> Specify the target storage disk as Premium-managed, Standard SSD-managed, Standard HDD-managed, or Ultra disk.
-**Target storage disk (performance-based sizing)** | Specifies the type of target storage disk as automatic, Premium-managed, Standard HDD-managed, Standard SSD-managed, or Ultra disk.<br><br> **Automatic**: The disk recommendation is based on the performance data of the disks, meaning the IOPS and throughput.<br><br>**Premium or Standard or Ultra disk**:  The assessment recommends a disk SKU within the storage type selected.<br><br> If you want a single-instance VM service-level agreement (SLA) of 99.9%, consider using Premium-managed disks. This use ensures that all disks in the assessment are recommended as Premium-managed disks.<br><br> If you are looking to run data-intensive workloads that need high throughput, high IOPS, and consistent low latency disk storage, consider using Ultra disks.<br><br> Azure Migrate supports only managed disks for migration assessment.
+**Target storage disk (performance-based sizing)** | Specifies the type of target storage disk as automatic, Premium-managed, Standard HDD-managed, Standard SSD-managed, or Ultra disk.<br><br> **Automatic**: The disk recommendation is based on the performance data of the disks, meaning the IOPS and throughput.<br><br>**Premium or Standard or Ultra disk**:  The assessment recommends a disk SKU within the storage type selected.<br><br> If you want a single-instance VM service-level agreement (SLA) of 99.9%, consider using Premium-managed disks. This use ensures that all disks in the assessment are recommended as Premium-managed disks.<br><br> If you're looking to run data-intensive workloads that need high throughput, high IOPS, and consistent low latency disk storage, consider using Ultra disks.<br><br> Azure Migrate supports only managed disks for migration assessment.
 **Azure Reserved VM Instances** | Specifies [reserved instances](https://azure.microsoft.com/pricing/reserved-vm-instances/) so that cost estimations in the assessment take them into account.<br><br> When you select 'Reserved instances', the 'Discount (%)' and 'VM uptime' properties are not applicable.<br><br> Azure Migrate currently supports Azure Reserved VM Instances only for pay-as-you-go offers.
 **Sizing criteria** | Used to rightsize the Azure VM.<br><br> Use as-is sizing or performance-based sizing.
 **Performance history** | Used with performance-based sizing. Performance history specifies the duration used when performance data is evaluated.
@@ -203,12 +203,12 @@ After the server is marked as ready for Azure, the assessment makes sizing recom
 
 If you use performance-based sizing in an Azure VM assessment, the assessment makes sizing recommendations as follows:
 
-- The assessment considers the performance history of the server to identify the VM size and disk type in Azure.
+- The assessment considers the performance (resource utilization) history of the server along with the [processor benchmark](common-questions-discovery-assessment.md#i-see-a-banner-on-my-assessment-that-the-assessment-now-also-considers-processor-parameters-what-will-be-the-impact-of-recalculating-the-assessment) to identify the VM size and disk type in Azure.
 
 > [!NOTE] 
 > If you import servers by using a CSV file, the performance values you specify (CPU utilization, Memory utilization, Disk IOPS and throughput) are used if you choose performance-based sizing. You will not be able to provide performance history and percentile information.
 
-- This method is especially helpful if you've overallocated the on-premises server, utilization is low, and you want to rightsize the Azure VM to save costs.
+- This method is especially helpful if you've overallocated the on-premises server, utilization is low, and you want to right-size the Azure VM to save costs.
 - 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.
 
 
@@ -252,7 +252,7 @@ For an Azure VM assessment, assessment tries to find an Azure VM that supports t
 
 After it calculates storage and network requirements, the assessment considers CPU and RAM requirements to find a suitable VM size in Azure.
 
-- Azure Migrate looks at the effective utilized cores and RAM to find a suitable Azure VM size.
+- Azure Migrate looks at the effective utilized cores (including [processor benchmark](common-questions-discovery-assessment.md#i-see-a-banner-on-my-assessment-that-the-assessment-now-also-considers-processor-parameters-what-will-be-the-impact-of-recalculating-the-assessment)) and RAM to find a suitable Azure VM size.
 - If no suitable size is found, the server is marked as unsuitable for Azure.
 - If a suitable size is found, Azure Migrate applies the storage and networking calculations. It then applies location and pricing-tier settings for the final VM size recommendation.
 - If there are multiple eligible Azure VM sizes, the one with the lowest cost is recommended.
@@ -289,12 +289,12 @@ This table shows the assessment confidence ratings, which depend on the percenta
 Here are a few reasons why an assessment could get a low confidence rating:
 
 - You didn't profile your environment for the duration for which you're creating the assessment. For example, if you create the assessment with performance duration set to one day, you must wait at least a day after you start discovery for all the data points to get collected.
-- Assessment is not able to collect the performance data for some or all the servers in the assessment period. For a high confidence rating, please ensure that: 
+- Assessment is not able to collect the performance data for some or all the servers in the assessment period. For a high confidence rating, ensure that: 
     - Servers are powered on for the duration of the assessment
     - Outbound connections on ports 443 are allowed
     - For Hyper-V servers, dynamic memory is enabled 
 
-    Please 'Recalculate' the assessment to reflect the latest changes in confidence rating.
+    **Recalculate** the assessment to reflect the latest changes in confidence rating.
 
 - Some servers were created during the time for which the assessment was calculated. For example, assume you created an assessment for the performance history of the last month, but some servers were created only a week ago. In this case, the performance data for the new servers will not be available for the entire duration and the confidence rating would be low.
 

articles/migrate/discovered-metadata.md

@@ -5,7 +5,7 @@ author: Vikram1988
 ms.author: vibansa
 ms.manager: abhemraj
 ms.topic: conceptual
-ms.date: 08/05/2022
+ms.date: 11/24/2022
 ms.custom: engagement-fy23
 ---
 
@@ -39,7 +39,9 @@ Number of disks | vm.Config.Hardware.Device.ToList().FindAll(x => is VirtualDisk
 Disk size list | vm.Config.Hardware.Device.ToList().FindAll(x => is VirtualDisk)
 Network adapters list | vm.Config.Hardware.Device.ToList().FindAll(x => is VirtualEthernet).count
 CPU utilization | cpu.usage.average
-Memory utilization |mem.usage.average
+Memory utilization | mem.usage.average
+Processor model/name | vm.Config.Hardware.CpuModel 
+Number of Sockets in a Processor | vm.Config.Hardware.NumCpuPkgs
 **Per disk details** |
 Disk key value | disk.Key
 Dikunit number | disk.UnitNumber