Merge pull request #298102 from habibaum/11Apr-plr-feedback-addressed

PLR updates

Author: v-dirichards

articles/migrate/assessment-prerequisites.md

@@ -11,12 +11,12 @@ monikerRange: migrate
 
 # Prerequisites for assessments 
 
-Azure Migrate assessments identifies the readiness and right-sized Azure targets using the configuration and performance data collected from the source workloads. The quality of assessments depends on the quality of the data available for assessments. Thus, to get high quality assessments ensure you have all the prerequisites satisfied. Before creating the assessments, ensure the following: 
+Azure Migrate assessments identifies the readiness and right-sized Azure targets using the configuration and performance data collected from the source workloads. The quality of assessments depends on the quality of the data available for assessments. Thus, to get high quality assessments ensure you have all the prerequisites fulfilled. Before creating the assessments, ensure the following: 
 
 - You discovered the inventory of all the workloads and applications you intend to assess. 
 - You resolved any data collection issues that your workloads are flagged for.
 - You have enough performance data collected before you create the assessment. You can create assessments anytime, but we recommend letting the appliance collect the performance data for at least 24 hours.  
-- For better results, in the case of appliance-based discovery, ensure that the appliances are in a connected state and performance data is flowing. 
+- In the case of appliance-based discovery, for better results. Ensure that the appliances are in a connected state and performance data is flowing. 
 - If you have an Enterprise agreement with Microsoft and want to use the negotiated prices to identify the resource cost, ensure that you have access to the required subscriptions. 
 
 ## Discovery sources 

articles/migrate/assessment-properties.md

@@ -13,14 +13,14 @@ monikerRange: migrate
 
 This article explains the assessment properties on the **General** tab that you can use when creating an assessment. These general properties apply to all workloads in an application or for cross-workload assessments. They also apply to individual workload assessments. 
 
-| **Setting Category**  | **Deafult Setting** | **Details** |                
+| **Setting Category**  | **Default Setting** | **Details** |                
 |-------------------|---------|--------  |                                                     
 | **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

@@ -10,9 +10,9 @@ ms.custom: engagement-fy24
 monikerRange: migrate
 --- 
 
-# Assessment Report 
+# Assessment report of Azure readiness
 
-Each assessment provides four key outputs: Azure readiness, right-sized target recommendations, cost details, and migration guidance. 
+Each assessment provides four key outputs: Azure readiness, right sized target recommendations, cost details, and migration guidance. 
 
 ## Understanding Azure readiness 
 
@@ -26,9 +26,9 @@ Not all workloads are suitable to run in Azure. An Azure Migrate assessment eval
 
 - **Readiness unknown**: Azure Migrate can't determine the readiness of the server because of insufficient metadata. 
 
-Readiness calculations differ based on the source and targets and the methodology to calculate also differs across assessment types. Learn more about readiness calculations of Azure VM assessments, Azure SQL assessments, AVS assessments, and Web app assessments. 
+Readiness calculations differ based on the source and targets and the methodology to calculate also differs across assessment types. 
 
-## Right-sized recommendations 
+## Right sized recommendations 
 
 After the server is marked as ready for Azure, the assessment makes sizing recommendations in the assessment. These recommendations identify the target for the on-premises workloads being assessed. Sizing calculations depend on whether you're using as-is on-premises sizing or performance-based sizing. 
 
@@ -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 rightsizing. 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 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) 
 
@@ -75,7 +75,7 @@ If any of these utilization numbers isn't available, the size recommendations mi
 
 ### Ratings 
 
-This table shows the assessment confidence ratings, which depend on the percentage of available data points: 
+The table below shows the confidence ratings for assessment, which depend on the percentage of available data points: 
 
 **Availability of data points** | **Confidence rating** 
 --- | --- 

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

@@ -83,8 +83,8 @@ The appliance collects the following performance data for compute settings:
 - The appliance collects a real-time sample point. For MySQL instances, it collects a sample point every 30 seconds.
 - 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.
+- 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.
     - 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:

articles/migrate/centralized-issue-tracking.md

@@ -29,7 +29,7 @@ The Action Center can be accessed directly from the Azure Migrate dashboard, pro
 
     ![Screenshot of Action Center.](./media/centralized-issue-tracking/action-center.png)
 
-- **Comprehensive issue tracking:** Users can see detailed information for each issue, including **severity level, affected workloads, affected features,** and **timestamps**. Each issue is accompanied by specific messages, allowing users to understand the nature of the problem and respond accordingly. Users can also sort and filter issues based on **severity, affected workload(s), timestamps**, and other parameters, enabling efficient prioritization of tasks and quick identification of high-severity issues that require immediate attention. Moreover, users can also have a view by affected workloads, where they can identify different issues by workloads.
+- **Comprehensive issue tracking:** Users can see detailed information for each issue, including **severity level, affected workloads, affected features,** and **timestamps**. Each issue is accompanied by specific messages, allowing users to understand the nature of the problem and respond accordingly. Users can also sort and filter issues based on **severity, affected workload(s), timestamps**, and other parameters, enabling efficient prioritization of tasks and quick identification of high-severity issues that require immediate attention. Users can also have a view by affected workloads, where they can identify different issues by workloads.
 
     [ ![Screenshot of affected workloads view.](./media/centralized-issue-tracking/view-affected-workloads-inline.png) ](./media/centralized-issue-tracking/view-affected-workloads-expanded.png#lightbox)
 

articles/migrate/cost-estimation.md

@@ -11,7 +11,10 @@ monikerRange: migrate
 
 # Cost estimation of Assessment in Azure Migrate
 
-Azure Migrate assessments provide you with an estimated cost of hosting the recommended targets on Azure. These costs are identified for each right-sized target on Azure. The cost estimates are dependent on the rates in the specified region, any applicable offers, and the licensing program selected by you. 
+Azure Migrate assessments provide you with an estimated cost of hosting the recommended targets on Azure. These costs are identified for each right-sized target on Azure. 
+
+> [!NOTE]
+> The cost estimates are dependent on the rates in the specified region, any applicable offers, and the licensing program selected by you. 
 
 This article describes Azure Migrate assessments, which estimate hosting costs for recommended targets on Azure, based on region rates, applicable offers, and selected licensing programs.