Starting Continuous Discovery
Start course
1h 34m

With the push to the cloud accelerating, it’s critical to understand how to migrate on-premises servers to Microsoft Azure. As an IT professional, you are likely to encounter situations where you need to plan and execute such migrations.

This course provides an overview of the Azure Migrate offering and the various Azure Migrate integrations that are available, before moving on to assessing and migrating VMware virtual machines, Hyper-V machines, and physical machines.

After preparing for migration, this course will walk you through a guided demonstration of an actual assessment and migration of a VMware virtual machine to Microsoft Azure. By the time you finish this course, you should have a full understanding of the Azure Migrate Service and the different options that are available for using it to migrate servers to Microsoft Azure.

If you have any feedback, comments, or questions about this course, please write to us at

Learning Objectives

  • Assess and migrate VMware virtual machines, Hyper-V machines, and physical machines
  • Set up and prepare Azure and VMware for Azure Migrate
  • Learn about the Azure Migrate Server Migration tool, appliance VMs, and continuous discovery
  • Understand all the steps necessary to carry out the migration of a VMware virtual machine to Microsoft Azure

Intended Audience

  • IT professionals interested in becoming Azure cloud architects or preparing for Microsoft’s Azure certification exams
  • IT professionals tasked with managing and supporting Azure virtual machines


  • General knowledge of IT infrastructure
  • General knowledge of the Azure environment and VMware



Okay, welcome back. So now that I have the appliance deployed and registered, it needs to connect to the vCenter Server, so that it can discover the configuration and performance of my VMs.

To make this happen, we're going to click continue here from within our app that we were running earlier. So in the Specify vCenter Server information box here, I need to provide the IP or FQDN of my vCenter Server along with the port that I wanna connect over and I need to use my username and password that I created in vCenter earlier during the Prepare VMware lecture so that I can connect to vCenter and do my discovery.

The IP address of my vCenter Server is And we can see that up here where I'm connected. We'll leave the port 443 at the default and then we'll log in with our Azure migration at vSphere local account. And then we'll validate the connection.

So as you can see here we've successfully connected to vCenter Server, and now if we scroll down further we can see we have an option here to discover applications and dependencies on our VMs.

Now, to discover applications, roles, features, and for visualizing dependencies on my VMs, I need to provide credentials here that have access to those VMs. Now, I can add one credential for Windows VMs and one for Linux VMs.

To specify my credentials here, I can click on Add credentials, and then for this exercise I'm going to choose Windows because it's a Windows VM, and then I'm going to provide a friendly name for the credential that I'm setting up here. Now, this name doesn't have to match the actual username but most times engineers in the wild will make it the same so they know what it is. For this case, I'm going to call it local admin. This tells me it's the local administrator for the machine. And we'll enter in the password for the local administrator account. 

Now, remember, the machine we're going to discover and assess and migrate for this lab is APP01 here. Just so you're aware of what we're going to move here. So what I'm doing in this exercise here is providing the local admin account for the APP01 VM. So we'll go ahead and add this, and then at this point, I can click Save and start discovery to begin discovery of my on-prem environment which in this exercise is just really my vCenter and my APP01 VM.

Now, this can actually take up to 15 minutes or so for the metadata of my discovered VMs to appear in my Azure portal. Discovery of the installed applications, roles, and features can take even more time. The time it takes is going to depend on the number of VMs that are being discovered obviously. For context, it takes about an hour for the application inventory for 500 VMs to appear in the Azure Migrate portal. So what we'll do is we'll let this discovery continue and when it's ready to go, we'll come back and finish up with this.

Now what I want to note before I step away while this runs its course is that if I wanted to, I could have scoped the discovery of my environment by limiting the access of the vCenter account that I'm using for discovery, that Azure migration account. What I can do is limit the access of that account and use that to scope what I'm discovering. Now, if I was going to scope my discovery what I would do is set the scope to vCenter Server data centers, clusters, a folder of clusters, hosts, even a folder of hosts, or to individual VMs.

I'm not doing any scoping in this demonstration. So the account that I'm using was set up ahead of time in VMware so that it has access to everything. So I'm going to pause the video here and when this discovery finishes we'll come back and verify our VMs in the portal.

Okay, welcome back. So we can see that my discovery has completed here. And after this discovery what I can now do is verify that my virtual machines appear in the Azure portal. Now, what I'm going to do is bounce out of my VM. Instead of clicking Go to the portal and relogging in to my Azure portal, I'll just go out to my portal through my workstation here, and I'll go back to home, and we'll go back into Azure Migrate here.

So from here, we'll select Servers under Migration goals here. And we can see under Assessment tools here in the Azure Migrate: Server Assessment box, we can see that a discovery is still in progress. Let's refresh the page here once, and we can see we now have three discovered servers. And if we select the three here, we can see that we have three different servers discovered.

We have the MicrosoftAzureMigration appliance, which is a VMware server. We have our APP01, which is the server we're going to migrate, and we have vCenter01. We didn't get a good application discovery for vCenter01 because the admin account didn't match. It only matched for APP01. And we can see there are five applications discovered as well. If we click on 5 Applications we can then see what those applications are. And it looks like it's mostly Visual C++ plus the VMware Tools application.

If we click on roles and features we can see what roles and features are installed on the VM as well. So we'll close this out. 

So that just about does it for this lesson. Join me in the next demo where we'll set up and run the complete assessment of our environment.

About the Author
Learning Paths

Tom is a 25+ year veteran of the IT industry, having worked in environments as large as 40k seats and as small as 50 seats. Throughout the course of a long an interesting career, he has built an in-depth skillset that spans numerous IT disciplines. Tom has designed and architected small, large, and global IT solutions.

In addition to the Cloud Platform and Infrastructure MCSE certification, Tom also carries several other Microsoft certifications. His ability to see things from a strategic perspective allows Tom to architect solutions that closely align with business needs.

In his spare time, Tom enjoys camping, fishing, and playing poker.