AzureMigrate

Objective

Azure Migrate is a service that makes it easy to assess on-premises workloads for migration to Azure. The
assessment includes migration suitability, performance-based sizing, cost-estimation of your on-premises
workloads. In this lab, we will see how we can use Azure Migrate to discover and assess an on-premises
VMware environment. The exercise will involve the following tasks.

a. Create an Azure Migrate project

b. Discover the vCenter Server environment in Azure Migrate
c. Assess the discovered machines for migration to Azure

Scenario

Virtual Machines

1. ESXi01
2. vCenter01
3. DC
4. floppyfw 3.0.15

Exercise 1 : Create a migration project

In this first exercise, you will create a migration project to get started with Azure Migrate. A migration project
holds the metadata that is discovered from the on-premises environment.

1. Connect to the lab environment

Click the Resources tab on the top right, click on vCenter01 and then click Ctrl+Alt+Delete. Sign in
to vCenter01 as vsphere\administrator using Passw0rd! as the password. You can alternatively use
the icon next to username and password to copy-paste these.

NOTE: Dimiss any notices that prompt you to restart the computer.

2. Navigate to Microsoft Azure

Once you are logged on to the VM, click the Google Chrome shortcut on the desktop of the VM and
browse to https://portal.azure.com/.

3. Logon to Azure

Click the Resources tab. Note the Portal Credentials that are listed on the Resource tab. Logon to the
Azure Portal using the username and password you see displayed on this tab. TIP: Click the Type Text
 icon to paste the user name and passwords into the appropriate fields.

Specify No on any pop-ups that might show up. When you are logged in, you may see a pop-up
called Welcome to Microsoft Azure, click Maybe later in the pop-up.

You will use these portal account credentials for Exercises 1 and 2. In Exercise 3, you will use other
portal account credentials to sign into a subscription that has been previously hydrated with data.

4. Create a migration project

In the Azure Portal, in the Search box on the top, type Azure Migrate and then select Azure
Migrate under MARKETPLACE.

5. Specify project details

In the Create Migration Project blade, in Name type xxxAzureMigrate, where xxx is your initials.
Leave Subscription with the default value. In Resource group, select any available resource group
from the drop down list. In Location, select West Central US. Click Create.

You may need to wait for a minute for the project to be created.

6. Review migration project

In the Azure Portal, in the Search box on the top, type Azure Migrate and then select Migration
projects (preview) under SERVICES. Click the migration project that you just created.

In the Migration projects page, if you do not see the migration project you just created, wait for a few
minutes and then click Refresh. The deployment may take a minute or so to complete.

7. Browse to the migration project

In the migration project page, click Discover Machines on the top pane. There are four steps in the
discovery process. The first two have been completed for you. You will now complete steps 3 and 4.
Minimize the browser window as you will use it later in the next exercise.

In this first exercise that you completed, you created a migration project that will be used to discover and assess
on-premises VMware VMs for migration to Azure.

Exercise 2 : Discover a VMware environment

In this second exercise, you will initiate the discovery of your on-premises VMware environment. The discovery of
the on-premises environment is done using a virtual appliance, called Azure Migrate Collector.

1. Connect to vCenter Server

Now, we will power on the pre-created Azure Migrate Collector virtual machine. On the Desktop,
double-click the VMware vSphere Client shortcut. Logon as Administrator@vsphere01.local using
the password Passw0rd!. If prompted with a certificate warning, click Ignore.
2. Start the Azure Migrate collector

In vCenter Server, on the Getting Started tab, under Basic Tasks, click Power on the virtual
machine link to switch on the Azure Migrate collector virtual machine. The collector VM will be used to
discover the on-premises vCenter Server environment. Click the Console tab in the vCenter Server UI.
In the VMware dialog box, click I Copied it and then click OK. Wait for a few moments for the VM to
start.

3. Connect to the Azure Migrate collector

On the Summary tab, note the value of IP Address of the VM. Click Start on the desktop of the VM
(Windows icon on the bottom left of the desktop), type MSTSC and then press ENTER. In Computer,
type the IP address shown on the Summary tab in vCenter Server, and then click Connect When
prompted, in Password, type Passw0rd!, click OK and then click Yes. Once connected, if you get any
network-related pop-up, click Yes.

If the VM does not show an IP address of 10.10.10.xx, refresh the summary view by clicking any other
tab, and then going back to the summary view.

4. Run the Collector

On the desktop of your remote-desktop session, double-click Run Collector to start the collector
application.

5. Verify Setup Prerequisites

In the collector, check I accept the end user license agreement, and then click Continue.

6. Discover Virtual Machines

In Discover Virtual Machines, in vCenter Name/IP Address type 10.10.10.102. In User

name type adminstrator@vsphere01.local. In Password type Passw0rd!, and then click Connect.
Note that the collector only needs read-only credentials for vCenter Server and does not ask for any
privileged credentials. Once the green Connected status is present, in vCenter inventory scope,
select Datacenter\esx01.vsphere.local and then click Continue.

7. Select a Migration Project

In Specify the project ID and key, copy and paste the values of Project ID and Project Key from the
Microsoft Azure Portal page you have left open in Google Chrome, and then click Continue. The
discovery will proceed and will complete quickly, but, the machines may take some time to show up in
the migration project. You will now proceed to evaluate the results in a pre-created migration project.

8. Close all Open Windows

