AVS update and doc support items

Rashi Joshi · Rashi Joshi · commit 04ca65bdad0e · 2021-10-14T12:14:08.000+05:30
diff --git a/articles/migrate/common-questions-discovery-assessment.md b/articles/migrate/common-questions-discovery-assessment.md
@@ -78,6 +78,16 @@ The confidence rating is calculated for "Performance-based" assessments based on
 - 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. [Learn more](./concepts-assessment-calculation.md#confidence-ratings-performance-based)
 - 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. [Learn more](./concepts-azure-sql-assessment-calculation.md#confidence-ratings)
 
+## Why is my RAM utilization greater than 100%?
+
+By design, in Hyper-V if maximum memory provisioned is less than what is required by the VM, Assessment will show memory utilization to be more than 100%.
+
+## Why can't I see all Azure VM families in the Azure VM assessment properties?
+
+There could be two reasons:
+- You have chosen an Azure region where a particular series is not supported. Azure VM families shown in Azure VM assessment properties are dependent on the availability of the VM series in the chosen Azure location, storage type and Reserved Instance. 
+- The VM series is not support in the assessment and is not in the consideration logic of the assessment. We currently do not support B-series burstable, accelerated and high performance SKU series. We are trying to keep the VM series updated, and the ones mentioned are on our roadmap. 
+
 ## The number of Azure VM or AVS assessments on the Discovery and assessment tool are incorrect
 
  To remediate this, click on the total number of assessments to navigate to all the assessments and recalculate the Azure VM or AVS assessment. The discovery and assessment tool will then show the correct count for that assessment type.
diff --git a/articles/migrate/concepts-assessment-calculation.md b/articles/migrate/concepts-assessment-calculation.md
@@ -203,9 +203,14 @@ After the server is marked as ready for Azure, the assessment makes sizing recom
 If you use performance-based sizing in an Azure VM assessment, the assessment makes sizing recommendations as follows:
 
 - The assessment considers the performance history of the server to identify the VM size and disk type in Azure.
-- If you import servers by using a CSV file, the values you specify are used. This method is especially helpful if you've overallocated the on-premises server, utilization is low, and you want to rightsize the Azure VM to save costs.
+
+> [!NOTE] 
+> If you import serves by using a CSV file, the performance values you specify (CPU utilization, Memory utilization, Disk IOPS and throughput) are used if you choose performance-based sizing. You will not be able to provide performance history and percentile information.
+
+- This method is especially helpful if you've overallocated the on-premises server, utilization is low, and you want to rightsize the Azure VM to save costs.
 - If you don't want to use the performance data, reset the sizing criteria to as-is on-premises, as described in the previous section.
 
+
 #### Calculate storage sizing
 
 For storage sizing in an Azure VM assessment, Azure Migrate tries to map each disk that is attached to the server to an Azure disk. Sizing works as follows:
diff --git a/articles/migrate/concepts-azure-vmware-solution-assessment-calculation.md b/articles/migrate/concepts-azure-vmware-solution-assessment-calculation.md
@@ -114,7 +114,7 @@ Here's what's included in an AVS assessment:
 | - | - |
 | **Target location** | Specifies the AVS private cloud location to which you want to migrate. |
 | **Storage type** | Specifies the storage engine to be used in AVS. AVS currently only supports vSAN as a default storage type but more storage options will be coming as per roadmap. |
-| **Reserved Instances (RIs)** | This property helps you specify Reserved Instances in AVS if purchased and the term of the Reserved Instance. Used to calculate costs. |
+| **Reserved Instances (RIs)** | This property helps you specify Reserved Instances in AVS if purchased and the term of the Reserved Instance. Used to calculate costs. This is currently disabled and defaulted to *No Reserved Instances*. [Azure VMware Solution supports Reserved Instances](https://docs.microsoft.com/azure/azure-vmware/reserved-instance) and assessments will be enabling this property soon.|
 | **Node type** | Specifies the [AVS Node type](../azure-vmware/concepts-private-clouds-clusters.md) used to be used in Azure. The default node type is AV36. More node types might be available in future.  Azure Migrate will recommend a required number of nodes for the VMs to be migrated to AVS. |
 | **FTT Setting, RAID Level** | Specifies the valid combination of Failures to Tolerate and Raid combinations. The selected FTT option combined with RAID level and the on-premises VM disk requirement will determine the total vSAN storage required in AVS. Total available storage after calculations also includes a) space reserved for management objects such as vCenter and b) 25% storage slack required for vSAN operations. |
 | **Sizing criterion** | Sets the criteria to be used to determine memory, cpu and storage requirements for AVS nodes. You can opt for*performance-based* sizing or *as on-premises* without considering the performance history. To simply lift and shift choose as on-premises. To obtain usage based sizing choose performance based. |
@@ -159,6 +159,10 @@ Along with VM properties, the assessment looks at the guest operating system of
 After a server is marked as ready for AVS, AVS Assessment makes node sizing recommendations, which involve identifying the appropriate on-premises VM requirements and finding the total number of AVS nodes required. These recommendations vary, depending on the assessment properties specified.
 
 - If the assessment uses*performance-based sizing*, Azure Migrate considers the performance history of the server to make the appropriate sizing recommendation for AVS. This method is especially helpful if you've over-allocated the on-premises VM, but utilization is low and you want to right-size the VM in AVS to save costs. This method will help you optimize the sizes during migration.
+
+> [!NOTE] 
+>If you import serves by using a CSV file, the performance values you specify (CPU utilization, Memory utilization, Disk IOPS and throughput) are used if you choose performance-based sizing. You will not be able to provide performance history and percentile information.
+
 - If you don't want to consider the performance data for VM sizing and want to take the on-premises servers as-is to AVS, you can set the sizing criteria to* as on-premises*. Then, the assessment will size the VMs based on the on-premises configuration without considering the utilization data.
 
 ### FTT Sizing Parameters
diff --git a/articles/migrate/how-to-create-azure-vmware-solution-assessment.md b/articles/migrate/how-to-create-azure-vmware-solution-assessment.md
@@ -120,11 +120,12 @@ There are two types of sizing criteria that you can use to create Azure VMware S
 An Azure VMware Solution (AVS) assessment describes:
 
 - **Azure VMware Solution (AVS) readiness**: Whether the on-premises servers are suitable for migration to Azure VMware Solution (AVS).
-- **Number of AVS nodes**: Estimated number of AVS nodes required to run the servers.
+- **Number of Azure VMware Solution nodes**: Estimated number of Azure VMware Solution nodes required to run the servers.
 - **Utilization across AVS nodes**: Projected CPU, memory, and storage utilization across all nodes.
     - Utilization includes up front factoring in the following cluster management overheads such as the vCenter Server, NSX Manager (large),
 NSX Edge, if HCX is deployed also the HCX Manager and IX appliance consuming ~ 44vCPU (11 CPU), 75GB of RAM and 722GB of storage before 
 compression and deduplication.
+    - Limiting factor determines the number of hosts/nodes required to accommodate the resources.
 - **Monthly cost estimation**: The estimated monthly costs for all Azure VMware Solution (AVS) nodes running the on-premises VMs.
 
 
@@ -136,7 +137,7 @@ compression and deduplication.
 
     :::image type="content" source="./media/tutorial-assess-vmware-azure-vmware-solution/avs-assessment-summary.png" alt-text="AVS Assessment summary":::
 
-1. Review the assessment summary. You can also edit the assessment properties, or recalculate the assessment.
+1. Review the assessment summary. You can click on  **Sizing assumptions** to understand the assumptions that went in node sizing and resource utilization calculations. You can also edit the assessment properties, or recalculate the assessment.
 
 ### Review Azure VMware Solution (AVS) readiness
 
@@ -173,7 +174,7 @@ This view shows the estimated cost of running servers in Azure VMware Solution (
 
 When you run performance-based assessments, a confidence rating is assigned to the assessment.
 
-![Confidence rating](./media/how-to-create-assessment/confidence-rating.png)
+    :::image type="content" source="./media/tutorial-assess-vmware-azure-vmware-solution/confidence-rating.png" alt-text="Confidence rating":::
 
 - A rating from 1-star (lowest) to 5-star (highest) is awarded.
 - The confidence rating helps you estimate the reliability of the size recommendations provided by the assessment.
diff --git a/articles/migrate/media/tutorial-assess-vmware-azure-vmware-solution/avs-assessment-summary.png b/articles/migrate/media/tutorial-assess-vmware-azure-vmware-solution/avs-assessment-summary.png
diff --git a/articles/migrate/troubleshoot-assessment.md b/articles/migrate/troubleshoot-assessment.md
@@ -138,6 +138,10 @@ The confidence rating is calculated for **Performance-based** assessments based
 - For Azure VM and Azure VMware Solution assessments, few servers were created after discovery had started. For example, say you're creating an assessment for the performance history of the past month, but a 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. [Learn more](./concepts-assessment-calculation.md#confidence-ratings-performance-based).
 - For Azure SQL assessments, few SQL instances or databases were created after discovery had started. For example, say you're creating an assessment for the performance history of the past month, but a 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. [Learn more](./concepts-azure-sql-assessment-calculation.md#confidence-ratings).
 
+## Why is my RAM utilization greater than 100%?
+
+By design, in Hyper-V if maximum memory provisioned is less than what is required by the VM, Assessment will show memory utilization to be more than 100%.
+
 ## Is the operating system license included in an Azure VM assessment?
 
 An Azure VM assessment currently considers the operating system license cost only for Windows servers. License costs for Linux servers aren't currently considered.
diff --git a/articles/migrate/tutorial-assess-vmware-azure-vmware-solution.md b/articles/migrate/tutorial-assess-vmware-azure-vmware-solution.md
@@ -123,13 +123,14 @@ Run an assessment as follows:
 
 An AVS assessment describes:
 
-- AVS readiness: Whether the on-premises servers are suitable for migration to Azure VMware Solution (AVS).
-- Number of AVS nodes: Estimated number of AVS nodes required to run the servers.
-- Utilization across AVS nodes: Projected CPU, memory, and storage utilization across all nodes.
-    - Utilization includes upfront factoring in the following cluster management overheads such as the vCenter Server, NSX Manager (large),
+- **Azure VMware Solution (AVS) readiness**: Whether the on-premises servers are suitable for migration to Azure VMware Solution (AVS).
+- **Number of Azure VMware Solution nodes**: Estimated number of Azure VMware Solution nodes required to run the servers.
+- **Utilization across AVS nodes**: Projected CPU, memory, and storage utilization across all nodes.
+    - Utilization includes up front factoring in the following cluster management overheads such as the vCenter Server, NSX Manager (large),
 NSX Edge, if HCX is deployed also the HCX Manager and IX appliance consuming ~ 44vCPU (11 CPU), 75GB of RAM and 722GB of storage before 
-compression and deduplication. 
-- Monthly cost estimation: The estimated monthly costs for all Azure VMware Solution (AVS) nodes running the on-premises servers.
+compression and deduplication.
+    - Limiting factor determines the number of hosts/nodes required to accommodate the resources.
+- **Monthly cost estimation**: The estimated monthly costs for all Azure VMware Solution (AVS) nodes running the on-premises VMs.
 
 ## View an assessment
 
@@ -141,7 +142,7 @@ To view an assessment:
 
     :::image type="content" source="./media/tutorial-assess-vmware-azure-vmware-solution/avs-assessment-summary.png" alt-text="AVS Assessment summary":::
 
-1. Review the assessment summary. You can also edit the assessment properties, or recalculate the assessment.
+1. Review the assessment summary. You can click on  **Sizing assumptions** to understand the assumptions that went in node sizing and resource utilization calculations. You can also edit the assessment properties, or recalculate the assessment.
  
 
 ### Review readiness
@@ -177,7 +178,8 @@ The assessment summary shows the estimated compute and storage cost of running s
 
 Server Assessment assigns a confidence rating to performance-based assessments. Rating is from one star (lowest) to five stars (highest).
 
-![Confidence rating](./media/tutorial-assess-vmware-azure-vmware-solution/confidence-rating.png)
+    :::image type="content" source="./media/tutorial-assess-vmware-azure-vmware-solution/confidence-rating.png" alt-text="Confidence rating":::
+
 
 The confidence rating helps you estimate the reliability of size recommendations in the assessment. The rating is based on the availability of data points needed to compute the assessment.
 
diff --git a/articles/migrate/tutorial-discover-import.md b/articles/migrate/tutorial-discover-import.md
@@ -192,6 +192,12 @@ Operating system names provided in the CSV must contain and match. If they don't
 --- | --- | --- | ---
 Asianux 3<br/>Asianux 4<br/>Asianux 5<br/>CentOS<br/>CentOS 4/5<br/>CoreOS Linux<br/>Debian GNU/Linux 4<br/>Debian GNU/Linux 5<br/>Debian GNU/Linux 6<br/>Debian GNU/Linux 7<br/>Debian GNU/Linux 8<br/>FreeBSD | IBM OS/2<br/>macOS X 10<br/>MS-DOS<br/>Novell NetWare 5<br/>Novell NetWare 6<br/>Oracle Linux<br/>Oracle Linux 4/5<br/>Oracle Solaris 10<br/>Oracle Solaris 11<br/>Red Hat Enterprise Linux 2<br/>Red Hat Enterprise Linux 3<br/>Red Hat Enterprise Linux 4<br/>Red Hat Enterprise Linux 5<br/>Red Hat Enterprise Linux 6<br/>Red Hat Enterprise Linux 7<br/>Red Hat Fedora | SCO OpenServer 5<br/>SCO OpenServer 6<br/>SCO UnixWare 7<br/> Serenity Systems eComStation 1<br/>Serenity Systems eComStation <br/>Sun Microsystems Solaris 8<br/>Sun Microsystems Solaris 9<br/><br/>SUSE Linux Enterprise 10<br/>SUSE Linux Enterprise 11<br/>SUSE Linux Enterprise 12<br/>SUSE Linux Enterprise 8/9<br/>SUSE Linux Enterprise 11<br/>SUSE openSUSE | Ubuntu Linux<br/>VMware ESXi 4<br/>VMware ESXi 5<br/>VMware ESXi 6<br/>Windows 10<br/>Windows 2000<br/>Windows 3<br/>Windows 7<br/>Windows 8<br/>Windows 95<br/>Windows 98<br/>Windows NT<br/>Windows Server (R) 2008<br/>Windows Server 2003<br/>Windows Server 2008<br/>Windows Server 2008 R2<br/>Windows Server 2012<br/>Windows Server 2012 R2<br/>Windows Server 2016<br/>Windows Server 2019<br/>Windows Server Threshold<br/>Windows Vista<br/>Windows Web Server 2008 R2<br/>Windows XP Professional
 
+## Assessment considerations
+
+- If you import serves by using a CSV file, the performance values you specify (CPU utilization, Memory utilization, Disk IOPS and throughput) are used if you choose performance-based sizing. You will not be able to provide performance history and percentile information. 
+- To get an accurate OS suitability/readiness in Azure VM and Azure VMware Solution assessment, please enter the Operating system version and architecture in the respective columns.
+
+
 ## Next steps
 
 In this tutorial, you:
