Merge pull request #307502 from ankitsurkar06/CodeScan

Code scan

Author: v-dirichards

articles/migrate/assessment-report.md

@@ -55,61 +55,51 @@ This value is multiplied by the comfort factor(taken as an input in assessment s
 
 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) 
+### Performance coverage (performance-based)
 
-Each performance-based Azure VM assessment in Azure Migrate 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. 
+Each performance-based Azure VM assessment in Azure Migrate is associated with a performance coverage. The coverage ranges from 0-100%. The performance coverage 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 performance coverage is assigned to an assessment. The coverage is based on the availability of data points that are needed to compute the assessment.
 
-- For performance-based sizing, the assessment needs: 
+- For performance-based sizing, the assessment needs:
 
-  - The utilization data for CPU and RAM. 
+  - The utilization data for CPU and RAM.
 
-  - The disk IOPS and throughput data for every disk attached to the server. 
+  - The disk IOPS and throughput data for every disk attached to the server.
 
-  - The network I/O to handle performance-based sizing for each network adapter attached to a server. 
+  - The network I/O to handle performance-based sizing for each network adapter attached to a server.
 
-If any of these utilization numbers isn't available, the size recommendations might be unreliable. 
+If any of these utilization numbers isn't available, the size recommendations might be unreliable.
 
 >[!Note]
->Confidence ratings aren't assigned for servers assessed using an imported CSV file. Ratings also aren't applicable for as-is on-premises assessment. 
+>Performance coverage isn't assigned for servers assessed using an imported CSV file. Coverage also isn't applicable for as-is on-premises assessment.
 
-### Ratings 
+### Coverage
 
-The table below shows the confidence ratings for assessment, which depend on the percentage of available data points: 
+### Low performance coverage
 
-**Availability of data points** | **Confidence rating** 
---- | --- 
-0-20% | One star 
-21-40% | Two stars 
-41-60% | Three stars 
-61-80% | Four stars 
-81-100% | Five stars 
+Here are a few reasons why an assessment could get a low performance coverage:
 
-### Low confidence ratings 
+- 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.
 
-Here are a few reasons why an assessment could get a low confidence rating: 
+- Assessment isn't able to collect the performance data for some or all the servers in the assessment period. For a high performance coverage, ensure that:
 
-- 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 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: 
-
-  - Servers are powered on for the duration of the assessment 
+  - 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 
 
-**Recalculate** the assessment to reflect the latest changes in confidence rating. 
+**Recalculate** the assessment to reflect the latest changes in performance coverage. 
 
-- 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. 
+- 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 performance coverage would be low. 
 
 >[!Note]
->If the confidence rating of any assessment is less 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. In that case, we recommend that you switch the assessment to on-premises sizing. 
+>If the performance coverage of any assessment is less than 80%, 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. In that case, we recommend that you switch the assessment to on-premises sizing. 
 
 ## Next steps 
 
 - [Review](./best-practices-assessment.md) best practices for creating assessments. 
 - Learn about running assessments for servers running in [VMware](./tutorial-discover-vmware.md) and [Hyper-V](./tutorial-discover-hyper-v.md) environment, and [physical servers](./tutorial-discover-physical.md). 
 - Learn about assessing servers [imported with a CSV file](./tutorial-discover-import.md). 
-- Learn about setting up [dependency visualization](./concepts-dependency-visualization.md). 
+- Learn about setting up [dependency visualization](./concepts-dependency-visualization.md).

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

