Merge pull request #285050 from v-sreedevank/20Aug-BestPractice

AVS best practice update

Author: prmerger-automator[bot]

articles/migrate/best-practices-assessment.md

@@ -12,7 +12,7 @@ ms.custom: engagement-fy23
 
 # Best practices for creating assessments
 
-[Azure Migrate](./migrate-services-overview.md) provides a hub of tools that help you to discover, assess, and migrate apps, infrastructure, and workloads to Microsoft Azure. The hub includes Azure Migrate tools, and third-party independent software vendor (ISV) offerings.
+[Azure Migrate](./migrate-services-overview.md) provides a hub of tools that help you to discover, assess, and migrate apps, infrastructure, and workloads to Microsoft Azure. The hub includes Azure Migrate tools, and non-Microsoft independent software vendor (ISV) offerings.
 
 This article summarizes the best practices when creating assessments using the Azure Migrate Discovery and assessment tool.
 
@@ -22,22 +22,25 @@ Assessments you create with Azure Migrate: Discovery and assessment tool are a p
 --- | ---
 **Azure VM** | Assessments to migrate your on-premises servers to Azure virtual machines. <br/><br/> You can assess your on-premises servers in [VMware](how-to-set-up-appliance-vmware.md) and [Hyper-V](how-to-set-up-appliance-hyper-v.md) environment, and [physical servers](how-to-set-up-appliance-physical.md) for migration to Azure using this assessment type. [Learn more](concepts-assessment-calculation.md)
 **Azure SQL** | Assessments to migrate your on-premises SQL servers from your VMware environment to Azure SQL Database or Azure SQL Managed Instance. [Learn More](concepts-azure-sql-assessment-calculation.md)
-**Azure App Service** | Assessments to migrate your on-premises ASP.NET web apps running on IIS web server, from your VMware environment to Azure App Service. [Learn More](concepts-azure-webapps-assessment-calculation.md)
+**Azure App Service** | Assessments to migrate your on-premises ASP.NET web apps running on IIS (Internet Information Services) web server, from your VMware environment to Azure App Service. [Learn More](concepts-azure-webapps-assessment-calculation.md)
 **Azure VMware Solution (AVS)** | Assessments to migrate your on-premises servers to [Azure VMware Solution (AVS)](../azure-vmware/introduction.md). <br/><br/> You can assess your on-premises [VMware VMs](how-to-set-up-appliance-vmware.md) for migration to Azure VMware Solution (AVS) using this assessment type. [Learn more](concepts-azure-vmware-solution-assessment-calculation.md)
 
 > [!NOTE]
-> If the number of Azure VM or AVS assessments are incorrect on the Discovery and assessment tool, click on the total number of assessments to navigate to all the assessments and recalculate the Azure VM or AVS assessments. The Discovery and assessment tool will then show the correct count for that assessment type. 
+> If the number of Azure VM or AVS assessments is incorrect on the Discovery and assessment tool, select the total number of assessments to navigate to all the assessments and recalculate the Azure VM or AVS assessments. The Discovery and assessment tool shows the correct count for that assessment type. 
 
 ### Sizing criteria
 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 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**: AVS nodes recommendation is based on CPU and memory utilization 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.
 **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]
+> If the data is being discovered using an Azure migrate appliance, VMs in disconnected or powered-off hosts are not discovered and considered for assessment.
+
 #### Example
-As an example, if you have an on-premises VM with four cores at 20% utilization, and memory of 8 GB with 10% utilization, the Azure VM assessment will be as follows:
+As an example, if you have an on-premises VM with four cores at 20% utilization, and memory of 8 GB with 10% utilization, the Azure VM assessment is as follows:
 
 - **Performance-based assessment**:
     - Identifies effective cores and memory based on core (4 x 0.20 = 0.8), and memory (8 GB x 0.10 = 0.8) utilization.
@@ -52,10 +55,10 @@ As an example, if you have an on-premises VM with four cores at 20% utilization,
 
 The Azure Migrate appliance continuously profiles your on-premises environment, and sends metadata and performance data to Azure. Follow these best practices for assessments of servers discovered using an appliance:
 
-- **Create as-is assessments**: You can create as-is assessments immediately once your servers show up in the Azure Migrate portal. You cannot create an Azure SQL assessment with sizing criteria "As on-premises". Azure App Service assessment by default is "As on-premises".
+- **Create as-is assessments**: You can create as-is assessments immediately once your servers show up in the Azure Migrate portal. You can't create an Azure SQL assessment with sizing criteria "As on-premises". Azure App Service assessment by default is "As on-premises".
 - **Create performance-based assessment**: After setting up discovery, we recommend that you wait at least a day before running a performance-based assessment:
     - Collecting performance data takes time. Waiting at least a day ensures that there are enough performance data points before you run the assessment.
-    - When you're running performance-based assessments, make sure you profile your environment for the assessment duration. For example, if you create an assessment with a performance duration set to one week, you need to wait for at least a week after you start discovery, for all the data points to be collected. If you don't, the assessment won't get a five-star rating.
+    - When you're running performance-based assessments, make sure you profile your environment for the assessment duration. For example, if you create an assessment with a performance duration set to one week, you need to wait for at least a week after you start discovery, for all the data points to be collected. If you don't, the assessment doesn't get a five-star rating.
 - **Recalculate assessments**: Since assessments are point-in-time snapshots, they aren't automatically updated with the latest data. To update an assessment with the latest data, you need to recalculate it.
 
 Follow these best practices for assessments of servers imported into Azure Migrate via .CSV file:
