In this video, learn about the Migrate assessment, including the various status options and requirements for a workload to be labelled as ready.
- [Instructor] Now that we've had an overview of Azure Migrate, let's dive into the assessment portion of the service. The assessment determines if the on-premises workloads are suitable for migration. It will also determine the size of the virtual machines in Azure, as well as provide a monthly cost estimate based on the size of those virtual machines. There are various statuses in the assessment, and the first being the status of the workload suitability.
Basically, can the workload migrate to Azure and there are four statuses that you need to be aware of. The first one is Ready for Azure. When we have this status, the virtual machine will boot in Azure with full support. If you have a status Conditionally ready for Azure, the virtual machine may boot in Azure, but it may not have full support. Next we have the status, Not ready for Azure. The virtual machine will not boot in Azure. And finally, Readiness unknown.
In this case, the information about the virtual machine could not be collected. Next we have the suitability of the machine properties. And there are several here starting with the boot type. If the boot type is BIOS, then the Azure readiness status will be ready, and the status will be conditionally ready if the boot is UEFI. Next we have the number of cores. If the virtual machine has less than or equal to 32 cores, the status will be ready.
And it's similar for memory. As long as the virtual machine has less than 3892 gig or less of memory, the status will be ready. Next we have storage. If the virtual machine has no more than four terabytes of allocated disk size and 65 or less disks attached to the virtual machine, the status will be ready. And our last property is networking. If the virtual machine has 32 NICs or less attached to the machine, then the status will be ready.
Next we have the Guest OS workload suitability, and this will be based off the operating system. Windows Server versions 2008 and above have full Azure support and the status will be ready for Azure. Windows Server 2003 and 2003 R2 will be conditionally ready for Azure, but Microsoft recommends upgrading before migration, and if you are going to migrate 2003, you will require a custom support agreement.
Next we have some of the legacy versions of Windows, including Windows 2000, 95, NT, 3.1, Microsoft-DOS for those of you who remember that far back, Windows XP and Windows Vista. No OS support is provided in Azure. The status will be conditionally ready, but Microsoft will recommend upgrading before migration. The client OSs Windows 7, 8, and 10 are supported with a Visual Studio subscription only, and these will be conditionally ready for Azure.
And finally, we have Linux, because Microsoft does love Linux. Only endorsed, supported Linux operating systems will be supported, and they will be ready for Azure if endorsed. If they are not endorsed, then the status will be conditionally supported. Also included in the assessment is the sizing of the virtual machines, and this can be calculated on either performance, which will take into account the storage, network, and compute, or based on on-premises sizing.
If we choose on-premises sizing, the virtual machine will be allocated based on the size of the on-premise virtual machine, and finally, a confidence rating will be given based on the assessment, from one being the lowest to five being the highest and this will be represented in stars. And finally, we have the monthly cost estimation in the assessment, and this is broken down into two costs. We have the compute cost which factors in the operating system, software assurance, reserved instances, virtual machine uptime, location, and currency.
And storage cost. And this will be estimated by gathering the monthly cost of all the disks attached to the machine. As you can see, the assessment will help you determine what you can easily migrate to Azure, what may require some work and what can't migrate, as well as the cost associated with moving those workloads.
- Managing Azure subscriptions and resources
- Implementing and managing storage
- Configuring and managing virtual networks
- Managing identities
- Evaluating and performing server migration to Azure
- Implementing and managing application services
- Implementing advanced virtual networking
- Securing identities