Stop/Start Virtual Network Gateway - to don't pay when it not in use
There are two charges related to the Azure VPN service: the compute resource charge at $0.05/hour, and the egress data volume charge. Both are based on resource consumption, Unfortunately, even if the VPN tunnels are not connected, the gateway compute resource is still being consumed and will cost ~$38 monthly!
This is not really "Pay only for what you use".
Need functionality to “STOP” (and of course "START") a gateway if the customer is certain that the gateway will not be in use.
We’ve moved this ask to the backlog due to technical challenges in reserving Public IP addresses during stop state.
Alex Figueiredo commented
I was doing a test here, and left the VPN Gateway, think it's only cost when is with traffic data. After 15 days I was scared of how my bill was! Sorry, this is not for testers, this is for real enterprises with money to pay 24h of use, not for a mortal like me.
Aanand Ramachandran commented
Folks - thanks for you comments on this feature. We understand that this is an important ask for many customers. It is in our list of features to add and is being discussed. Once we decide on a timeline for supporting this we will make an announcement.
Peter de Wit commented
Same here. With this limitation it is FAR cheaper to build your own server based on pfsense or whatever.
Lars Fastrup commented
May I suggest a simple solution here. Release the Basic VPN sku of hourly charges and charge only for the traffic.
Gert Humphris commented
We also have this requirement. Want to build a big network with lots of VPN Gateways but if we cannot turn them off when not in use the cost is going to be too much to make it a viable project.
I know Azure Virtual Network Gateways are basically special-purpose VMs running windows RRAS and/or IPsec tunnel rules. the point is that once you spin one Gateway up, there is no way to stop it unless you delete it all together.
please add a feature to Stop/Start the gatways on-demand/scheduled/automated on top of the current always-on config. I use Azure as my lab environment and has configured it to connect to my home router. even when I disable IPsec tunnel on my end, Azure is still running the Gateway, trying to connect to my router, and charging me for it. I am paying about 45$/month for simply not doing anything with my lab!
Its been over 3 years since people started requesting this. Microsoft we need this functionality yesterday!
Fernando Medeiros commented
Microsoft, we need a way to stop/start vpn gateway now. It`s high important if you think about to be a cloud leader.
Any updates in the way this is being billed MSFT? The STOP functionality has been requested since 2014!
Foglia Taverna Maurizio commented
no news ??? my msdn credit is over ... argh, my test is blocked.
@Azure team......what is happening> Are there any updates? Instead of start/stop? VPN charges should be calculated based on connectivity ? Does every feedback provided ot Microsoft take years to resolve? Eg: Just getting Azure to send us the Invoice via emails take >2 years!!
Shailesh Puranik commented
I will suggest provisioning a CentOS VM on Azure and configure VPN tunnel between your on-premises VPN gateway and centos VM VPN gateway. you can start and stop by manually or setup a schedule.
Jeremy Bradshaw commented
A Microsoft response in 2017 would be nice. It is now Q2 in 2017. If it didn't take 15-20 minutes to provision a new virtual network gateway I would just de / re-provision as needed. But it does take that long unfortunately.
Nivaldo Fernandes commented
Hi There, same need here.
Gert Kjerslev commented
I also need this. Testing Site-to-site VPN has used way to munch of my monthly test/dev budget. Come on MS! We need to stop/start Virual Network Gateway's in azure now.
Frederick Lin commented
Need the ability for this as well. It is just sitting idle for the majority of the time and would like the ability to stop...
Another joining in the chorus. Currently evaluating site recovery services with our MSDN subscription and more than 3 quarters of the allowance is swallowed up by having to run the gateway non-stop.
Chris M. commented
Nearly three years and still no solution? Embarrassing, when I see, that MS is trying to push Dev/Test Labs.
Furthermore no auto generated templates for gateways in the new portal.
Come on MS, that's the wrong strategy to become the cloud market leader, where costs are the number one argument.
The inability to Stop a virtual network gateway and thereby stop the billing destroys our ability to operate test/research environment. I don't mind paying for it when I'm using it but let me turn it off.
Is there an update on this please ? I am running a small virtual test lab. Today I was able to successfully setup the VPN Tunnel. My pfsense VPN appliance has got a Connect/Disconnect button - a very handy switch that can help me to make/break the tunnel. However I do not see anything on the Azure side. Now this means even if i break the connection at my end , Azure VPN device will still try to sent connection traffic towards my router(carrying the public ip) and will cost me!!!! Please do something