You can create a virtual machine with multiple NICs in Azure virtual networks. Each NIC must be located in one subnet; one subnet can be assigned to multiple NICs. Each NIC has an IP address consistent with its subnet assignment. The IP address and MAC pairing for each NIC persists, even if the order of the NICs changes.
Consider the following guidelines when you are migrating workloads to Microsoft Azure.
You can use private IP addresses for workload migration if you have configured an Azure VPN to connect your premise network with your Azure cloud environment. Otherwise, you must enable a public IP address to be assigned to the replication network, cutover network, and test cutover network. If the VM has multiple NICs, only the primary NIC can have a public IP address. The assigned public IP addresses will be in the address space of the specified network and subnet for the designated NIC in each network.
NOTE:PlateSpin requires a public IP address only if a site-to-site Azure VPN is not available.
If you enable a public IP address for the primary NIC, Azure assigns the NIC both a public IP address and a private IP address. For more information about connecting to the Azure VM, see Private and Public IP Addresses for Workloads Connected on an Azure VPN.
Azure configures the VM with a default gateway that is associated with the primary network interface. Azure removes the gateway information for all secondary NICs, which limits their communications to the same subnet as the primary interface.
For Windows workloads with multiple NICs, you can enable a secondary NIC to communicate outside its own subnet. Use the Windows route add command to add a different gateway entry for the secondary NIC in the routing table. See Configure Windows VMs
in Create a VM with Multiple NICs on the Microsoft Azure website.
An Azure VM can have one or more NICs attached to it. The primary NIC for the VM can have both a public and private IP address. A private IP address is used for communications from other resources in a virtual network and from machines inside the address space for the Azure VPN that connects your premise network to your Azure cloud environment. A public IP address can be used to communicate with the Internet and with machines outside the Azure cloud environment. Azure automatically associates these IP addresses with the primary network interface for the VM.
You can use the Microsoft Remote Desktop client to connect remotely to the Azure VM. Specify the IP address as follows:
Private IP address: Use the VM’s private IP address if your machine is part of the address space for the Azure VPN.
Public IP address: Use the VM’s public IP address if your machine is not part of the address space for the Azure VPN.
You can alternatively use the Connect option in the Microsoft Azure portal from a machine with an address space that is not part of the Azure VPN. This option automatically launches the Microsoft Remote Desktop client configured to connect to the VM’s public IP address for the primary NIC.
NOTE:This portal operation fails if your machine is in the address space of the Azure VPN.