On 30 June, Microsoft formally deprecated the Standard and High Performance Azure VPN Gateway SKUs: the older gateway types still sitting behind a lot of hybrid and on-premises setups that route traffic into Azure for backup, disaster recovery, or an on-premises Business Central deployment connected over a site-to-site VPN.
If your business connects to Azure this way and nobody has touched the gateway SKU in a few years, this is worth checking today rather than waiting for something to break.
What actually changes
No new gateway can be created on the Standard or High Performance SKU from now on. For gateways already running on them, Microsoft will attempt an automatic migration after June 2026, upgrading Standard to VpnGw1AZ and High Performance to VpnGw2AZ, and performance actually improves once that happens.
The safer route
Migrate the gateway’s Basic public IP address to a Standard IP address through the Azure portal now. The SKU upgrade rides along with that migration automatically, without the same subnet-size risk.
The IP address itself does not change, but expect a short window of connectivity downtime while the gateway is recreated, so plan the change outside business hours rather than in the middle of a trading day.
Why this is in a Dynamics 365 newsletter
This is not a Dynamics 365 feature update, but it directly affects anyone running Business Central, or any other on-premises system, behind a site-to-site VPN into Azure. If Braintree manages your Azure networking, check with your account manager whether this has already been actioned for you. If you manage it yourself, this is the week to check your gateway SKU, not next quarter.
Talk to our team about what this means for your Dynamics 365 environment. Chat to a Braintree consultant or email us directly at enquiries@braintree.co.za.
Specialists in Business Applications, Modern Workplace and Azure. Let’s grow.
Sources: Microsoft Learn, “VPN Gateway Legacy SKUs” and “What’s new in Azure VPN Gateway”, both confirming the Standard and High Performance SKU deprecation date of 30 June 2026.
