Learn about Prepare on-premises machines
This tutorial will help you to learn about Prepare on-premises machines for migration to Azure. let us have a look in order to prepare throughly.
Verifying migration limitations
The table summarizes discovery, assessment, and migration limits for Azure Migrate. We recommend that you assess machines before migration, but you don’t have to.
| Scenario | Project | Discovery/Assessment | Migration |
|---|---|---|---|
| VMware VMs | Discover and assess up to 35,000 VMs in a single Azure Migrate project. | Discover up to 10,000 VMware VMs with a single Azure Migrate appliance for VMware. | Agentless migration: you can simultaneously replicate a maximum of 300 VMs. For best performance, we recommend creating multiple batches of VMs if you have more than 50. Also, Agent-based migration: you can scale out the replication appliance to replicate large numbers of VMs. In the portal, you can select up to 10 machines at once for replication. To replicate more machines, add in batches of 10. |
| Hyper-V VMs | Discover and assess up to 35,000 VMs in a single Azure Migrate project. | Discover up to 5,000 Hyper-V VMs with a single Azure Migrate appliance | An appliance isn’t used for Hyper-V migration. Instead, the Hyper-V Replication Provider runs on each Hyper-V host. Replication capacity is influenced by performance factors such as VM churn, and upload bandwidth for replication data. In the portal, you can select up to 10 machines at once for replication. To replicate more machines, add in batches of 10. |
| Physical machines | Discover and assess up to 35,000 machines in a single Azure Migrate project. | Discover up to 250 physical servers with a single Azure Migrate appliance for physical servers. | You can scale out the replication appliance to replicate large numbers of servers. In the portal, you can select up to 10 machines at once for replication. To replicate more machines, add in batches of 10. |
Select a VMware migration method
If you’re migrating VMware VMs to Azure, compare the agentless and agent-based migration methods, to decide what works for you.
Verify hypervisor requirements
- Verify VMware agentless, or VMware agent-based requirements.
- Also, Verify Hyper-V host requirements.
Verifying operating system requirements
Verify supported operating systems for migration:
- If you’re migrating VMware VMs or Hyper-V VMs, verify VMware VM requirements for agentless, and agent-based migration, and requirements for Hyper-V VMs.
- Verify Windows operating systems are supported in Azure.
- Verify Linux distributions supported in Azure.
Review URL and port access
Review which URLs and ports are accessed during migration.
| Scenario | Details | URLs | Ports |
|---|---|---|---|
| VMware agentless migration | Uses the Azure Migrate appliance for migration. Nothing is installed on VMware VMs. | Review the public cloud and government URLs needed for discovery, assessment, and migration with the appliance. | Review the port requirements for agentless migration. |
| VMware agent-based migration | Uses the replication appliance for migration. The Mobility service agent is installed on VMs. | Also, Review the public cloud and Azure Government URLs that the replication appliance needs to access. | Also, Review the ports used during agent-based migration. |
| Hyper-V migration | Uses a Provider installed on Hyper-V hosts for migration. Nothing is installed on Hyper-V VMs. | Review the public cloud and Azure Government URLs that the Replication Provider running on the hosts needs to access. | The Replication Provider on the Hyper-V host uses outbound connections on HTTPS port 443 to send VM replication data. |
| Physical machines | Uses the replication appliance for migration. The Mobility service agent is installed on the physical machines. | Review the public cloud and Azure Government URLs that the replication appliance needs to access. | Review the ports used during physical migration. |
Verify required changes before migrating
There are some changes needed on VMs before you migrate them to Azure.
- For some operating systems, Azure Migrate makes changes automatically during the replication/migration process.
- For other operating systems, you need to configure settings manually.
- It’s important to configure settings manually before you begin migration. If you migrate the VM before you make the change, the VM might not boot up in Azure.
Configure Azure VMs after migration
After migration, complete the below mentioned steps on the Azure VMs that are created:
- To connect to the VM over the internet, assign a public IP address to the VM. You must use a different public IP address for the Azure VM than you used for your on-premises machine.
- Then, Check that network security group (NSG) rules on the VM allow incoming connections to the RDP or SSH port.
- Finally, Check boot diagnostics to view the VM.
Reference documentation – Prepare on-premises machines for migration to Azure