MicrosoftDocs
diff --git a/‎articles/migrate/assessments-overview-migrate-to-azure-db-mysql.md
Lines changed: 43 additions & 35 deletions b/‎articles/migrate/assessments-overview-migrate-to-azure-db-mysql.md
Lines changed: 43 additions & 35 deletions
@@ -11,11 +11,11 @@ ms.date: 02/24/2025
 
 This article provides an overview of assessments for migrating on-premises MySQL database instances from a VMware, Microsoft Hyper-V, and Physical environment to Azure Database for MySQL using the [Azure Migrate: Discovery and assessment tool](migrate-services-overview.md).
 
-## What is an assessment?
+## Overview
 
 An assessment with the Discovery and assessment tool provides a point-in-time snapshot of data, measuring the readiness and estimating the impact of migrating on-premises servers, databases, and web apps to Azure, while also offering recommendations on suitable Azure SKUs and associated costs.
 
-### Types of assessments
+### Assessment Types
 
 The Azure Migrate: Discovery and assessment tool supports the following types of assessments:
 
@@ -36,46 +36,46 @@ After you [discover MySQL instances and their attributes](tutorial-discover-mysq
 MySQL assessments are performed on the **performance-based** sizing criteria, making recommendations based on collected performance data of MySQL instances, including CPU utilization, Memory utilization, IOPS, IO Count, total number of connections and read-write ratio.  
 
 > [!NOTE]
-> The assessments only include MySQL database instances that are in online status. For  any other status, the assessment ignores the readiness, sizing, and cost calculation for such instances. In case you wish to assess such instances, change the status of the instance and recalculate the assessment later.
+> The assessments only include MySQL database instances that are in online status. For instances with any other status, the assessment ignores the readiness, sizing, and cost calculation. In case you wish to assess such instances, change the status of the instance and recalculate the assessment later.
 
-## How do I assess my on-premises MySQL instances?
+## Assess on-premises MySQL instances
 
 You can assess your on-premises MySQL instances using the configuration and utilization data collected by lightweight Azure Migrate appliances, which discover the instances and databases and send the data to the Azure Migrate service.
 
-1. Deploy the Azure Migrate appliances to discover the MySQL instances: [Refer this tutorial](tutorial-discover-mysql-database-instances.md) to learn more about the steps to deploy the Azure Migrate appliances and discover the MySQL instances that you want to assess.
-1. Create a MySQL assessment: Refer this [tutorial](create-mysql-assessment.md) for steps to create a new assessment and review the reports.
+1. Deploy the Azure Migrate appliances to discover the MySQL instances: [Refer this tutorial](tutorial-discover-mysql-database-instances.md) to deploy the Azure Migrate appliances and discover the MySQL instances that you want to assess.
+1. Create a MySQL assessment: Refer this [tutorial](create-mysql-assessment.md) to create a new assessment and review the reports.
 
-## What are the properties used to create and customize a MySQL assessment?
+## Properties to create and customize a MySQL assessment
 
 The Azure Database for MySQL assessment properties includes:
 
 **Section** | **Setting** | **Details**
 --- | --- | ---
 Target and pricing settings | **Target location**  | The Azure region to which you want to migrate. Azure Database for MySQL configuration and cost recommendations are based on the location that you specify.
-Target and pricing settings | **Environment type** | The environment for the MySQL deployments to apply Azure Database for MySQL configuration and cost recommendations applicable to Production or Dev/Test.
+Target and pricing settings | **Environment type** | The environment for the MySQL deployments to apply Azure Database for MySQL configuration and cost recommendations applicable to Production or Development/Testing.
 Target and pricing settings | **Licensing program**  | The Azure offer if you're enrolled. Currently, the field is Pay-as-you-go by default, which gives you retail Azure prices.
 Target and pricing settings | **Currency** | The billing currency for your account.
 Target and pricing settings | **Savings options**  | Specify the reserved capacity savings option that you want the assessment to consider to optimize your Azure compute cost. <br/><br> Azure reservations (one year or three years reserved) are a good option for the most consistently running resources. <br/><br> When you select None, the Azure compute cost is based on the Pay-as-you-go rate or based on actual usage. <br/><br> You need to select pay-as-you-go in the offer/licensing program to be able to use Reserved Instances. When you select any savings option other than None, the Discount (%) setting isn’t applicable. The monthly cost estimates are calculated by multiplying 744 hours with the hourly price of the recommended SKU.
 Target and pricing settings | **Discount (%)** | Any subscription-specific discounts you receive on top of the Azure offer. The default setting is 0%.
 Assessment criteria | **Sizing criteria**  | Set to be **Performance-based** by default, which means Azure Migrate collects performance metrics pertaining to MySQL instances to recommend an optimal-sized Azure Database for MySQL instance configuration.
-Assessment criteria | **Performance history** | Indicate the data duration on which you want to base the assessment. (Default is one day).
-Assessment criteria | **Percentile utilization** | Indicate the percentile value you want to use for the performance sample. (Default is 95th percentile).
+Assessment criteria | **Performance history** | Indicate the data duration on which you want to base the assessment (Default is one day).
+Assessment criteria | **Percentile utilization** | Indicate the percentile value you want to use for the performance sample (Default is 95th percentile).
 Assessment criteria | **Comfort factor** | Indicate the buffer you want to use during assessment. This accounts for issues like seasonal usage, short performance history, and likely increases in future usage.
-Azure DB for MySQL – Flexible Server sizing | **Service Tier** | Choose the most appropriate service tier option to accommodate your business needs for migration to Azure Database for MySQL. <br/><br> By default, all three service tiers are selected. Azure Migrate recommends the best suited service tier for your servers based on your Environment Type and the collected performance data. <br/><br> Select only *General Purpose* if you want an Azure Database for MySQL configuration designed for business workloads that require balanced computing and memory with scalable I/O throughput. <br/><br> Select only *Business Critical* if you want an Azure Database for MySQL configuration designed for high-performance database workloads that require in-memory performance for faster transaction processing and higher concurrency.
+Azure DB for MySQL – Flexible Server sizing | **Service Tier** | Choose the most appropriate service tier option to accommodate your business needs for migration to Azure Database for MySQL. <br/><br> By default, all three service tiers are selected. Azure Migrate recommends the best suited service tier for your servers based on your Environment Type and the collected performance data. <br/><br> Select *General Purpose* if you want an Azure Database for MySQL configuration designed for business workloads that require balanced computing and memory with scalable I/O throughput. <br/><br> Select *Business Critical* if you want an Azure Database for MySQL configuration designed for high-performance database workloads that require in-memory performance for faster transaction processing and higher concurrency.
 
 
-## How is the performance data calculated for MySQL instances?
+## Performance data calculation for MySQL instances
 
 The appliance collects performance data for compute settings with these steps:
 
-1. The appliance collects a real-time sample point. For MySQL instances, it collects a sample point every 30 seconds.
-1. 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.
-1. Azure Migrate stores all the 10-minute data points for the last month.
-1. 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.
+- 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.
     - 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.
-1. This value is multiplied by the comfort factor to get the effective performance utilization data for these metrics that the appliance collects:
+- This value is multiplied by the comfort factor to get the effective performance utilization data for these metrics that the appliance collects:
     - CPU utilization (%)
     - Memory utilization (%)
     - IOPS and IO Count
@@ -87,14 +87,15 @@ The appliance collects performance data for compute settings with these steps:
 Readiness to migrate a MySQL instance to Azure Database for MySQL is determined through various feature compatibility checks between the source and target instances. These checks include:
 
 - Supported versions, editions, storage engines, plugins, configuration or parameter values, user permissions and privileges.
-- Maximum supported storage size, vCores, Memory, IOPS, InnoDB buffer pool size, connections, tablespace number, and size.
+- Maximum supported storage size, vCores, Memory, IOPS, DB buffer pool size, connections, tablespace number, and size.
 - Security settings, and more.
 
 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.
-- **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.
+- **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.
+- **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.
+
 
 ## Calculate sizing
 
@@ -103,24 +104,24 @@ After the assessment determines the readiness, for every server that is either *
 ### Compute sizing
 
 During the discovery process, Azure Migrate collects the MySQL instance configuration and performance data that includes:
-- vCores (allocated) and CPU utilization (%): CPU utilization for a MySQL instance is the percentage of allocated CPU utilized by the MySQL instance on the server.
-- Memory (allocated) and memory utilization (%): The amount of memory allocated to the MySQL instance, and its utilization percentage.
-- IOPS: Calculated by adding the Read and Write IOPS for each instance.
+- **vCores (allocated) and CPU utilization (%)**: CPU utilization for a MySQL instance is the percentage of allocated CPU utilized by the MySQL instance on the server.
+- **Memory (allocated) and memory utilization (%)**: The amount of memory allocated to the MySQL instance, and its utilization percentage.
+- **IOPS**: Calculated by adding the Read and Write IOPS for each instance.
 - Total number of connections made to the MySQL instance.
-- Read-write ratio: Used to determine whether the workload is memory-intensive or CPU-intensive, which in turn helps decide the appropriate service tier.
+- **Read-write ratio**: Used to determine whether the workload is memory-intensive or CPU-intensive, which in turn helps decide the appropriate service tier.
 
-The assessment aggregates all the configuration and performance data and tries to find the best match across the [various Azure Database for MySQL service tiers and configurations](https://learn.microsoft.com/azure/mysql/flexible-server/concepts-service-tiers-storage), selecting a configuration that can match or exceed the MySQL instance performance requirements, optimizing the cost.
+The assessment aggregates all the configuration and performance data and tries to find the best match across the [various Azure Database for MySQL service tiers and configurations](https://learn.microsoft.com/azure/mysql/flexible-server/concepts-service-tiers-storage), selecting a configuration that can match or exceed the MySQL instance performance requirements, and  optimizing the cost.
 
 ### Storage sizing
-Azure Migrate calculates the total disk space used by the MySQL instance (including database files, temporary files, transaction logs, and the MySQL server logs) and suggests the recommended storage to provision in Azure Database for MySQL. For Burstable and General Purpose service tiers, the storage range spans from a minimum of 20 GiB to a maximum of 16 TiB, while for the Business Critical service tier, the storage support extends up to 32 TiB. In all service tiers, storage is scaled in 1-GiB increments and can be scaled up (but not down) after the server is created.
+Azure Migrate calculates the total disk space used by the MySQL instance (including database files, temporary files, transaction logs, and the MySQL server logs) and suggests the recommended storage to provision in Azure Database for MySQL. For Burstable and General Purpose service tiers, the storage range spans from a minimum of 20 GiB to a maximum of 16 TiB, while for the Business Critical service tier, the storage support extends up to 32 TiB. In all service tiers, storage is scaled in 1 GiB increments and can be scaled up (but not down) after the server is created.
 
 ### IOPS sizing
 Azure Migrate recommends the [Autoscale IOPS feature in Azure Database for MySQL](https://learn.microsoft.com/azure/mysql/flexible-server/concepts-service-tiers-storage#autoscale-iops), which enables the MySQL instance to automatically scale the database instance’s performance (IO) seamlessly and independent of the selected storage size, depending on the workload needs. With Autoscale IOPS, you pay only for the IO the server uses, eliminating the need to provision and pay for resources that aren't fully utilized, thereby saving time and money.
 
 ## Confidence ratings
 
 Each MySQL assessment is associated with a confidence rating. The rating ranges from one (lowest) to five (highest) stars. The confidence rating helps you estimate the reliability of the size recommendations Azure Migrate provides.
-- The confidence rating is assigned to an assessment. The rating is based on the availability of data points that are needed to compute the assessment.
+-  The rating is based on the availability of data points that are needed to compute the assessment.
 - For performance-based sizing, the assessment collects performance data of all the MySQL instances and databases, which include:
   - CPU utilization (%)
   -	Memory utilization (%)
@@ -143,15 +144,22 @@ Each MySQL assessment is associated with a confidence rating. The rating ranges
 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.
-- The Assessment isn't able to collect the performance data for some or all the servers in the assessment period. For a high confidence rating, ensure that:
+- The Assessment isn't able to collect the performance data for some or all the servers in the assessment period. 
+
+**Recalculate** the assessment to reflect the latest changes in confidence rating.
+
+- Some database instances were created during the time for which the assessment was calculated. For example, you created an assessment for the performance history of the last month, but some instances were created only a week ago. In this case, the performance data for the new servers won't be available for the entire duration and the confidence rating would be low.
+
+### High confidence ratings
+
+Here are a few reasons why an assessment could have a high confidence rating:
+
   - Servers are powered on during the assessment.
   - Outbound connections on ports 3306 are allowed.
   - If Azure Migrate connection status of the MySQL agent in Azure Migrate is Connected, check the last heartbeat.
   - Azure Migrate connection status for all MySQL instances is Connected in the discovered MySQL instance section.
 
-  **Recalculate** the assessment to reflect the latest changes in confidence rating.
-
-- Some database instances were created during the time for which the assessment was calculated. For example, you created an assessment for the performance history of the last month, but some instances were created only a week ago. In this case, the performance data for the new servers won't be available for the entire duration and the confidence rating would be low.
+ **Recalculate** the assessment to reflect the latest changes in confidence rating.
 
 > [!NOTE]
 > As MySQL assessments are performance-based assessments, if the confidence rating of any assessment is fewer than five stars, we recommend that you wait at least a day for the appliance to profile the environment and then recalculate the assessment. Otherwise, performance-based sizing might be unreliable.
@@ -169,6 +177,6 @@ To calculate the compute, storage and IO costs for an Azure Database for MySQL c
 
 ## Next steps
 
- - [Learn how to run a MySQL assessment.](create-mysql-assessment.md)
- - [Get started on your MySQL migration journey to Azure Database for MySQL.](https://learn.microsoft.com/training/modules/choose-tool-to-migrate-data-to-azure-database-for-mysql/)
+ - [Learn how to run a MySQL assessment](create-mysql-assessment.md).
+ - [Get started on your MySQL migration journey to Azure Database for MySQL](https://learn.microsoft.com/training/modules/choose-tool-to-migrate-data-to-azure-database-for-mysql/).