Close all open windows on vCenter01 in preparation for the next exercise. You will use another set of
credentials in the next exercise to sign into a subscription that has been previously populated with
data.
In this second exercise you just completed, you initiated the discovery of the on-premises VMware environment
using the Azure Migrate Collector. The discovered machines will take some time to show up in the migration
project. You will now proceed to a pre-created migration project to assess the discovered machines.

Exercise 3 : Assess the discovered environment

In this third exercise, you will review few pre-created migration projects and create an assessment of the
discovered virtual machines. You will also learn how to view dependencies of the on-premises machines to create
high-confidence groups for migration.

1. Navigate to Microsoft Azure

Using Google Chrome, navigate to https://portal.azure.com/. Logon

as MigrateHOL@hynesite.biz using the password Ignite2017.

2. Connect to the Microsoft Directory

In the Azure Portal, in the upper right corner, click the username, and then click Microsoft to switch to
the Microsoft directory.

3. Browse to an existing migration project

In the Azure Portal, in the Search box on the top, type Azure Migrate and then select Migration
projects (preview) under SERVICES. In the Migration projects page, click LabProject from the list of
projects. The discovery for LabProject is already completed and we will now use it to create an
assessment.

4. Create an assessment

In the migration project, click the +Create assessment command on the top pane to create an
assessment. An assessment is created on a group of machines that you plan to migrate together.
In Select or create a group, specify xxxgroup as the group name where xxx are your initials. In Add
machines to the group, select the WEB and SQL VMs and then click Create assessment.

While creating the assessment, the assumption here is that the user will know the machines that need
to be taken together to Azure. However, we will see later in the exercise, how you can visualize
dependencies of machines and identify machines that need to be migrated together. The dependency
visualization functionality requires installation of agents on the on-premises machines.

5. Review the assessment

On the project Overview page, you will see the list of assessments that are created and the status of
assessment creation.The top row in the list will show the assessment you just created. Wait for few
seconds for the assessment status to change from Computing to Ready, and then click the
assessment to view it.

6. Review Azure readines

 On the assessment, click the Azure readiness chart. In the Azure readiness details page, Azure Migrate
will help you identify the VMs that are not suitable for Azure (if any) and will help you understand the
suitability-issues. Azure Migrate will also right-size the VMs for Azure based on performance history of
VMs and will recommend an Azure VM size for each on-premises machine. Note down the VM sizes
recommended by Azure for the WEB and SQL machines as you will need these later when you are
migrating the VMs using Azure Site Recovery.

7. Review cost details

Click on Cost details tab in the assessment to review the estimated cost of running the on-premises
VMs in Azure. You will see the total monthly cost of running the on-premises machines in Azure as well
as the cost per machine. The cost is divided into compute and storage costs.

8. Review assessment properties

Click Edit properties command on top to view the properties associated with the assessment. The
properties specified here impact the sizing and cost estimation logic used by Azure Migrate. You can
customize an assessment based on your needs by changing the assessment properties. For example,
you can specify the Target location you want to migrate to or specify the Offer you are enrolled to
and the cost estimation will be done accordingly. Similarly, you can specify the duration
of Performance history you want to consider for right-sizing the on-premises VMs. Close the Edit
properties blade.

9. Export the assessment report

Click Export assessment command on top of the assessment to download the assessment report in an
Excel format. The assessment report in Excel format can be shared with various stakeholders after
doing required modifications. Close the assesssment and the migration project page.

10. Browse to another migration project

We will now browse to another project that has discovery data of a complex environment. From the
Migration projects page, click DemoProject. We will use this project to visualize dependencies of
machines and create groups. We will then review an existing assessment in this project to review
complex readiness scenarios.

11. View dependencies of a machine

One the migration project Overview page, click the Machines tile that displays the count of machines
discovered in the project. In the machine list, search for MiddleTierVM01 and click View
dependenciesin the third column to view its dependencies. Dependency visualization requires
installation of agents on the on-premises machines, it has already been done for this machine.

12. Review dependencies and create a group

On the Dependencies page, you will see the dependency map of the VM, MiddleTierVM01. The
dependency map will show you all the incoming and outgoing TCP connections from the VM. You can
expand MiddleTierVM01 to see the processes that are communicating with each of the dependent
machines. This will help you identify the machines are related and need to be taken together to Azure.
 In this case, MiddleTierVM01 is talking to FrontTierVM01, DataTierVM01 and DataTierVM02.
Use Ctrl+Click to multi-select these machines and click +Group machines on top left to group these
machines together. In Create a new group, specify xxxgroup1 as the group name where xxx are your
initials.

Click OK to create the group. You can then later create an assessment for this group. We will not do
this in this exercise as we already have an assessment pre-created.Close the Dependencies page.

13. Review an existing assessment

Click Assessments on the left pane of the project under Manage. From the list of assessments, click
the assessment assessment_1_19_2018_16_8_44 that is listed with group as contosopayroll.
Click Azure readiness chart in the assessment. In the Azure readiness details, Azure Migrate will help
you identify the VMs that are not suitable for Azure. For example, in this report, DataTierVM03 has an
EFI boot type which is not supported in Azure, MiddleTierVM01 uses an older operating
system, MiddleTierVM03 uses an unsupported Linux OS.

Azure Migrate also right-sizes the VMs for Azure based on performance history of VMs and
recommends an Azure VM size for each VM. You can use these VM sizes when you are migrating your
VM using Azure Site Recovery.