Allow S2S VPNs from multiple sites to one Virtual Network
Allow connection to VPN from multiple sites even from sites which are on Dynamic IP addressed to use azure as central site and others a branch offices
As well as allow the possibility of windows machines with direct access to connect to azure VPN
Allow multiple VPN connections to be created in a virtual network so we can connect to both on-premise and another location without all traffic having to be routed via on-premise
A must add! Almost useless without it.
This is a very important feature to be added to Azure.
This is so important a lot of our choices to use azure depend on this technology
Azure must have Mutiple SITE TO SITE ASAP - it is really a MUST option
and IAAS supplier must have this option.
its actualy doesnt allow me to connect at least 10 branches
also you must allow Connectivity between diffrent Azure VNET ( on the same subscription to start )
We need the S2S and P2S enables Azure to service the market need to consolidate infrastructure for many clients on nationally an dinternationaly
Curt Nordin commented
Is this status change related to the new ExpressRoute options announced yesterday, or are you working on a multi-site-to-site solution within Azure?
I argued against Azure for just this reason.
This is a MUST HAVE feature. Please add it as soon as possible.
So this was mentioned in May of last year as an item that the Azure product team knew customers wanted and that they were working on it (see msdn channel at 8:02 http://channel9.msdn.com/Shows/Edge/Edge-Show-64-Windows-Azure-Point-to-Site-VPN)
How has this not been added by this point? Rolling up to a year from that video's publish date!!
Really is needed.
So a little surprised this hasn't been addressed yet. This is a big limitation for us
Agreed, this is a serious oversight that needs to be rectified before Azure IAAS can be seen as anything else than a dev environment at best.
Philip Brewer commented
This is a no brainer! Please add Multiple Site to Site VPN Connectivity to the Virtual Network in Azure.
Is there really still no solution on this?
Stanley Lim commented
1) minimum of 20
2) different keys
3) I would like to be able to route traffic inside azure between sites.
Michael Sainz commented
1. Max Number of Sites - 5
2. Pre-shared Key for each VPN Tunnel - Different for each Tunnel
3. My preferences would be to *not* route site traffic through the Azure gateway
Giscard Biamby commented
1. The max. number of on premises sites that you will connect to a single Azure Virtual Network/VPN - does not have to be precise, we are looking for the ranges (5, 10, 20, 100, etc.)
ANSWER: About 5 S2S would cover our needs
2. For the IPsec/IKE pre-shared keys for each S2S/VPN tunnel, do you expect one pre-shared key for ALL tunnels/sites or one key for each tunnel/site?
ANSWER: Different key for each tunnel.
3. Are you looking to transit traffic through Azure when you have multiple sites connected to the same Azure VPN gateway? Basically, site one sending to site two (not Azure VNet) going through the Azure VPN gateway?
R. E. commented
1) We would need approximately 1000 S2S connections at an affordable price. Yes this is a real-world currently needed scenario!
2) I cannot believe Azure does not already support multiple S2S VPN's.
3) Extend your known compatibility list devices to include the true specs... ANY device with appropriate IPSec / IKE spec's, not just cisco/juniper/whoever else lining pockets.
4) different keys... yes definitely...
5) the main point of this whole thing is the ability to truly have Azure as the centre of the infrastructure.... what a dream that would be.
1) 2-10 sites
2) different keys if possible
3) No need to route traffic via Azure
on a different subject, we are experiencing issues with Azure VPN when it returns an incorrect network mask, it would be great if this issue would be looked at and resolved in the next release
Paul Houghton commented
1) We don't need many VPN's probably 5-10
2) We would expect to use a different key for each connection
3) We would not be looking to route traffic through Azure from one VPN connection to another.
We need to be able to use at least 2 VPN Sites , This would be great to allow for a File Server Witness for our Exchange 2013 roll out. If not we need a to create a 2nd internal datacenter. Which would pretty much make Azure useless. I would rather use Azure.