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.
@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
Ditto to all these posts. What is the hold up? Can you please provide an update to the many requests for STOP/START gateway capability? I need my ExpressRoute gateway, but only need to connect a few times during during the month (and for short periods of time). Yet this gateway amounts for 90% of my monthly charge! I thought Azure cloud computing was built on the pay-only-for-what-you-use model.
Ben H commented
I too will be cancelling if this doesn't get implemented
Patrick Wingert commented
Since I am using azure as a teaching lab for myself and others I also want to be able to start/stop the gateway. Until this functionality is added I have cancelled my subscription until this feature is implemented.
Come on Microsoft - how is it per hour charge if you charge when the feature is not in use and there is no way to stop it - unlike the VM. In my scenario I have a specific VM that needs to be reachable only during work hours - and that is when I need the VPN. But instead of paying for 8 hrs a day, I pay for 24? That is ridiculous!
Dan Einarsson commented
Also in need of START/STOP feature!
The Rocksurian commented
Not having the "STOP" on a Azure site-to-site VPN really isn't any good for development. We DO NOT need the gateway 24/7 we only need it on during testing. Once it goes LIVE we are happy to pay but the development lab is in a Credit subscription and we keep running out of credit as the gateway literally eats all the credit even though everything is spun down.
MS come on be fair, we'll pay for it, honest, when we put it LIVE
Peter Selch Dahl commented
I think this decidion will dissapoint a lot of people. Please reconsider this decision
[Deleted User] commented
Still no update. Disappointing ...
I have a VPN gateway connected to my on-premises netwirwork. I would like that have no charges if the gateway is disconnected.
Graham Bird commented
Just to add more backing to this, I have a MSDN that is rendered useless with in 1/2 a month as the credit is used by the two gateways I need to have running to simulate our setup.
As requested there should be a way to stop these gateways when I dont need them.