Can I Deploy a Basic VPN Gateway in Brazil South?
Asked by
TechWizard42
I'm trying to set up a Basic VPN Gateway in the Azure Portal for Brazil South, but I'm hitting some obstacles. The only options available seem to be higher SKUs like VpnGw1, which costs around โฌ140 a month. Meanwhile, the Basic VPN Gateway is priced at around โฌ25 and is what most small to medium-sized enterprises need. I know I can create the Basic SKU using PowerShell, but I'm stuck because:
- The Basic VPN Gateway only works with a Public IP SKU Basic, but I can't create new Basic Public IPs in Brazil South since only Standard is available.
- If I try to use a Standard Public IP, the setup fails because the Basic Gateway doesn't support it.
So, I can't deploy a Basic VPN Gateway in this region. Has anyone encountered a similar issue? Is there a workaround or is this feature just not supported in Brazil South anymore?
Answers
I read that while Basic SKU public IPs are end of life, Basic VPN Gateways might still be available for now. I have a couple of them running with Basic IPs, but I might need to upgrade. I heard that Standard SKU IPs are now supported on Basic VPN Gateways, so I'll give that a shot and let you know how it goes later.
Reply to this answer
It seems like Basic public IPs are being phased out, which might explain your issue. They're likely deprecating the Basic VPN Gateway around the same time, especially considering the recent changes.
Reply to this answer
From what I remember, if you use the Basic SKU and later want to upgrade to a higher SKU, you'll have to destroy the existing Basic SKU setup. This means your VPN connections will be down during that transition, so keep that in mind when choosing.
Reply to this answer
You might want to consider a virtual firewall as a cheaper alternative to the VpnGw1. It could replace the need for that if you're just looking to save costs without compromising much on functionality.
Reply to this answer
Both the Basic Public IP SKU and the Basic VPN Gateway SKU are being retired soon. That's probably why you're unable to select them in your setup.
Reply to this answer
Are you trying to set this up through the GUI or PowerShell? It might make a difference in seeing if you can get it to work better.
Reply to this answer
Add your answer
Answers are reviewed before publication.
Related Discussions