A
network interface (NIC) is the interconnection between a VM and a virtual network (VNet). A VM must have at least one NIC, but can have more than one, depending on the size of the VM you create. Learn about how many NICs
each VM size supports for
Windows or
Linux.
You can create a VM with multiple NICs and add or remove NICs through the lifecycle of a VM. Multiple NICs allow a VM to connect to
different subnets and send or receive traffic over the most appropriate interface.
If the VM is added to an availability set, all VMs within the availability set must have one or multiple NICs. VMs with more than
one NIC aren’t required to have the same number of NICs, but they must all have at least two.
Each NIC attached to a VM must exist in the same location and subscription as the VM. Each NIC must be connected to a VNet
that exists in the same Azure location and subscription as the NIC. You can change the subnet a VM is connected to after it's created, but you cannot change the VNet.
Each NIC attached to a VM is assigned a MAC address that doesn’t change until the VM is deleted.
Refer the below articles:
https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-network-interface-vm
https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-network-interface-vm#constraints
If you want to add multiple NICs in Windows VM, refer the steps outlined in the below article:
https://docs.microsoft.com/en-us/azure/virtual-machines/windows/multiple-nics
If you want to add multiple NICs in Linux VM, refer the steps outlined in the below article:
https://docs.microsoft.com/en-us/azure/virtual-machines/linux/multiple-nics
------------------------------------------------------------------------------------------
Do click on "Mark as Answer" on the post that helps you, this can be beneficial to other community members
