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
Please provide for multiple site to site connections from Windows Azure.
Yes sir we need to connect around 5 sites to Azure's vNetwork. Please do as soon as possible.
Jesper Ravn commented
We urgent need to connect around 40 branch office sites via Azure Site-To-Site VPN
Please make it a top priority to implement this feature asap
Ulrich Kirkegaard commented
I agree there should be many more options to tweak network as is normal in a real hardware router, or offer to lease a real router; just as Joyent offers to stick in a Cisco ASA 5505; its totally manageable then.
we need it badly. From San jose, CA
Evandro Pereira commented
Please we need connect multiple sites with azure
Azure IaaS isn't secure and useful without ability to have multiple site to site VPNs into Azure virtual networks.
Without multi tunnel and/or support for MPLS, Azure IaaS is not Enterprise ready.
Giscard Biamby commented
5 site-to-site VPN connections would cover our needs.
Harry G commented
Many thanks for taking the trouble to respond on here. Watched Edge Show 64, and heard the question, and your response, on this issue - hence coming to post on here.
Hope you manage to get it on the schedule. "working to get this into our schedule" sounds as though it's not on there yet! Not privy to what else IS on there already, but from this user's perspective, this is at the top of _our_ list. But we're new to this, so as we go on, maybe we'll stumble over other things that should be, and maybe are, further up the list.
We have 10 sites to connect to Azure, in Europe and north America
Andreas Gidlöf commented
We currently have 40 sites that we want to connect, but would be good enough if we could just connect our main hubs, that would limit the number to 8.
Johnathan Revell commented
5 sites would cover us now, but with expansion we'd be looking at 20.
Neil Moran commented
My current requirement is to connect 4 sties to Azure via VPN. In an ideal world it could also support 100+ user/remote access connections, too, from a wider variety of client OS than just Windows.
Chris Barth commented
I have about a dozen sites and about that many more who work from home and would use a direct VPN connection to Azure. Ideally, given the reliability of Azure, I would like to have upwards of 100 people (with room for growth) to use the VPN connection to Azure as a portal to get to the other connected sites, I believe that is where DirectAccess comes in. In my mind, DirectAccess is a fancy version of VPN and it should all be included together.
Currently my need sits at about 25 sites, however I expect that to grow to at least 50 and potentially up to 100 sites. Hopefully this can be a mesh VPN capability and not just a hub and spoke type connectivity. My current VPN structure is mesh, and is the best option for fault tolerance.
I would take Hub and Spoke though if the only option.
I am currently using Azure and would consider it as a full data center replacement except for this issue. To accomplish this I would need to be able to support 60+ connections with gowth capacity.
Thanks for the feedback. The product team understands this is a critical missing feature on the Azure platform, and is working to get this into our schedule.
At the same time, please let us know what is the target number of sites that could meet your requirements. Is it 5, 10, 50, or 200? Obviously, 10 or 20 should cover a substantial group of businesses, but it will be useful for the team to know a target number for support.
One note on the subject: "DirectAccess" as in the remote access technology offered in Windows Server is currently NOT on the Azure VPN support roadmap. Just want to clarify that.
Yes, important feature to have!
Is this still not available? Any ETA???