Welcome to part 3 on migrating Azure resources from ASM to ARM with the help of Azure Site Recovery.
In this part we will go over 2 options on how to connect the ASM network to the ARM network.
This is needed as we want our source VMs to communicate with the process server!

VNET Peering
this feature is currently under preview (Let’s not forget that preview also means FREE 😉 ) and is by far the most simple way to connect VNETs.
With VNET Peering you can also connect ASM VNET to ARM VNET without the use of VNET gateway site to site VPN connections.
Today this feature is limited to connect VNETs if they are:
– in the same region (might change later, but today a VNET’s boundary is the region it was created in)
– subnets IP ranges don’t overlap
– for connecting ASM to ARM networks, VNETS must be in same subscription
You can peer networks in different subscriptions if:
– the privileged user must have rights in both subscriptions AND
– both subscriptions are connected to the same Azure Active Directory.
Create peering takes less than 5 minutes:

almost instantly:

The other option requires a little more configuration as we need to create a Site to Site VPN Connection between the 2 VNET gateways in different deployment models and that requires some PowerShell to make this work.
You will need to select this option if:
– you need to connect networks in different regions
– you need to connect to network in another subscription that is not linked to the same Azure AD
The whole process is already very nicely documented and you can find it here: https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-connect-different-deployment-models-portal

In the following chapter we will talk about installing the mobility agent on our source servers

part 4: Mobility Agent installation 

In case you landed on this page, you can find the other topics here:
Part 1: Creating ASM resources through ARM portal  
Part 2:  Create ARS Vault and configure process server