Merge pull request #298123 from habibaum/11Apr-updates

Feedback updates

Author: v-ccolin

articles/migrate/assessment-properties.md

@@ -17,10 +17,10 @@ This article explains the assessment properties on the **General** tab that you
 |-------------------|---------|--------  |                                                     
 | **Target settings**   | **Target location**         | The Azure region to which you want to migrate. Azure target configuration and cost recommendations are based on the location that you specify. |
 | **Target settings**   | **Default Environment**      | The environment for the target deployments to apply pricing applicable to Production or Dev/Test. |
-| **Right Sizing**      | **Sizing criteria**          | This attribute is used for right-sizing the target recommendations. <br> Use as-is on-premises sizing if you don't want to right-size the targets and identify the targets according to your configuration for on-premises workloads. Use **performance-based** sizing to calculate compute recommendation based on CPU and memory utilization data. Use the storage recommendation based on the input/output operations per second (IOPS) and throughput of the on-premises disks.  |
-| **Right Sizing**              | **Performance history**      | Used with performance-based sizing. Performance history specifies the duration used when performance data is evaluated. |
-|  **Right Sizing**               | **Percentile utilization**   | Used with performance-based sizing. Percentile utilization specifies the percentile value of the performance sample used for rightsizing. Learn more about [sampling mechanism](target-right-sizing.md). |
-|  **Right Sizing**                 | **Comfort factor**           | This is the buffer applied during assessment. It's a multiplying factor used with performance metrics of CPU, RAM, disk, and network data for VMs. It accounts for issues like seasonal usage, short performance history, and likely increases in future usage. The comfort factor is applied irrespective of type of assessment (As-is on premises or performance based). For **performance-based** assessment, it's multiplied with utilization value of the resources, whereas for **As-is on premises** assessment it's multiplied by allocated resources. <br> The default values change. <br>  For example, a 10-core VM with 20% utilization normally results in a two-core VM. With a comfort factor of 2.0, the result is a four-core VM instead. |
+| **Right-Sizing**      | **Sizing criteria**          | This attribute is used for right-sizing the target recommendations. <br> Use as-is on-premises sizing if you don't want to right-size the targets and identify the targets according to your configuration for on-premises workloads. Use **performance-based** sizing to calculate compute recommendation based on CPU and memory utilization data. Use the storage recommendation based on the input/output operations per second (IOPS) and throughput of the on-premises disks.  |
+| **Right-Sizing**              | **Performance history**      | Used with performance-based sizing. Performance history specifies the duration used when performance data is evaluated. |
+|  **Right-Sizing**               | **Percentile utilization**   | Used with performance-based sizing. Percentile utilization specifies the percentile value of the performance sample used for rightsizing. Learn more about [sampling mechanism](target-right-sizing.md). |
+|  **Right-Sizing**                 | **Comfort factor**           | This is the buffer applied during assessment. It's a multiplying factor used with performance metrics of CPU, RAM, disk, and network data for VMs. It accounts for issues like seasonal usage, short performance history, and likely increases in future usage. The comfort factor is applied irrespective of type of assessment (As-is on premises or performance based). For **performance-based** assessment, it's multiplied with utilization value of the resources, whereas for **As-is on premises** assessment it's multiplied by allocated resources. <br> The default values change. <br>  For example, a 10-core VM with 20% utilization normally results in a two-core VM. With a comfort factor of 2.0, the result is a four-core VM instead. |
 | **Pricing settings**  | **Default savings option**  | Specify the savings option that you want the assessment to consider to help optimize your Azure compute cost. </br> [Azure reservations](/azure/cost-management-billing/reservations/save-compute-costs-reservations?view=migrate&preserve-view=true) (One year or three years reserved) are a good option for the most consistently running resources. </br> [Azure Savings Plan](/azure/cost-management-billing/savings-plan/savings-plan-compute-overview?view=migrate&preserve-view=true) (One year or three years savings plan) provide additional flexibility and automated cost optimization. </br> When you select **None**, the Azure compute cost is based on the Pay-as-you-go rate considering 730 hours as VM uptime, unless specified otherwise in VM uptime attribute.|
 | |**Offer/Licensing program**| The [Azure offer](https://azure.microsoft.com/support/legal/offer-details/) in which you're enrolled. The assessment estimates the cost for that offer. Select one of the pay-as-you-go, Enterprise Agreement support, or pay-as-you-go Dev/Test. </br> You need to select pay-as-you-go in offer/licensing program to be able to use Reserved Instances or Azure Savings Plan. When you select any savings option other than **None**, the *Discount (%)* and *VM uptime* properties aren't applicable. The monthly cost estimates are calculated by multiplying 744 hours in the VM uptime field with the hourly price of the recommended SKU.|
 | |**Currency** | The billing currency for your account.| 

articles/migrate/assessment-report.md

@@ -37,7 +37,7 @@ After the server is marked as ready for Azure, the assessment makes sizing recom
 **Performance-based** | Assessments that make recommendations based on collected performance data. |  The compute recommendation is based on CPU and memory utilization data.<br/><br/> The storage recommendation is based on the input/output operations per second (IOPS) and throughput of the on-premises disks. Disk types are Azure Standard HDD, Azure Standard SSD, Azure Premium disks, and Azure Ultra disks. 
 **As-is on-premises** | Assessments that don't use performance data to make recommendations. |  The compute recommendation is based on the on-premises server size.<br/><br/> The recommended storage is based on the selected storage type for the assessment. 
 
-In performance-based assessment the assessment identifies the appropriate data point to use for right sizing. Identification is based on the percentile values for performance history and percentile utilization taken as input as assessment setting.   
+In performance-based assessment the assessment identifies the appropriate data point to use for right-sizing. Identification is based on the percentile values for performance history and percentile utilization taken as input as assessment setting.   
 
 For example, if the performance history selected is one week and the percentile utilization is the 95th percentile, the assessment sorts the performance data sample points for the last week. It sorts them in ascending order and picks the 95th percentile value for rightsizing. 
 
@@ -52,7 +52,7 @@ This value is multiplied by the comfort factor(taken as an input in assessment s
 
 ### Monthly costs 
 
-After right sizing target candidates are selected, and if more than one suitable candidate is available the recommended target is selected based on selected migration strategy. By default **Minimizing the cost** is the selected strategy. In the case of Azure VM and AVS assessment that is the only strategy. Once the targets are finalized a monthly cost is calculated by aggregating the cost of all resources, licenses and ancillary services like security. Based on the selected input from assessment settings the prices and offer details are fetched to arrive at the final cost. Learn more [about how pricing](cost-estimation.md) works in Azure Migrate assessments. 
+After right-sizing target candidates are selected, and if more than one suitable candidate is available the recommended target is selected based on selected migration strategy. By default **Minimizing the cost** is the selected strategy. In the case of Azure VM and AVS assessment that is the only strategy. Once the targets are finalized a monthly cost is calculated by aggregating the cost of all resources, licenses and ancillary services like security. Based on the selected input from assessment settings the prices and offer details are fetched to arrive at the final cost. Learn more [about how pricing](cost-estimation.md) works in Azure Migrate assessments. 
 
 ### Confidence ratings (performance-based) 
 

articles/migrate/assessments-overview-migrate-to-azure-db-mysql.md

@@ -84,7 +84,7 @@ The appliance collects the following performance data for compute settings:
 - The appliance aggregates the sample data points collected every 30 seconds over 10 minutes. To create the data point, the appliance selects the peak values from all samples. It sends the max and means for each counter to Azure.
 - Azure Migrate stores all the 10-minute data points for the last month.
 - When you create an assessment, Azure Migrate identifies the appropriate data point to use for right sizing. Identification is based on the percentile values for performance history and percentile utilization.
-    - For example, if the performance history spans a week and the utilization is at 95th percentile, the assessment sorts the 10-minute sample points for the last week. It sorts them in ascending order and picks the 95th percentile value for right sizing.
+    - For example, if the performance history spans a week and the utilization is at 95th percentile, the assessment sorts the 10-minute sample points for the last week. It sorts them in ascending order and picks the 95th percentile value for right-sizing.
     - The 95th percentile value ensures you ignore any outliers, which might be included if you picked the 99th percentile.
     - If you want to pick the peak usage for the period and don't want to miss any outliers, select the 99th percentile for percentile utilization.
 - This value is multiplied by the comfort factor to get the effective performance utilization data for these metrics that the appliance collects:
@@ -104,7 +104,7 @@ Readiness to migrate a MySQL instance to Azure Database for MySQL is determined
 
 An instance is then marked as:
 - **Ready**: If no major compatibility issues were found between source and target MySQL instances.
-- **Ready with conditions**: If there are non-critical compatibility issues such as degraded or unsupported features, that don't block the migration to Azure Database for MySQL. Azure Migrate displays the migration warnings with impact details and recommended remediation guidelines.
+- **Ready with conditions**: If there are non-critical compatibility issues such as degraded or unsupported features that don't block the migration to Azure Database for MySQL. Azure Migrate displays the migration warnings with impact details and recommended remediation guidelines.
 - **Not ready**: If there are any compatibility issues that may block the migration to Azure Database for MySQL. Azure Migrate displays the migration issues with impact details and recommended remediation guidance.
 - **Unknown**:  If the discovery is still in progress or there are any discovery issues in the source instance.
 

articles/migrate/concepts-assessment-overview.md

@@ -66,7 +66,7 @@ If you're using the appliance for discovery, it collects performance data using
 1. The assessment stores all the 10-minute data points for the last month. 
 
 1. The created assessment identifies the appropriate data point to use for rightsizing. Identification is based on the percentile value for *performance history* and *percentile utilization*. 
-    - For example,  If you selected performance history as one week and percentile utilization as 95th percentile while creating the assessments, all the data points are sorted in ascending order and the 95th percentile value is picked for right sizing. 
+    - For example,  if you selected performance history as one week and percentile utilization as 95th percentile while creating the assessments, all the data points are sorted in ascending order and the 95th percentile value is picked for right-sizing. 
     - The 95th percentile value makes sure you ignore any outliers, which might be included if you picked the 99th percentile.  
     - If you want to consider all the outliers while calculating the assessments, select 99th percentile as percentile utilization. 
 

articles/migrate/concepts-migration-planning.md

@@ -57,7 +57,7 @@ After server discovery, you can [analyze dependencies](concepts-dependency-visua
 
 ### Optimization and sizing
 
-Azure provides flexibility to resize your cloud capacity over time, and migration provides an opportunity for you to optimize the CPU and memory resources allocated to your servers. Creating an assessment on servers you've identity helps you to understand your workload performance history. This is crucial for right sizing Azure VM SKUs, and disk recommendations in Azure.
+Azure provides flexibility to resize your cloud capacity over time, and migration provides an opportunity for you to optimize the CPU and memory resources allocated to your servers. Creating an assessment on servers you've identity helps you to understand your workload performance history. This is crucial for right-sizing Azure VM SKUs, and disk recommendations in Azure.
 
 ## Assess migration readiness
 

articles/migrate/review-assessment.md

@@ -43,7 +43,7 @@ After the server is marked as ready for Azure, the assessment makes sizing recom
 | **Performance-based** | The compute recommendation is based on CPU and memory utilization data. <br> The storage recommendation is based on the input/output operations per second (IOPS) and throughput of the on-premises disks. Available disk types are Azure Standard HDD, Azure Standard SSD, Azure Premium disks, and Azure Ultra disks.  |
 | **As-is on-premises** | The compute recommendation is based on the on-premises server size. <br> The recommended storage is based on the selected storage type for the assessment.|
 
-You can review the source properties that were used for right sizing the targets. For each on-premises workload, the configuration properties and the aggregated performance data are available. Review the allocated cores, allocated memory, CPU utilization, and memory utilization for compute right sizing and disk size, read IO/s, and throughput for storage recommendations.  
+You can review the source properties that were used for right-sizing the targets. For each on-premises workload, the configuration properties and the aggregated performance data are available. Review the allocated cores, allocated memory, CPU utilization, and memory utilization for compute right-sizing and disk size, read IO/s, and throughput for storage recommendations.  
 
 On the **Target recommendations** page, you can review the target configuration and the recommendation reasoning for each target component like compute, storage, network etc.  
 

articles/migrate/target-right-sizing.md

@@ -35,7 +35,7 @@ If you use the appliance for discovery, it collects performance data directly fr
 
 2. The appliance combines the sample points to create a single data point every 10 minutes for VMware and Hyper-V servers, and every 5 minutes for physical servers. To create the data point, the appliance selects the peak values from all samples. It then sends the data point to Azure. 
 
-3. The assessment stores all the 10-minute data points for the last month. All the peaks are arranged in the ascending order to identify the appropriate data point to use for right sizing.  
+3. The assessment stores all the 10-minute data points for the last month. All the peaks are arranged in the ascending order to identify the appropriate data point to use for right-sizing.  
 
 ### Performance data collected for import-based discovery  
 

articles/migrate/toc.yml

@@ -96,7 +96,7 @@ items:
       href: assessment-report.md
     - name: Cost and savings calculations # provide details about cost calculations, Reservations & savings plan calculations, Environment based calculations, license cost.
       href: cost-estimation.md   
-    - name: Target right sizing # help users understand how perf data is used in depth
+    - name: Target right-sizing # help users understand how perf data is used in depth
       href: target-right-sizing.md
     - name: Confidence rating
       href: confidence-ratings.md
@@ -116,7 +116,7 @@ items:
           href: how-to-create-assessment.md
         - name: Customize assessment settings
           href: vm-assessment-properties.md
-        - name: Target right sizing
+        - name: Target right-sizing
           href: target-right-sizing.md
         - name: Review assessment report
           href: review-assessment.md

articles/migrate/vm-assessment-properties.md

@@ -20,7 +20,7 @@ This section describes the components that are part of an assessment.
 |-------------------|---------|--------  |                                                     
 | **Target settings**   | **Target VM series**         | The Azure VM series that you want to consider for rightsizing. For example, if you don't have a production environment that needs A-series VMs in Azure, you can exclude A-series from the list of series. The availability of VM series depends on the target location selected. [Learn more](/azure/virtual-machines/sizes/overview?branch=main&branchFallbackFrom=release-migrate-new-structure&tabs=breakdownseries,generalsizelist,computesizelist,memorysizelist,storagesizelist,gpusizelist,fpgasizelist,hpcsizelist). |
 | **Target settings**   | **Target storage disk**      | Specifies the type of target storage disk as Premium-managed, Standard HDD-managed, Standard SSD-managed, or Ultra disk. <br> **Premium or Standard or Ultra disk**: The assessment recommends a disk SKU within the storage type selected. <br>If you want a single-instance VM service level agreement (SLA) of 99.9%, consider using Premium-managed disks. This ensures that all disks are recommended as Premium-managed disks. <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> Azure Migrate supports only Managed disks for migration assessment.  |
-| **Right-Sizing**      | **Sizing criteria**          | This attribute is used for right sizing the target recommendations. <br> Use **as-is on-premises** sizing if you don't want to right size the targets and identify the targets according to your configuration for on-premises workloads. Use **performance-based** sizing to calculate compute recommendation based on CPU and memory utilization data and storage recommendation based on the input/output operations per second (IOPS) and throughput of the on-premises disks.  |
+| **Right-Sizing**      | **Sizing criteria**          | This attribute is used for right-sizing the target recommendations. <br> Use **as-is on-premises** sizing if you don't want to right size the targets and identify the targets according to your configuration for on-premises workloads. Use **performance-based** sizing to calculate compute recommendation based on CPU and memory utilization data and storage recommendation based on the input/output operations per second (IOPS) and throughput of the on-premises disks.  |
 | | **VM uptime** | The duration in days per month and hours per day for Azure VMs that won't run continuously. Cost estimates are based on that duration. The default values are 31 days per month and 24 hours per day. | 
 | | **Azure Hybrid Benefit**| Specifies whether you have software assurance and are eligible for [Azure Hybrid Benefit](/pricing/hybrid-benefit/) to use your existing OS licenses. For Azure VM assessments, you can bring in both Windows and Linux licenses. If the setting is enabled, Azure prices for selected operating systems aren't considered for VM costing.  |