Consider the following guidelines when you are migrating workloads to Microsoft Azure.
For Windows workloads with multiple NICs, 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.
To enable a secondary NIC to communicate outside its own subnet, you can 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.
Each Azure VM has both a public IP address and a private IP address for communications from machines outside the Microsoft 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.