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.
Eric Cox commented
Instead of grappling with the technical challenges of dynamically allocating public IP addresses, what about simply charging a small flat fee, plus a fee for the traffic used? Seems like that would be a relatively easy change, and would truly be "pay for what you use"
John Mendivel commented
please friends of microsoft will be able to turn off the vpn to avoid having to pay money for something that we will not be using, please note this
Nanthakumar Subramanian commented
I too agree to have an option to stop this vNet Gateway when it is NOT in use. I can effectively use this money elsewhere.
had also a testlab with gateway, only sporadic usage, inaceptable to pay for this 24*7
Hey , Azure team. Last update was June, 27th 2019! It's already 2020 and still no updatem yet! Paying for a public IP still reserved while gateway is stopped are peanuts and no problem for anyone, like others said. Please add that feature for "Pay as you go" reasons
Bring it in!
Yep I'd like this too - happy to pay a bit for the reservation of the IP,
I think Microsoft have fallen asleep at the wheel on this one. Shame, this would be a useful feature for the smaller companies.
Antonio Russo commented
Agreed that this is a very wanted feature. Please team don't let me think that Steve Ballmer is back :).
To avoid PIP issue, why don't use alias ? most firewall can deal with it .
Olga Agafonova commented
Same issue here. I like Bastion a lot but not enough to pay $10/daily for it when I am not using it.
Nearly 6 years without any indication of when it will be added to the roadmap, surely Microsoft?
Azure hosted dynamic DNS should solve the issue with fixed IP.
If we could point our tunnels toward name from azure space like vpn.myDNSname.onmicrosoft-whatsoever.azure.net instead of static public IP, it would save cost for Microsoft and for us as well.
I will bring my VPN GW up, it will get ANY ip, get the DNS name and voila, in minutes I can connect to VPN. Azure mobile app is out already, add the feature and 1900+ people will be more happy (and less revenue for MS :-) ).
At an MSP that deals with small businesses, we would definitely see more widespread adoption. Shiny new Synology NAS and I just need a tunnel for SSO (very little traffic). There should be a way to control cost.
Come on, if we run an ER as our primary connection and have an IPSec gateway configured on a separate VNG and only connect to it when needed, we have to pay for the unused gateway? >1800 votes and five years to get this done, is it hard or is there a financial intensive NOT to do this?
Steve Sykes commented
This is really ridiculous. I understand being charged for it whether you use it or not but something is not right here. I created a connection between US East and US east 2. I've turned deallocated every machine in US East 2 and I'm being charged almost $10 a day. I see no way to avoid this daily charge without deleting the connection all together, That's simply ridiculous.
Either allow an on / off of the virtual network gateway, or make it quicker to spin up. Either way this is painful to see the cost ticking up
Anthony Morales commented
Yes please this is critical for our business model and would be a great CLOUD feature.
Microsoft really needs to give higher priority to customer desires to 'scale down' scenarios in Azure like this. It's not the most obvious feature to pursue at first from Microsoft's perspective because it seems they don't immediately benefit financially from scale down scenarios, however, it is possible that 1) Adoption rates could be higher if these options were available. For example, I purposely do not use Azure VPN because I can't scale down when I don't need it and I'm not willing to write my own scripting for it. 2) The improved efficiency/usage of the Azure network adds more value out of every CPU cycle. 3) No company survives the long term by charging for something that adds NO value. In order to survive the long-term, you have to constantly be pushing the value proposition to customers and NOT charging them for something they're not using. 4) The wastefulness of unused resources at cloud scale is destructive 5) The customer satisfaction of getting good value out of the product re-wins them over every day.
Would be a good feature, no matter if IP change if you are using DNS. IP fees would be cheaper.
I thought I could stop the VPN service and not accrue charges.