Upgrade from Basic to Standard SKU public IP addresses in Azure by 30 September 2025

SafiyullahSA 65 Reputation points
2024-03-28T21:42:05.35+00:00

Hi All,

I have a VPN Gateway in my environment, It is a standard SKU. The VPN gateway having a Public IP which is basic SKU with IP as (20.x.x.122) and having Dynamic IP address assignment. How can I make it as Static assignment without change the IP address (20.x.x.122) ? If I didn't do upgrade activity before 30 Sept 2025, What could be worst scenario happen?

Azure VPN Gateway
Azure VPN Gateway
An Azure service that enables the connection of on-premises networks to Azure through site-to-site virtual private networks.
1,370 questions
{count} votes

Accepted answer
  1. GitaraniSharma-MSFT 47,011 Reputation points Microsoft Employee
    2024-04-01T14:10:12.9566667+00:00

    Hello @Safiyullah S A ,

    Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well.

    I understand that you've an Azure VPN gateway with Basic SKU Public IP with dynamic IP address assignment. You would like to make it Static without changing the IP address and would also like to know what will happen if you don't upgrade the IP before 30 Sept 2025.

    The VPN gateway having a Public IP which is basic SKU with IP as (20.x.x.122) and having Dynamic IP address assignment. How can I make it as Static assignment without change the IP address (20.x.x.122)?

    As per the Azure VPN documentation,

    The Standard and High-Performance SKUs will be deprecated on September 30, 2025. The product team will make a migration path available for these SKUs by November 30, 2024. At this time, there's no action that you need to take.

    Refer: https://learn.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-about-skus-legacy#sku-deprecation

    So, even if you are able to change the IP assignment from dynamic to static, it will be of no help as the Standard SKU itself is going to be deprecated. So, the only option you have would be to upgrade to a new VPN SKU and this involves both downtime and IP address change.

    Refer: https://learn.microsoft.com/en-us/azure/vpn-gateway/about-gateway-skus#considerations

    If I didn't do upgrade activity before 30 Sept 2025, what could be worst scenario happen?

    As mentioned in our Azure VPN document and FAQs,

    We're taking action to ensure the continued operation of deployed VPN gateways that utilize Basic SKU public IP addresses. If you already have VPN gateways with Basic SKU public IP addresses, there's no need for you to take any action.

    However, it's important to note that Basic SKU public IP addresses are being phased out. Going forward, when creating a new VPN gateway, you must use the Standard SKU public IP address. Further details on the retirement of Basic SKU public IP addresses can be found here.

    Refer: https://learn.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-vpn-faq#how-does-public-ip-address-basic-sku-retirement-affect-my-vpn-gateways

    The Azure VPN Product Group team is working on a migration plan that will be communicated soon. So, for now, you can wait for the announcement without making any changes to your VPN gateway.

    Kindly let us know if the above helps or you need further assistance on this issue.


    Please "Accept the answer" if the information helped you. This will help us and others in the community as well.


1 additional answer

Sort by: Most helpful
  1. Marcin Policht 9,505 Reputation points MVP
    2024-03-28T22:07:07.91+00:00

    The upgrade guidance is provided at https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/public-ip-basic-upgrade-guidance , however, as that documentation states Azure Firewall does not support Basic SKU - so it appears that the information you have is incorrect.


    hth

    Marcin