Basic SKU Public IP Adresses + Basic SKU VPN Gateway - depreciation

Mirosław Łabuz 20 Reputation points
2025-08-11T12:08:21.9066667+00:00

Hi,

We got an email notification asking us to upgrade Basic SKU Public IP adresses in Azure by 30 September 2025:

User's image

However in our case those public IP adresses are associated with VPN Gateways - also Basic SKU.

I am reading the following news on VPN gateway site https://learn.microsoft.com/en-us/azure/vpn-gateway/whats-new#upcoming-projected-changes
User's image

Does it mean that in our case there will be a "Migration Tool" provided Sept / Oct 2025 ?

I would grately appreciate some clarification on the process in our case.

Thank you.

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.
0 comments No comments
{count} votes

Accepted answer
  1. Praveen Bandaru 6,850 Reputation points Microsoft External Staff Moderator
    2025-08-11T12:50:13.42+00:00

    Hello Mirosław Łabuz

    I see that your question concerns the migration process for Basic SKU Public IP addresses, particularly in relation to their use with Basic SKU VPN Gateways.
    The deadline to upgrade the Basic SKU Public IP used with the VPN Gateway is at the end of January 2026, so there is still some time remaining.
    User's image

    Your actual IP address will not change, and connectivity will not be interrupted.

    • An automated capability to remove the Basic public IP from your gateway will be available in Sept/Oct 2025
    • Deprecation timeline of Basic IP for all VPN Gateways is moved from Sep 2025 to end of Jan 2026
    • Because Microsoft is retiring Basic public IP resources, we’re updating the Basic VPN Gateway construct. You’ll see the Basic public IP reference as an attribute on your virtual network gateway.
    • If you have scripts, ARM templates, or monitoring solutions that reference the Basic public IP resource, update them to use the IP address property of the virtual network gateway instead.
    • An automated migration tool should be available by September, so it is advisable to wait until then before starting the migration.

    Check the document for more understanding:https://learn.microsoft.com/en-us/azure/vpn-gateway/whats-new#upcoming-projected-changes


    Hope the above answer helps! Please let us know do you have any further queries.

    Please do not forget to "accept answer" and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

    1 person found this answer helpful.
    0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.