adding new assess tutorials

Author: rayne-wiselman

articles/migrate/media/tutorial-assess-aws/assess-group.png

@@ -0,0 +1,183 @@
+---
+title: Assess AWS instances for migration to Azure with Azure Migrate Server Assessment
+description: Describes how to assess AWS instances for migration to Azure using Azure Migrate Server Assessment.
+ms.topic: tutorial
+ms.date: 09/01/2020
+#Customer intent: As a server admin, I want to assess my AWS instances in preparation for migration to Azure.
+---
+
+# Tutorial: Assess AWS instances for migration to Azure
+
+As part of your migration journey to Azure, you assess your on-premises workloads to measure cloud readiness, identify risks, and estimate costs and complexity.
+
+This article shows you how to assess Amazon Web Services (AWS) instances for migration to Azure, using the Azure Migrate: Server Assessment tool.
+
+In this tutorial, you learn how to:
+> [!div class="checklist"]
+- Run an assessment based on machine metadata and configuration information.
+- Run an assessment based on performance data.
+
+> [!NOTE]
+> Tutorials show the quickest path for trying out a scenario, and use default options where possible. 
+
+If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/pricing/free-trial/) before you begin.
+
+
+## Prerequisites
+
+- Before you follow the steps in this tutorial, complete the first tutorial in this series to [discover your on-premises inventory](tutorial-discover-aws.md). 
+- Make sure AWS instances aren't running Windows Server 2003, or SUSE Linux. Assessment isn't supported for these machines.
+
+
+## Decide which assessment to run
+
+
+Decide whether you want to run an assessment using sizing criteria based on machine configuration data/metadata that's collected as-is on-premises, or on dynamic performance data.
+
+**Assessment** | **Details** | **Recommendation**
+--- | --- | ---
+**As-is on-premises** | Assess based on machine configuration data/metadata.  | Recommended Azure VM size is based on the on-premises VM size.<br/><br> The recommended Azure disk type is based on what you select in the storage type setting in the assessment.
+**Performance-based** | Assess based on collected dynamic performance data. | Recommended Azure VM size is based on CPU and memory utilization data.<br/><br/> The recommended disk type is based on the IOPS and throughput of the on-premises disks.
+
+## Run an assessment
+
+Run an assessment as follows:
+
+1. On the **Servers** page > **Windows and Linux servers**, click **Assess and migrate servers**.
+
+   ![Location of Assess and migrate servers button](./media/tutorial-assess-aws/assess.png)
+
+2. In **Azure Migrate: Server Assessment, click **Assess**.
+
+    ![Location of the Assess button](./media/tutorial-assess-aws/assess-servers.png)
+
+3. In **Assess servers** > **Assessment type**, select **Azure VM**.
+4. In **Discovery source**:
+
+    - If you discovered machines using the appliance, select **Machines discovered from Azure Migrate appliance**.
+    - If you discovered machines using an imported CSV file, select **Imported machines**. 
+5. Specify a name for the assessment. 
+6. Click **View all** to review the assessment properties.
+
+    ![Location of the View all button to review assessment properties](./media/tutorial-assess-aws/assessment-name.png)
+
+7. In **Assessment properties** > **Target Properties**:
+    - In **Target location**, specify the Azure region to which you want to migrate.
+        - Size and cost recommendations are based on the location that you specify.
+        - In Azure Government, you can target assessments in [these regions](migrate-support-matrix.md#supported-geographies-azure-government)
+    - In **Storage type**,
+        - If you want to use performance-based data in the assessment, select **Automatic** for Azure Migrate to recommend a storage type, based on disk IOPS and throughput.
+        - Alternatively, select the storage type you want to use for VM when you migrate it.
+    - In **Reserved Instances**, specify whether you want to use reserve instances for the VM when you migrate it.
+        - If you select to use a reserved instance, you can't specify  '**Discount (%)**, or **VM uptime**. 
+        - [Learn more](https://aka.ms/azurereservedinstances).
+8. In **VM Size**:
+ 
+    - In **Sizing criterion**, select if you want to base the assessment on machine configuration data/metadata, or on performance-based data. If you use performance data:
+        - In **Performance history**, indicate the data duration on which you want to base the assessment
+        - In **Percentile utilization**, specify the percentile value you want to use for the performance sample. 
+    - In **VM Series**, specify the Azure VM series you want to consider.
+        - If you're using performance-based assessment, Azure Migrate suggests a value for you.
+        - Tweak settings as needed. For example, if you don't have a production environment that needs A-series VMs in Azure, you can exclude A-series from the list of series.
+    - In **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. For example, if you use a comfort factor of two:
+        **Details** | **Utilization** | **Add comfort factor (2.0)**
+        Read IOPS | 100 | 200
+        Write IOPS | 100 | 200
+        Read throughput | 100 Mbps | 200 Mbps
+        Write throughput | 100 Mbps | 200 Mbps
+   
+9. In **Pricing**:
+    - In **Offer**, specify the [Azure offer](https://azure.microsoft.com/support/legal/offer-details/) if you're enrolled. Server Assessment estimates the cost for that offer.
+    - In **Currency**, select the billing currency for your account.
+    - In **Discount (%)**, add any subscription-specific discounts you receive on top of the Azure offer. The default setting is 0%.
+    - In **VM Uptime**, specify the duration (days per month/hour per day) that VMs will run.
+        - This is useful for Azure VMs that won't run continuously.
+        - Cost estimates are based on the duration specified.
+        - Default is 31 days per month/24 hours per day.
+
+    - In **EA Subscription**, specify whether to take an Enterprise Agreement (EA) subscription discount into account for cost estimation. 
+    - In **Azure Hybrid Benefit**, specify whether you already have a Windows Server license. If you do and they're covered with active Software Assurance of Windows Server Subscriptions, you can apply for the [Azure Hybrid Benefit](https://azure.microsoft.com/pricing/hybrid-use-benefit/) when you bring licenses to Azure.
+
+10. Click **Save** if you make changes.
+
+    ![Assessment properties](./media/tutorial-assess-aws/assessment-properties.png)
+
+11. In **Assess Servers**, click **Next**.
+12. In **Select machines to assess**, select **Create New**, and specify a group name. 
+13. Select the appliance, and select the VMs you want to add to the group. Then click **Next**.
+14. In **Review + create assessment, review the assessment details, and click **Create Assessment** to create the group and run the assessment.
+
+
+    > [!NOTE]
+    > For performance-based assessments, we recommend that you wait at least a day after starting discovery before you create an assessment. This provides time to collect performance data with higher confidence. Ideally, after you start discovery, wait for the performance duration you specify (day/week/month) for a high-confidence rating.
+
+## Review an assessment
+
+An assessment describes:
+
+- **Azure readiness**: Whether VMs are suitable for migration to Azure.
+- **Monthly cost estimation**: The estimated monthly compute and storage costs for running the VMs in Azure.
+- **Monthly storage cost estimation**: Estimated costs for disk storage after migration.
+
+To view an assessment:
+
+1. In **Servers** > **Azure Migrate: Server Assessment**, click the number next to **Assessments**.
+2. In **Assessments**, select an assessment to open it.
+
+    ![Assessment summary](./media/tutorial-assess-aws/assessment-summary.png)
+
+3. Review the assessment summary. You can also edit the assessment properties, or recalculate the assessment.
+ 
+ 
+### Review readiness
+
+1. Click **Azure readiness**.
+2. In **Azure readiness**, review the VM status:
+    - **Ready for Azure**: Used when Azure Migrate recommends a VM size and cost estimates, for VMs in the assessment.
+    - **Ready with conditions**: Shows issues and suggested remediation.
+    - **Not ready for Azure**: Shows issues and suggested remediation.
+    - **Readiness unknown**: Used when Azure Migrate can't assess readiness, because of data availability issues.
+
+3. Select an **Azure readiness** status. You can view VM readiness details. You can also drill down to see VM details, including compute, storage, and network settings.
+
+### Review cost estimates
+
+The assessment summary shows the estimated compute and storage cost of running VMs in Azure. 
+
+1. Review the monthly total costs. Costs are aggregated for all VMs in the assessed group.
+
+    - Cost estimates are based on the size recommendations for a machine, its disks, and its properties.
+    - Estimated monthly costs for compute and storage are shown.
+    - The cost estimation is for running the on-premises VMs on Azure VMs. The estimation doesn't consider PaaS or SaaS costs.
+
+2. Review monthly storage costs. The view shows the aggregated storage costs for the assessed group, split over different types of storage disks. 
+3. You can drill down to see cost details for specific VMs.
+
+### Review confidence rating
+
+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-aws/confidence-rating.png)
+
+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.
+
+> [!NOTE]
+> Confidence ratings aren't assigned if you create an assessment based on a CSV file.
+
+
+Confidence ratings are as follows.
+
+**Data point availability** | **Confidence rating**
+--- | ---
+0%-20% | 1 star
+21%-40% | 2 stars
+41%-60% | 3 stars
+61%-80% | 4 stars
+81%-100% | 5 stars
+
+[Learn more](concepts-assessment-calculation.md#confidence-ratings-performance-based) about confidence ratings.
+
+## Next steps
+
+- Find machine dependencies using [dependency mapping](concepts-dependency-visualization.md).
+- Set up [agent-based](how-to-create-group-machine-dependencies.md) dependency mapping.

articles/migrate/media/tutorial-assess-aws/assess-migrate.png

@@ -0,0 +1,188 @@
+---
+title: Assess VMware VMs for migration to Azure VMs with Server Assessment in Azure Migrate
+description: Learn how to assess VMware VMs for migration to Azure VMs with Server Assessment.
+ms.topic: how-to
+ms.date: 09/01/2020
+#Customer intent: As a VMware VM admin, I want to assess my VMware VMs in preparation for migration to Azure.
+---
+
+# Tutorial: Assess VMware VMs for migration to Azure VMs
+
+As part of your migration journey to Azure, you assess your on-premises workloads to measure cloud readiness, identify risks, and estimate costs and complexity.
+
+This article shows you how to assess discovered VMware virtual machines (VMs) in preparation for migration to Azure VMs, using the Azure Migrate: Server Assessment tool.
+
+
+In this tutorial, you learn how to:
+> [!div class="checklist"]
+- Run an assessment based on machine metadata and configuration information.
+- Run an assessment based on performance data.
+
+> [!NOTE]
+> Tutorials show the quickest path for trying out a scenario, and use default options where possible. 
+
+If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/pricing/free-trial/) before you begin.
+
+
+## Prerequisites
+
+Before you follow this tutorial to assess your machines for migration to Azure VMs, make sure you've discovered the machines you want to assess:
+
+- To discover machines using the Azure Migrate appliance, [follow this tutorial](tutorial-discover-vmware.md). 
+- To discover machines using an imported CSV file, [follow this tutorial](tutorial-discover-import.md).
+
+
+## Decide which assessment to run
+
+
+Decide whether you want to run an assessment using sizing criteria based on machine configuration data/metadata that's collected as-is on-premises, or on dynamic performance data.
+
+**Assessment** | **Details** | **Recommendation**
+--- | --- | ---
+**As-is on-premises** | Assess based on machine configuration data/metadata.  | Recommended Azure VM size is based on the on-premises VM size.<br/><br> The recommended Azure disk type is based on what you select in the storage type setting in the assessment.
+**Performance-based** | Assess based on collected dynamic performance data. | Recommended Azure VM size is based on CPU and memory utilization data.<br/><br/> The recommended disk type is based on the IOPS and throughput of the on-premises disks.
+
+
+## Run an assessment
+
+Run an assessment as follows:
+
+1. On the **Servers** page > **Windows and Linux servers**, click **Assess and migrate servers**.
+
+   ![Location of Assess and migrate servers button](./media/tutorial-assess-vmware-azure-vm/assess.png)
+
+2. In **Azure Migrate: Server Assessment**, click **Assess**.
+
+    ![Location of the Assess button](./media/tutorial-assess-vmware-azure-vm/assess-servers.png)
+
+3. In **Assess servers** > **Assessment type**, select **Azure VM**.
+4. In **Discovery source**:
+
+    - If you discovered machines using the appliance, select **Machines discovered from Azure Migrate appliance**.
+    - If you discovered machines using an imported CSV file, select **Imported machines**. 
+    
+1. Specify a name for the assessment. 
+1. Click **View all** to review the assessment properties.
+
+    ![Location of the View all button to review assessment properties](./media/tutorial-assess-vmware-azure-vm/assessment-name.png)
+
+1. In **Assessment properties** > **Target Properties**:
+    - In **Target location**, specify the Azure region to which you want to migrate.
+        - Size and cost recommendations are based on the location that you specify.
+        - In Azure Government, you can target assessments in [these regions](migrate-support-matrix.md#supported-geographies-azure-government)
+    - In **Storage type**,
+        - If you want to use performance-based data in the assessment, select **Automatic** for Azure Migrate to recommend a storage type, based on disk IOPS and throughput.
+        - Alternatively, select the storage type you want to use for VM when you migrate it.
+    - In **Reserved Instances**, specify whether you want to use reserve instances for the VM when you migrate it.
+        - If you select to use a reserved instance, you can't specify  '**Discount (%)**, or **VM uptime**. 
+        - [Learn more](https://aka.ms/azurereservedinstances).
+ 7. In **VM Size**:
+ 
+    - In **Sizing criterion**, select if you want to base the assessment on machine configuration data/metadata, or on performance-based data. If you use performance data:
+        - In **Performance history**, indicate the data duration on which you want to base the assessment
+        - In **Percentile utilization**, specify the percentile value you want to use for the performance sample. 
+    - In **VM Series**, specify the Azure VM series you want to consider.
+        - If you're using performance-based assessment, Azure Migrate suggests a value for you.
+        - Tweak settings as needed. For example, if you don't have a production environment that needs A-series VMs in Azure, you can exclude A-series from the list of series.
+    - In **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. For example, if you use a comfort factor of two:
+        **Component** | **Effective utilization** | **Add comfort factor (2.0)**
+        Cores | 2 | 4
+        Memory | 8 GB | 16 GB     
+   
+8. In **Pricing**:
+    - In **Offer**, specify the [Azure offer](https://azure.microsoft.com/support/legal/offer-details/) if you're enrolled. Server Assessment estimates the cost for that offer.
+    - In **Currency**, select the billing currency for your account.
+    - In **Discount (%)**, add any subscription-specific discounts you receive on top of the Azure offer. The default setting is 0%.
+    - In **VM Uptime**, specify the duration (days per month/hour per day) that VMs will run.
+        - This is useful for Azure VMs that won't run continuously.
+        - Cost estimates are based on the duration specified.
+        - Default is 31 days per month/24 hours per day.
+
+    - In **EA Subscription**, specify whether to take an Enterprise Agreement (EA) subscription discount into account for cost estimation. 
+    - In **Azure Hybrid Benefit**, specify whether you already have a Windows Server license. If you do and they're covered with active Software Assurance of Windows Server Subscriptions, you can apply for the [Azure Hybrid Benefit](https://azure.microsoft.com/pricing/hybrid-use-benefit/) when you bring licenses to Azure.
+
+9. Click **Save** if you make changes.
+
+    ![Assessment properties](./media/tutorial-assess-vmware-azure-vm/assessment-properties.png)
+
+10. In **Assess Servers**, click **Next**.
+11. In **Select machines to assess**, select **Create New**, and specify a group name. 
+12. Select the appliance, and select the VMs you want to add to the group. Then click **Next**.
+
+     ![Add VMs to a group](./media/tutorial-assess-vmware-azure-vm/assess-group.png)
+
+13. In **Review + create assessment, review the assessment details, and click **Create Assessment** to create the group and run the assessment.
+
+
+    > [!NOTE]
+    > For performance-based assessments, we recommend that you wait at least a day after starting discovery before you create an assessment. This provides time to collect performance data with higher confidence. Ideally, after you start discovery, wait for the performance duration you specify (day/week/month) for a high-confidence rating.
+
+## Review an assessment
+
+An assessment describes:
+
+- **Azure readiness**: Whether VMs are suitable for migration to Azure.
+- **Monthly cost estimation**: The estimated monthly compute and storage costs for running the VMs in Azure.
+- **Monthly storage cost estimation**: Estimated costs for disk storage after migration.
+
+To view an assessment:
+
+1. In **Servers** > **Azure Migrate: Server Assessment**, click the number next to **Assessments**.
+2. In **Assessments**, select an assessment to open it.
+
+    ![Assessment summary](./media/tutorial-assess-vmware-azure-vm/assessment-summary.png)
+
+3. Review the assessment summary. You can also edit the assessment properties, or recalculate the assessment.
+ 
+ 
+### Review readiness
+
+1. Click **Azure readiness**.
+2. In **Azure readiness**, review the VM status:
+    - **Ready for Azure**: Used when Azure Migrate recommends a VM size and cost estimates, for VMs in the assessment.
+    - **Ready with conditions**: Shows issues and suggested remediation.
+    - **Not ready for Azure**: Shows issues and suggested remediation.
+    - **Readiness unknown**: Used when Azure Migrate can't assess readiness, because of data availability issues.
+
+3. Select an **Azure readiness** status. You can view VM readiness details. You can also drill down to see VM details, including compute, storage, and network settings.
+
+### Review cost estimates
+
+The assessment summary shows the estimated compute and storage cost of running VMs in Azure. 
+
+1. Review the monthly total costs. Costs are aggregated for all VMs in the assessed group.
+
+    - Cost estimates are based on the size recommendations for a machine, its disks, and its properties.
+    - Estimated monthly costs for compute and storage are shown.
+    - The cost estimation is for running the on-premises VMs on Azure VMs. The estimation doesn't consider PaaS or SaaS costs.
+
+2. Review monthly storage costs. The view shows the aggregated storage costs for the assessed group, split over different types of storage disks. 
+3. You can drill down to see cost details for specific VMs.
+
+### Review confidence rating
+
+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-vm/confidence-rating.png)
+
+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.
+
+> [!NOTE]
+> Confidence ratings aren't assigned if you create an assessment based on a CSV file.
+
+Confidence ratings are as follows.
+
+**Data point availability** | **Confidence rating**
+--- | ---
+0%-20% | 1 star
+21%-40% | 2 stars
+41%-60% | 3 stars
+61%-80% | 4 stars
+81%-100% | 5 stars
+
+[Learn more](concepts-assessment-calculation.md#confidence-ratings-performance-based) about confidence ratings.
+
+## Next steps
+
+- Find machine dependencies using [dependency mapping](concepts-dependency-visualization.md).
+- Set up [agentless](how-to-create-group-machine-dependencies-agentless.md) or [agent-based](how-to-create-group-machine-dependencies.md) dependency mapping.

articles/migrate/media/tutorial-assess-aws/assess-servers.png

@@ -0,0 +1,185 @@
+---
+title: Assess VMware VMs for migration to Azure VMware Solution (AVS) with Azure Migrate
+description: Learn how to assess VMware VMs for migration to Azure VMs with Server Assessment.
+ms.topic: how-to
+ms.date: 09/01/2020
+#Customer intent: As a VMware VM admin, I want to assess my VMware VMs in preparation for migration to Azure VMware Solution (AVS)
+---
+
+# Tutorial: Assess VMware VMs for migration to AVS
+
+As part of your migration journey to Azure, you assess your on-premises workloads to measure cloud readiness, identify risks, and estimate costs and complexity.
+
+This article shows you how to assess discovered VMware virtual machines (VMs) for migration to Azure VMware Solution (AVS), using the Azure Migrate: Server Assessment tool. AVS is a managed service that allows you to run the VMware platform in Azure.
+
+In this tutorial, you learn how to:
+> [!div class="checklist"]
+- Run an assessment.
+- Analyze an assessment.
+
+> [!NOTE]
+> Tutorials show the quickest path for trying out a scenario, and use default options where possible. 
+
+If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/pricing/free-trial/) before you begin.
+
+
+
+## Prerequisites
+
+Before you follow this tutorial to assess your machines for migration to AVS, make sure you've discovered the machines you want to assess:
+
+- To discover machines using the Azure Migrate appliance, [follow this tutorial](tutorial-discover-vmware.md). 
+- To discover machines using an imported CSV file, [follow this tutorial](tutorial-discover-import.md).
+
+
+## Decide which assessment to run
+
+
+Decide whether you want to run an assessment based on static machine metadata that's collected as-is on-premises, or on dynamic performance data.
+
+**Assessment** | **Details** | **Recommendation**
+--- | --- | ---
+**As-is on-premises** | Assess based on static machine data.  | Recommended node size in AVS is based on the on-premises VM size, along with the settings you specify in the assessment for the node type, storage type, and failure-to-tolerate setting.
+**Performance-based** | Assess based on collected dynamic performance data. | Recommended node size in AVS is based on CPU and memory utilization data, along with the settings you specify in the assessment for the node type, storage type, and failure-to-tolerate setting.
+
+## Run an assessment
+
+Run an assessment as follows:
+
+1. On the **Servers** page > **Windows and Linux servers**, click **Assess and migrate servers**.
+
+   ![Location of Assess and migrate servers button](./media/tutorial-assess-vmware-azure-vmware-solution/assess.png)
+
+2. In **Azure Migrate: Server Assessment**, click **Assess**.
+
+3. In **Assess servers** > **Assessment type**, select **Azure VMware Solution (AVS) (Preview)**.
+4. In **Discovery source**:
+
+    - If you discovered machines using the appliance, select **Machines discovered from Azure Migrate appliance**.
+    - If you discovered machines using an imported CSV file, select **Imported machines**. 
+    
+5. Specify a name for the assessment. 
+6. Click **View all** to review the assessment properties.
+
+    ![Page for selecting the assessment settings](./media/tutorial-assess-vmware-azure-vmware-solution/assess-servers.png)
+
+
+7. 1n **Assessment properties** > **Target Properties**:
+
+    - In **Target location**, specify the Azure region to which you want to migrate.
+       - Size and cost recommendations are based on the location that you specify.
+       - You can currently assess for three regions (East US, West US, West Europe)
+   - In **Storage type**, leave **vSAN**. This is the default storage type for an AVS private cloud.
+   - **Reserved Instances** aren't currently supported for AVS nodes.
+7. In **VM Size**:
+    - In **Node type**, select a node type based on the workloads running on the on-premises VMs.
+        - Azure Migrate recommends the node of nodes needed to migrate the VMs to AVS.
+        - The default node type is AV36.
+    - **FTT setting, RAID level**, select the Failure to Tolerate and RAID combination.  The selected FTT option, combined with the on-premises VM disk requirement, determines the total vSAN storage required in AVS.
+    - In **CPU Oversubscription**, specify the ratio of virtual cores associated with one physical core in the AVS node. Oversubscription of greater than 4:1 might cause performance degradation, but can be used for web server type workloads.
+
+8. In **Node Size**: 
+    - In **Sizing criterion**, select if you want to base the assessment on static metadata, or on performance-based data. If you use performance data:
+        - In **Performance history**, indicate the data duration on which you want to base the assessment
+        - In **Percentile utilization**, specify the percentile value you want to use for the performance sample. 
+    - In **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. For example, if you use a comfort factor of two:
+    
+        **Details** | **Utilization** | **Add comfort factor (2.0)**
+        --- | --- | ---
+        Read IOPS | 100 | 200
+        Write IOPS | 100 | 200
+        Read throughput | 100 Mbps | 200 Mbps
+        Write throughput | 100 Mbps | 200 Mbps
+
+9. In **Pricing**:
+    - In **Offer**, [Azure offer](https://azure.microsoft.com/support/legal/offer-details/) you're enrolled in is displayed Server Assessment estimates the cost for that offer.
+    - In **Currency**, select the billing currency for your account.
+    - In **Discount (%)**, add any subscription-specific discounts you receive on top of the Azure offer. The default setting is 0%.
+
+10. Click **Save** if you make changes.
+
+    ![Assessment properties](./media/tutorial-assess-vmware-azure-vmware-solution/view-all.png)
+
+1. In **Assess Servers**, click **Next**.
+1. In **Assess Servers** > **Select machines to assess**, to create a new group of servers for assessment, select **Create New**, and specify a group name. 
+1. Select the appliance, and select the VMs you want to add to the group. Then click **Next**.
+
+     ![Add VMs to a group](./media/tutorial-assess-vmware-azure-vmware-solution/assess-group.png)
+
+13. In **Review + create assessment**, review the assessment details, and click **Create Assessment** to create the group and run the assessment.
+
+    ![Create an assessment](./media/tutorial-assess-vmware-azure-vmware-solution/create-assessment.png)
+
+    > [!NOTE]
+    > For performance-based assessments, we recommend that you wait at least a day after starting discovery before you create an assessment. This provides time to collect performance data with higher confidence. Ideally, after you start discovery, wait for the performance duration you specify (day/week/month) for a high-confidence rating.
+
+## Review an assessment
+
+An assessment describes:
+
+- **Ready for AVS**: The machine can be migrated as-is to Azure AVS, without any changes. The machine will start in AVS, with full AVS support.
+- **Ready with conditions**: The machine might have compatibility issues with the current vSphere version. It might need VMware tools installed, or other settings, before it has full functionality in AVS.
+- **Not ready for AVS**: The VM won't start in AVS. For example, if an on-premises VMware VM has an external device (like a CD-RON) attached to it and you're using VMware VMotion, the VMotion operation fails.
+- **Readiness unknown**: Azure Migrate couldn't determine machine readiness, due to insufficient metadata collected from the on-premises environment.
+
+To view an assessment:
+
+1. In **Servers** > **Azure Migrate: Server Assessment**, click the number next to **Assessments**.
+2. In **Assessments**, select an assessment to open it.
+
+    ![Assessment summary](./media/tutorial-assess-vmware-azure-vm/assessment-summary.png)
+
+3. Review the assessment summary. You can also edit the assessment properties, or recalculate the assessment.
+ 
+ 
+### Review readiness
+
+1. Click **Azure readiness**.
+2. In **Azure readiness**, review the VM status:
+    - **Ready for Azure**: Used when Azure Migrate recommends a VM size and cost estimates, for VMs in the assessment.
+    - **Ready with conditions**: Shows issues and suggested remediation.
+    - **Not ready for Azure**: Shows issues and suggested remediation.
+    - **Readiness unknown**: Used when Azure Migrate can't assess readiness, because of data availability issues.
+
+3. Select an **Azure readiness** status. You can view VM readiness details. You can also drill down to see VM details, including compute, storage, and network settings.
+
+### Review cost estimates
+
+The assessment summary shows the estimated compute and storage cost of running VMs in Azure. 
+
+1. Review the monthly total costs. Costs are aggregated for all VMs in the assessed group.
+
+    - Cost estimates are based on the size recommendations for a machine, its disks, and its properties.
+    - Estimated monthly costs for compute and storage are shown.
+    - The cost estimation is for running the on-premises VMs on Azure VMs. The estimation doesn't consider PaaS or SaaS costs.
+
+2. Review monthly storage costs. The view shows the aggregated storage costs for the assessed group, split over different types of storage disks. 
+3. You can drill down to see cost details for specific VMs.
+
+### Review confidence rating
+
+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)
+
+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.
+
+> [!NOTE]
+> Confidence ratings aren't assigned if you create an assessment based on a CSV file.
+
+Confidence ratings are as follows.
+
+**Data point availability** | **Confidence rating**
+--- | ---
+0%-20% | 1 star
+21%-40% | 2 stars
+41%-60% | 3 stars
+61%-80% | 4 stars
+81%-100% | 5 stars
+
+[Learn more](concepts-assessment-calculation.md#confidence-ratings-performance-based) about confidence ratings.
+
+## Next steps
+
+- Find machine dependencies using [dependency mapping](concepts-dependency-visualization.md).
+- Set up [agentless](how-to-create-group-machine-dependencies-agentless.md) or [agent-based](how-to-create-group-machine-dependencies.md) dependency mapping.

articles/migrate/media/tutorial-assess-aws/assess.png

@@ -61,30 +61,19 @@ Set up a new Azure Migrate project as follows:
 
 Azure Migrate:Server Assessment uses a lightweight Azure Migrate appliance. The appliance performs VM discovery and sends VM metadata and performance data to Azure Migrate. The appliance can be set up in a number of ways.
 
-- Set up on a VMware VM using a downloaded OVA template. **This is the method used in this tutorial.**
+- Set up on a VMware VM using a downloaded OVA template. This is the method used in this tutorial.
 - Set up on a VMware VM or physical machine with a PowerShell installer script. [This method](deploy-appliance-script.md) should be used if you can't set up a VM using an OVA template, or if you're in Azure Government.
 
 After creating the appliance, you check that it can connect to Azure Migrate:Server Assessment, configure it for the first time, and register it with the Azure Migrate project.
 
 
-### Generate the Azure Migrate project key
+### Download the OVA template
 
 1. In **Migration Goals** > **Servers** > **Azure Migrate: Server Assessment**, select **Discover**.
 2. In **Discover machines** > **Are your machines virtualized?**, select **Yes, with VMware vSphere hypervisor**.
-3. In **1:Generate Azure Migrate project key**, provide a name for the Azure Migrate appliance that you will set up for discovery of VMware VMs.The name should be alphanumeric with 14 characters or fewer.
-1. Click on **Generate key** to start the creation of the required Azure resources. Please do not close the Discover machines page during the creation of resources.
-1. After the successful creation of the Azure resources, an **Azure Migrate project key** is generated.
-1. Copy the key as you will need it to complete the registration of the appliance during its configuration.
-
-### Download the OVA template
-In **2: Download Azure Migrate appliance**, select the .OVA file and click on **Download**. 
-
-
-   ![Selections for Discover machines](./media/tutorial-assess-vmware/servers-discover.png)
-
-
-   ![Selections for Generate Key](./media/tutorial-assess-vmware/generate-key-vmware.png)
+3. Select **Download** to download the OVA template file.
 
+   ![Selections for downloading an OVA file](./media/tutorial-assess-vmware/download-ova.png)
 
 ### Verify security
 
@@ -103,13 +92,13 @@ Check that the OVA file is secure, before you deploy it:
 
         **Algorithm** | **Download** | **SHA256**
         --- | --- | ---
-        VMware (11.6 GB) | [Latest version](https://go.microsoft.com/fwlink/?linkid=2140333) | e9c9a1fe4f3ebae81008328e8f3a7933d78ff835ecd871d1b17f367621ce3c74
+        VMware (10.9 GB) | [Latest version](https://aka.ms/migrate/appliance/vmware) | cacbdaef927fe5477fa4e1f494fcb7203cbd6b6ce7402b79f234bc0fe69663dd
 
     - For Azure Government:
 
         **Algorithm** | **Download** | **SHA256**
         --- | --- | ---
-        VMware (85 MB) | [Latest version](https://go.microsoft.com/fwlink/?linkid=2140337) | 47179f47eba2842337bbe533c424dd1da56baccdcf68b1d87b71a5a4280108c2
+        VMware (63.1 MB) | [Latest version](https://go.microsoft.com/fwlink/?linkid=2120300&clcid=0x409 ) | 3d5822038646b81f458d89d706832c0a2c0e827bfa9b0a55cc478eaf2757a4de
 
 
 ### Create the appliance VM
@@ -144,49 +133,49 @@ Set up the appliance for the first time.
 3. Open a browser on any machine that can connect to the VM, and open the URL of the appliance web app: **https://*appliance name or IP address*: 44368**.
 
    Alternately, you can open the app from the appliance desktop by selecting the app shortcut.
-1. Accept the **license terms**, and read the third-party information.
 1. In the web app > **Set up prerequisites**, do the following:
+   - **License**: Accept the license terms, and read the third-party information.
    - **Connectivity**: The app checks that the VM has internet access. If the VM uses a proxy:
-     - Click on **Set up proxy** to specify the proxy address (in the form http://ProxyIPAddress or http://ProxyFQDN) and listening port.
+     - Select **Proxy settings**, and specify the proxy address and listening port in the form http://ProxyIPAddress or http://ProxyFQDN.
      - Specify credentials if the proxy needs authentication.
      - Only HTTP proxy is supported.
-     - If you have added proxy details or disabled the proxy and/or authentication, click on **Save** to trigger connectivity check again.
    - **Time sync**: The time on the appliance should be in sync with internet time for discovery to work properly.
-   - **Install updates**: The appliance ensures that the latest updates are installed. After the check completes, you can click on **View appliance services** to see the status and versions of the components running on the appliance.
-   - **Install VDDK**: The appliance checks that VMware vSphere Virtual Disk Development Kit (VDDK) is installed. If it isn't installed, download VDDK 6.7 from VMware, and extract the downloaded zip contents to the specified location on the appliance, as provided in the **Installation instructions**.
+   - **Install updates**: The appliance ensures that the latest updates are installed.
+   - **Install VDDK**: The appliance checks that VMware vSphere Virtual Disk Development Kit (VDDK) is installed. If it isn't installed, download VDDK 6.7 from VMware, and extract the downloaded zip contents to the specified location on the appliance.
 
-     Azure Migrate Server Migration uses the VDDK to replicate machines during migration to Azure. 
-1. If you want, you can **rerun prerequisites** at any time during appliance configuration to check if the appliance meets all the prerequisites.
+     Azure Migrate Server Migration uses the VDDK to replicate machines during migration to Azure.       
 
 ### Register the appliance with Azure Migrate
 
-1. Paste the **Azure Migrate project key** copied from the portal. If you do not have the key, go to **Server Assessment> Discover> Manage existing appliances**, select the appliance name you provided at the time of key generation and copy the corresponding key.
-1. Click on **Log in**. It will open an Azure login prompt in a new browser tab. If it doesn't appear, make sure you've disabled the pop-up blocker in the browser.
-1. On the new tab, sign in by using your Azure username and password.
+1. Select **Log In**. If it doesn't appear, make sure you've disabled the pop-up blocker in the browser.
+2. On the new tab, sign in by using your Azure username and password.
 
    Sign-in with a PIN isn't supported.
-3. After you successfully logged in, go back to the web app. 
-4. If the Azure user account used for logging has the right [permissions](tutorial-prepare-vmware.md#prepare-azure) on the Azure resources created during key generation, the appliance registration will be initiated.
-1. After appliance is successfully registered, you can see the registration details by clicking on **View details**.
+3. After you successfully sign in, go back to the web app.
+4. Select the subscription in which the Azure Migrate project was created, and then select the project.
+5. Specify a name for the appliance. The name should be alphanumeric with 14 characters or fewer.
+6. Select **Register**.
 
 
 ## Start continuous discovery
 
 The appliance needs to connect to vCenter Server to discover the configuration and performance data of the VMs.
 
-1. In **Step 1: Provide vCenter Server credentials**, click on **Add credentials** to  specify a friendly name for credentials, add **Username** and **Password** for the vCenter Server account that the appliance will use to discover VMs on the vCenter Server instance.
+### Specify vCenter Server details
+1. In **Specify vCenter Server details**, specify the name (FQDN) or IP address of the vCenter Server instance. You can leave the default port or specify a custom port on which vCenter Server listens.
+2. In **User name** and **Password**, specify the vCenter Server account credentials that the appliance will use to discover VMs on the vCenter Server instance. 
+
     - You should have set up an account with the required permissions in the [previous tutorial](tutorial-prepare-vmware.md#set-up-permissions-for-assessment).
     - If you want to scope discovery to specific VMware objects (vCenter Server datacenters, clusters, a folder of clusters, hosts, a folder of hosts, or individual VMs.), review the instructions in [this article](set-discovery-scope.md) to restrict the account used by Azure Migrate.
-1. In **Step 2: Provide vCenter Server details**, click on **Add discovery source** to select the friendly name for credentials from the drop-down, specify the **IP address/FQDN** of the vCenter Server instance. You can leave the **Port** to default (443) or specify a custom port on which vCenter Server listens and click on **Save**.
-1. On clicking Save, appliance will try validating the connection to the vCenter Server with the credentials provided and show the **Validation status** in the table against the vCenter Server IP address/FQDN.
-1. You can **revalidate** the connectivity to vCenter Server any time before starting the discovery.
-1. In **Step 3: Provide VM credentials to discover installed applications and to perform agentless dependency mapping**, click **Add credentials**, and specify the operating system for which the credentials are provided, friendly name for credentials and the **Username** and **Password**. Then click on **Save**.
+
+3. Select **Validate connection** to make sure that the appliance can connect to vCenter Server.
+4. In **Discover applications and dependencies on VMs**, optionally click **Add credentials**, and specify the operating system for which the credentials are relevant, and the credentials username and password. Then click **Add**.
 
     - You optionally add credentials here if you've created an account to use for the [application discovery feature](how-to-discover-applications.md), or the [agentless dependency analysis feature](how-to-create-group-machine-dependencies-agentless.md).
-    - If you do not want to use these features, you can click on the slider to skip the step. You can reverse the intent any time later.
-    - Review the credentials needed for [application discovery](migrate-support-matrix-vmware.md#application-discovery-requirements), or for [agentless dependency analysis](migrate-support-matrix-vmware.md#dependency-analysis-requirements-agentless).
+    - If you're not using these features, you can skip this setting.
+    - Review the credentials needed for [app discovery](migrate-support-matrix-vmware.md#application-discovery-requirements), or for [agentless analysis](migrate-support-matrix-vmware.md#dependency-analysis-requirements-agentless).
 
-5. Click on **Start discovery**, to kick off VM discovery. After the discovery has been successfully initiated, you can check the discovery status against the vCenter Server IP address/FQDN in the table.
+5. **Save and start discovery**, to kick off VM discovery.
 
 Discovery works as follows:
 - It takes around 15 minutes for discovered VM metadata to appear in the portal.