@@ -64,7 +67,7 @@ Follow these best practices for assessments of servers imported into Azure Migra
 - **Create performance-based assessment**: This helps to get a better cost estimate, especially if you have overprovisioned server capacity on-premises. However, the accuracy of the performance-based assessment depends on the performance data specified by you for the servers. 
 - **Recalculate assessments**: Since assessments are point-in-time snapshots, they aren't automatically updated with the latest data. To update an assessment with the latest imported data, you need to recalculate it.
 
-### FTT Sizing Parameters for AVS assessments
+### Failures to Tolerate (FTT) Sizing Parameters for AVS assessments
 
 The storage engine used in AVS is vSAN. vSAN storage policies define storage requirements for your virtual machines. These policies guarantee the required level of service for your VMs because they determine how storage is allocated to the VM. These are the available FTT-Raid Combinations: 
 
@@ -112,7 +115,7 @@ If you add or remove servers from a group after you create an assessment, the as
 
 #### Azure VM assessment and AVS assessment
 
-If there are changes on the on-premises servers that are in a group that's been assessed, the assessment is marked **outdated**. An assessment can be marked as “Outdated” because of one or more changes in below properties:
+If there are changes on the on-premises servers that are in a group that's been assessed, the assessment is marked **outdated**. An assessment can be marked as "Outdated" because of one or more changes in below properties:
 
 - Number of processor cores
 - Allocated memory
@@ -127,7 +130,7 @@ Run the assessment again (**Recalculate**) to reflect the changes.
 
 #### Azure SQL assessment
 
-If there are changes to on-premises SQL instances and databases that are in a group that's been assessed, the assessment is marked **outdated**. An assessment can be marked as “Outdated” because of one or more reasons below:
+If there are changes to on-premises SQL instances and databases that are in a group that's been assessed, the assessment is marked **outdated**. An assessment can be marked as "Outdated" because of one or more reasons below:
 
 - SQL instance was added or removed from a server
 - SQL database was added or removed from a SQL instance
@@ -139,7 +142,7 @@ If there are changes to on-premises SQL instances and databases that are in a gr
 
 #### Azure App Service assessment
 
-If there are changes to on-premises web apps that are in a group that's been assessed, the assessment is marked **outdated**. An assessment can be marked as “Outdated” because of one or more reasons below:
+If there are changes to on-premises web apps that are in a group that's been assessed, the assessment is marked **outdated**. An assessment can be marked as "Outdated" because of one or more reasons below:
 
 - Web apps were added or removed from a server
 - Configuration changes made to existing web apps.
@@ -150,26 +153,26 @@ If there are changes to on-premises web apps that are in a group that's been ass
 
 An assessment might not have all the data points for many reasons:
 
-- You did not profile your environment for the duration for which you are creating the assessment. For example, if you are 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 cannot wait for the duration, please change the performance duration to a smaller period and 'Recalculate' the assessment.
+- 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.
 
-- 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 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 during the assessment
     - Outbound connections on ports 443 are allowed
-    - For Hyper-V Servers dynamic memory is enabled 
-    - The connection status of agents in Azure Migrate are 'Connected' and check the last heartbeat
-    - For Azure SQL assessments, Azure Migrate connection status for all SQL instances is "Connected" in the discovered SQL instance blade
+    - For Hyper-V servers, dynamic memory is enabled 
+    - The connection status of agents in Azure Migrate is "Connected" and check the last heartbeat
+    - For Azure SQL assessments, Azure Migrate connection status for all SQL instances is "Connected" in the discovered SQL instance tab.
 
-    Please 'Recalculate' the assessment to reflect the latest changes in confidence rating.
+    Recalculate the assessment to reflect the latest changes in confidence rating.
 
-- For Azure VM and AVS assessments, few servers were created after discovery had started. For example, if you are creating an assessment for the performance history of last one month, but few servers were created in the environment 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.
+- For Azure VM and AVS assessments, few servers were created after discovery had started. For example, if you're creating an assessment for the performance history of last one month, but few servers were created in the environment 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.
 
-- For Azure SQL assessments, few SQL instances or databases were created after discovery had started. For example, if you are creating an assessment for the performance history of last one month, but few SQL instances or databases were created in the environment 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.
+- For Azure SQL assessments, few SQL instances or databases were created after discovery had started. For example, if you're creating an assessment for the performance history of last one month, but few SQL instances or databases were created in the environment 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.
 
 ### Migration Tool Guidance for AVS assessments
 
 In the Azure readiness report for Azure VMware Solution (AVS) assessment, you can see the following suggested tools: 
 - **VMware HCX or Enterprise**: For VMware servers, VMware Hybrid Cloud Extension (HCX) solution is the suggested migration tool to migrate your on-premises workload to your Azure VMware Solution (AVS) private cloud. [Learn More](../azure-vmware/install-vmware-hcx.md).
-- **Unknown**: For servers imported via a CSV file, the default migration tool is unknown. Though, for servers in VMware environment, its is recommended to use the VMware Hybrid Cloud Extension (HCX) solution.
+- **Unknown**: For servers imported via a CSV file, the default migration tool is unknown. Though, for servers in VMware environment, it's recommended to use the VMware Hybrid Cloud Extension (HCX) solution.
 
 
 ## Next steps