@@ -133,51 +133,42 @@ Azure Migrate calculates the total disk space used by the MySQL instance (includ
 ### IOPS sizing
 Azure Migrate recommends the [Autoscale IOPS feature in Azure Database for MySQL](/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
+## Performance coverage
 
-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 rating is based on the availability of data points that are required to compute the assessment.
+Each MySQL assessment is associated with a performance coverage. The coverage ranges from one (lowest) to five (highest) stars. The performance coverage helps you estimate the reliability of the size recommendations Azure Migrate provides.
+-  The coverage is based on the availability of data points that are required 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 (%)
-  -	IOPS
+  - Memory utilization (%)
+  - IOPS
   - Number of connections to the MySQL instance
   - Read-write ratio
-- If any of these utilization numbers aren't available, the size recommendations might be unreliable. This table shows the assessment confidence ratings, which depend on the percentage of available data points:
+- If any of these utilization numbers aren't available, the size recommendations might be unreliable. This table shows the assessment performance coverage, which depend on the percentage of available data points:
 
-    **Data point availability** | **Confidence rating**
-    --- | ---
-    0%-20% | One star
-    21%-40% | Two stars
-    41%-60% | Three stars
-    61%-80% | Four stars
-    81%-100% | Five stars
+### Low performance coverage
 
-
-### Low confidence ratings
-
-Here are a few reasons why an assessment could get a low confidence rating:
+Here are a few reasons why an assessment could get a low performance coverage:
 
 - 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. 
+- 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.
+**Recalculate** the assessment to reflect the latest changes in performance coverage.
 
-- 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.
+- 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 performance coverage would be low.
 
-### High confidence ratings
+### High performance coverage
 
-Here are a few reasons why an assessment could have a high confidence rating:
+Here are a few reasons why an assessment could have a high performance coverage:
 
   - 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.
+ **Recalculate** the assessment to reflect the latest changes in performance coverage.
 
 > [!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.
+> As MySQL assessments are performance-based assessments, if the performance coverage of any assessment is fewer than 80%, 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.
 
 ## Calculate monthly costs
 Once the sizing recommendations are complete, MySQL assessment calculates the compute, storage, and IO costs for the recommended Azure Database for MySQL configurations using an internal pricing API. It aggregates these costs across all the instances to determine the total monthly cost.

articles/migrate/best-practices-assessment.md

@@ -32,7 +32,7 @@ Sizing criteria options in Azure Migrate assessments:
 
 **Sizing criteria** | **Details** | **Data**
 --- | --- | ---
-**Performance-based** | Assessments that make recommendations based on collected performance data. | **Azure VM assessment**: VM size recommendation is based on CPU and memory utilization data.<br/><br/> Disk type recommendation (standard HDD/SSD, premium-managed or ultra disks) is based on the IOPS (Input/output per second) and throughput of the on-premises disks.<br/><br/>**Azure SQL assessment**: The Azure SQL configuration is based on performance data of SQL instances and databases, which includes: CPU utilization, Memory utilization, IOPS (Data and Log files), throughput, and latency of IO operations<br/><br/>**Azure VMware Solution (AVS) assessment**: If the data was imported using an RVTools file, AVS nodes recommendation is based on storage utilization data and provisioned CPU and RAM. If the data was imported using an Azure Migrate CSV file and CPU and RAM utilization data is provided, it's used. Else, the configured CPU, RAM, and storage is used. If the data was successfully imported using an Azure Migrate appliance, the CPU and RAM utilization data is used.
+**Performance-based** | Assessments that make recommendations based on collected performance data. | **Azure VM assessment**: VM size recommendation is based on CPU and memory utilization data.<br/><br/> Disk type recommendation (standard HDD/SSD, premium-managed or ultra disks) is based on the IOPS (Input/output per second) and throughput of the on-premises disks.<br/><br/>**Azure SQL assessment**: The Azure SQL configuration is based on performance data of SQL instances and databases, which includes: CPU utilization, Memory utilization, IOPS (Data and Log files), throughput, and latency of IO operations<br/><br/>**Azure VMware Solution (AVS) assessment**: If the data was imported using an RVTools file, AVS nodes recommendation is based on storage utilization data and provisioned CPU and RAM. If the data was imported using an Azure Migrate CSV file and CPU and RAM utilization data is provided, it's used. Else, the configured CPU, RAM, and storage are used. If the data was successfully imported using an Azure Migrate appliance, the CPU and RAM utilization data is used.
 **As-is on-premises** | Assessments that don't use performance data to make recommendations. | **Azure VM assessment**: VM size recommendation is based on the on-premises VM size<br/><br> The recommended disk type is based on what you select in the storage type setting for the assessment.<br/><br/> **Azure App Service assessment**: Assessment recommendation is based on on-premises web apps configuration data.<br/><br/> **Azure VMware Solution (AVS) assessment**: AVS nodes recommendation is based on the on-premises VM size.
 
 > [!NOTE]
@@ -78,9 +78,9 @@ The storage engine used in AVS is vSAN. vSAN storage policies define storage req
 2 | RAID-6 (Erasure Coding) | 6 | A 100GB VM would consume 150GB.
 3 | RAID-1 (Mirroring) | 7 | A 100GB VM would consume 400GB.
 
-## Best practices for confidence ratings
+## Best practices for performance coverage
 
-When you run performance-based assessments, a confidence rating from 1-star (lowest) to 5-star (highest) is awarded to the assessment. To use confidence ratings effectively:
+When you run performance-based assessments, a performance coverage is assigned to the assessment. To use performance coverage effectively:
 
 - Azure VM and AVS assessments need:
     - The CPU and memory utilization data for each of the servers
@@ -92,15 +92,8 @@ When you run performance-based assessments, a confidence rating from 1-star (low
     - The read/write IOPS/throughput data of data and Log files
     - The latency of IO operations
 
-Depending on the percentage of data points available for the selected duration, the confidence rating for an assessment is provided as summarized in the following table.
+Depending on the percentage of data points available for the selected duration, the performance coverage for an assessment is provided as summarized in the following table.
 
-   **Data point availability** | **Confidence rating**
-   --- | ---
-   0%-20% | 1 Star
-   21%-40% | 2 Star
-   41%-60% | 3 Star
-   61%-80% | 4 Star
-   81%-100% | 5 Star
 
 ## Common assessment issues
 
@@ -148,8 +141,7 @@ If there are changes to on-premises web apps that are in a group that's been ass
 
     Run the assessment again (**Recalculate**) to reflect the changes.
 
-### Low confidence rating
-
+### Low performance coverage
 An assessment might not have all the data points for many reasons:
 
 - You didn't profile your environment for the duration for which you're creating the assessment. For example, if you're creating an assessment with performance duration set to one week, you need to wait for at least a week after you start the discovery for all the data points to get collected. If you can't wait for the duration, change the performance duration to a smaller period and "Recalculate" the assessment.