Option to use Standard Public IP with VPN Gateway Basic SKU creation

Thank you for submitting your feature request—we truly value input from our community.

Next steps:
     • We will review your request and update its status as it progresses through our evaluation process.
     • If any clarification is needed, we'll follow up with you directly in the comments.

We also encourage the community to influence our decision through comments, votes, and feedback.

Agree 100%.

This request is critical.

When a new customer is onboarded and is created a VPNGateway in Nerdio, a Basic Public IP SKU object is still created by default. But this object will be deprecated next month, on September 30, 2025.

Please replace the creation of a "Default Basic SKU Public IP" object with a "Standard SKU Public IP" object as soon as possible, or in a month all customers who created a VPNGateway using Nerdio will be experiencing VPN issues. 

NOTE: Currently, the only option available to not be affected on September 30, is to delete the VPNGateway created by Nerdio (process who will delete the Public IP associated too, without ask you first) and then manually create a new VPNGateway (Standard SKU) + Public IP (Standard SKU) in Azure to be able to use it later in Nerdio.

I have spent quite a few hours now looking for a good process to “migrate” the Basic VPN/Basic IP SKU.  I have about 30 of these to go through across our clients.  I was waiting on Microsoft's migration path announcement at the end of July but was quite let down that only the higher SKU's have a migration path and now I'm in a time crunch.  

I have to say I am pretty upset, not with NERDIO, with the chaos this created.  I have narrowed down a few PowerShell commands to run after manually deleting Azure resources to get the Basic VPN back with a Standard IP but there are some “gotchas” between regions with Zone redundancy for IPs or not.  

I would be GREAT if NMM had the extra option to create the VPN Basic SKU with Standard IP.  Right now I am looking at doing this manually inside each Azure Tenant so that my other techs can “easily” get through my list.  

Just an update to the process…unrelated to the option(s) in NMM.  

I deployed several VPN Gateway's using PowerShell and forced the Basic SKU vpn gateway to be created with a Standard SKU Public IP address (created separately).  Initially they all were created and connected the VPN tunnel fine but every one that i deployed would eventually stop passing traffic and the only “fix” would be to reset the VPN which would only last for a few hours before the same thing would happen.  

I have since gone to just using the higher vpngw1 SKU at least for now and will check back after the Sept. 30 deadline to see if anything changes. 

If the combo of Standard IP and Basic VPN is not stable, probably no reason to have this feature in NMM