As part of your migration journey to Azure, you assess your on-premises workloads to determine cloud readiness, identify risks, and estimate costs and complexity.
This blog shows you how to assess Google Cloud Platform (GCP) VM instances for migration to Azure, using the Azure Migrate: Discovery and Assessment tool.
In this blog, you learn how to:
Run an assessment based on server metadata and configuration information.
Run an assessment based on performance data.
Prerequisites
Before you follow the steps in this tutorial, complete the first tutorial in this series to discover your on-premises inventory.
Decide which assessment to run
Decide whether you want to run an assessment using sizing criteria based on server configuration data/metadata that's collected as-is on-premises or based on performance data.
Assessment | Details | Recommendation |
As-is on-premises | Assess based on server configuration data/metadata. | Recommended Azure VM size is based on the on-premises VM size. 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 performance data. | Recommended Azure VM size is based on CPU and memory utilization data. 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. Go to Servers, databases and web apps > Azure Migrate: Discovery and assessment.
2. In Azure Migrate: Discovery and assessment, click Assess.
3. In Assess servers > Assessment type, select Azure VM.
4. In Discovery source:
o If you discovered servers using the appliance, select Servers discovered from Azure Migrate appliance.
o If you discovered servers using an imported CSV file, select Imported servers.
5. Click Edit to review the assessment properties.
6. In Assessment properties > Target Properties, do the following:
o 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. Once you change the target location from default, you will be prompted to specify Reserved Instances and VM series.
In Azure Government, you can target assessments in these regions.
o 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 the disk IOPS and throughput.
Alternatively, select the storage type you want to use for VM when you migrate it.
o In Reserved Instances, specify whether you want to use reserved 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 about VM resrved instances. Learn more about VM resrved instances.
7. In VM Size:
o In Sizing criteria, select if you want to base the assessment on server 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.
o 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 the 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.
o In Comfort factor, indicate the buffer you want to use during the assessment. This accounts for issues like seasonal usage, short performance history, and likely increases during 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:
o In Offer, specify the Azure offer if you're enrolled. The assessment estimates the cost for that offer.
o In Currency, select the billing currency for your account.
o In Discount (%), add any subscription-specific discounts you receive on top of the Azure offer. The default setting is 0%.
o In VM Uptime, specify the duration (days per month/hour per day) for which the 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.
o In EA Subscription, specify whether to take an Enterprise Agreement (EA) subscription discount into account for cost estimation.
o 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 when you bring licenses to Azure.
9. Click Save if you make changes.
10. In Assess Servers, click Next.
11. In Select servers to assess > Assessment name, specify a name for the assessment.
12. In Select or create a group > Create New and specify a group name.
13. Select the appliance, and select the VMs you want to add to the group. Click Next.
14. In Review + create assessment, review the assessment details, and click Create Assessment to create the group and run the assessment.
15. After the assessment is created, view it in Servers > Azure Migrate: Discovery and assessment > Assessments.
16. Click Export assessment to download it as an Excel file.
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, databases, and web apps > Azure Migrate: Discovery and assessment, click the number next to Assessments.
2. In Assessments, select an assessment to open it. As an example (estimations and costs for example only):
1. 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:
o Ready for Azure: Used when Azure Migrate recommends a VM size and cost estimates, for VMs in the assessment.
o Ready with conditions: Shows issues and suggested remediation.
o Not ready for Azure: Shows issues and suggested remediation.
o Readiness unknown: Used when Azure Migrate can't assess readiness, because of data availability issues.
3. Select an Azure readiness status. You can view the 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.
o Cost estimates are based on the size recommendations for a server, its disks, and its properties.
o Estimated monthly costs for compute and storage are shown.
o 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
Azure Migrate assigns a confidence rating to performance-based assessments. Rating is from one star (lowest) to five stars (highest).
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.
Confidence ratings are as follows.
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 |