Prepare on-premises Hyper-V servers for disaster recovery to Azure

This article describes how to prepare your on-premises Hyper-V infrastructure when you want to set up disaster recovery of Hyper-VMs to Azure, using Azure Site Recovery.

This is the second tutorial in a series that shows you how to set up disaster recovery to Azure for on-premises Hyper-V VMs. In the first tutorial, we set up the Azure components needed for Hyper-V disaster recovery.

In this tutorial you learn how to:

  • Review Hyper-V requirements, and VMM requirements if your Hyper-V hosts are managed by System Center VMM.
  • Prepare VMM if applicable.
  • Verify internet access to Azure locations.
  • Prepare VMs so that you can access them after failover to Azure.


Tutorials show you the simplest deployment path for a scenario. They use default options where possible, and don't show all possible settings and paths. For detailed instructions, review the article in the How To section of the Site Recovery Table of Contents.

Before you start

Make sure you've prepared Azure as described in the first tutorial in this series.

Review requirements and prerequisites

Make sure Hyper-V hosts and VMs comply with requirements.

  1. Verify on-premises server requirements.
  2. Check the requirements for Hyper-V VMs you want to replicate to Azure.
  3. Check Hyper-V host networking; and host and guest storage support for on-premises Hyper-V hosts.
  4. Check what's supported for Azure networking, storage, and compute, after failover.
  5. Your on-premises VMs you replicate to Azure must comply with Azure VM requirements.

Prepare VMM (optional)

If Hyper-V hosts are managed by VMM, you need to prepare the on-premises VMM server.

  • Make sure the VMM server has a least one cloud, with one or more host groups. The Hyper-V host on which VMs are running should be located in the cloud.
  • Prepare the VMM server for network mapping.

Prepare VMM for network mapping

If you're using VMM, network mapping maps between on-premises VMM VM networks, and Azure virtual networks. Mapping ensures that Azure VMs are connected to the right network when they're created after failover.

Prepare VMM for network mapping as follows:

  1. Make sure you have a VMM logical network that's associated with the cloud in which the Hyper-V hosts are located.
  2. Ensure you have a VM network linked to the logical network.
  3. In VMM, connect the VMs to the VM network.

Verify internet access

  1. For the purposes of the tutorial, the simplest configuration is for the Hyper-V hosts and VMM server to have direct access to the internet without using a proxy.
  2. Make sure that Hyper-V hosts, and the VMM server if relevant, can access the required URLs below.
  3. If you're controlling access by IP address, make sure that:
    • IP address-based firewall rules can connect to Azure Datacenter IP Ranges, and the HTTPS (443) port.
    • Allow IP address ranges for the Azure region of your subscription.

Required URLs

Name Commercial URL Government URL Description
Azure Active Directory Used for access control and identity management by using Azure Active Directory.
Backup * * Used for replication data transfer and coordination.
Replication * * Used for replication management operations and coordination.
Storage * * Used for access to the storage account that stores replicated data.
Telemetry (optional) Used for telemetry.
Time synchronization Used to check time synchronization between system and global time in all deployments.

Prepare to connect to Azure VMs after failover

During a failover scenario you may want to connect to your replicated on-premises network.

To connect to Windows VMs using RDP after failover, allow access as follows:

  1. To access over the internet, enable RDP on the on-premises VM before failover. Make sure that TCP, and UDP rules are added for the Public profile, and that RDP is allowed in Windows Firewall > Allowed Apps for all profiles.
  2. To access over site-to-site VPN, enable RDP on the on-premises machine. RDP should be allowed in the Windows Firewall -> Allowed apps and features for Domain and Private networks. Check that the operating system's SAN policy is set to OnlineAll. Learn more. There should be no Windows updates pending on the VM when you trigger a failover. If there are, you won't be able to sign in to the virtual machine until the update completes.
  3. On the Windows Azure VM after failover, check Boot diagnostics to view a screenshot of the VM. If you can't connect, check that the VM is running and review these troubleshooting tips.

After failover, you can access Azure VMs using the same IP address as the replicated on-premises VM, or a different IP address. Learn more about setting up IP addressing for failover.

Next steps