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 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.
Fabiano Martins commented
Agreed. Please, thanks.
Francesco Pasqualetti commented
Yes, it's a must-have feature...
John Jenkins commented
Still waiting for this, seriously c'mon?
Alex Figueiredo commented
2019, 5 years and still no changes. Pay-as-you-go still #fails
[Deleted User] commented
"We’ve moved this ask to the backlog due to technical challenges in reserving Public IP addresses during stop state."
Really? we pay for a reserved ip and for a vpn only when in use, not always, you must be joking!
No problem to pay for reserved ip address. That will still cheaper than running gateway during nights and weekend.
Linz Mathew commented
@Admin, Not sure what is the confusion on Public IP Address to implement this request.
If the public IP address is static, you cannot release it even though the gateway is stopped and you must continue billing for the static public IP address.
If the public IP address is dynamic, it is understood that the IP address will be released and we will get a new IP when the Gateway is started again.
Paying for a Public static IP address makes sense than paying for gateway when gateway is not used at all.
Mark P commented
1581 technicians (and counting) requesting this feature should be enough for MS to set a reasonable priority on resolution. Surely, you can solve reserving the IP address. As stated 1581 times, this is high $'s for low use. Why not make a bold move & bring down the cost while you are working to resolve?
Yep this is ********. Such costs are pure profit targeting. My client needs just casual access to their Windows 2016 server while on business trips and on the weekends. Less than 20 hours a month yet to have this feature he's having to pay $200/month!! Like WHAT THE F%$K Microsoft.
My Maschin run 275 horus per month... the Gatway works for 743 hours ?!
pay for 500 hours and no traffic in this time ;-(
B2ms - Europa, Westen 275,97 275,97 22,34
Basic-Gateway - VPN Gateway 743,92 743,92 22,58
Bump bump bump. Come on Azure, you are supposed to be state of the art!