Multiple Network Interface Cards on VM
This is a big restriction where we cannot assign multiple IP addresses to a single VM.
There could be several design considerations that demand this,
- two public IP's on a Single V,
- internal IP address on one NIC to route traffic inside Azure private cloud and one public IP (for DNS or whatever other service that needs to be reached over a secure tunnel
Thanks for your feedback. This is something that we’re taking a look at providing support for in the near future. Stay tuned.
Brandon Spilove commented
In my opinion, this is a huge pitfall of using Azure VMs to host websites and other web-based applications. Sure if we are only hosting a couple web apps on an Azure VM they could share the same IP. But IIS can host hundreds, if not thousands of websites. It is unreasonable to assume that ALL of them would have to use the same public IP address and segment the traffic via host headers alone. There are many IP address reputation trackers out there, SSL issues, and just basic separation of traffic that would explain the need to have multiple IP addresses on one VM. Every other windows platform supports multiple IP addresses on the same NIC, why not Azure?? This is a deal breaker for us and is forcing us to move to Amazon.
Any update on when Azure will support multiple nics??
Yes, this would be a benefit for more advanced networking and setting up VPN services...etc. Azure already has some sweet networking options, adding this would really open the options :)
Ivo Santos commented
It would be nice if you could create your very own virtual private network o azure, however such a thing requires more than 2 nic's on at least 1 server which should have RRAS + VPN configured which doesn't seem to be possble at the moment, I know it is possible but i think that azure was meant for websites and not virtual private networks with 2 or more domain controllers.
DO you know whether the possibility to add an additional network adapter to a Azure hosted Virtual Machine is going to be (near future) or is currently available?
Angelo Armenteros commented
There is already another suggestion above for multiple NICs per VM. once we can do that we can install RRAS or any other software router to create VPNs and do advanced networking and firewalling inside our Azure environment. You should consolidate your votes on the other request.
Daniel Kelly commented
Some Microsoft Software requires two network cards with statically assigned IP's like Dynamics CRM... This is a big deal, I know that you can use Azure Connect to create some new Virtual Network adapters, but its more or less supposed to be used to connect your "other cloud service" VM's to this Azure VM.
I suspect this more of a problem of hyper V than Azure
I also recommend this