Basic SKU public IP addresses will be retired in Azure

Osama Khan 0 Reputation points
2025-09-19T11:32:03.4466667+00:00

I’ve had communication from Microsoft that they are retiring their “basic” form of public IP addresses in Azure.

On the links recieved it says:

"On 30 September 2025, Basic SKU public IP addresses will be retired in Azure. You can continue to use your existing Basic SKU public IP addresses until then, however, you'll no longer be able to create new ones after 31 March 2025."

Does this mean that I don't have to change anything on my current VMs with public IP address, only that I cannot create new one even after 30th September?

Azure Virtual Machines
Azure Virtual Machines

An Azure service that is used to provision Windows and Linux virtual machines.

0 comments No comments

2 answers

Sort by: Most helpful
  1. TP 162.1K Reputation points Volunteer Moderator
    2025-09-19T11:48:30.69+00:00

    Hi Osama,

    You need to upgrade the Basic Public IPs that are associated with your current VMs by September 30th in order to avoid service disruption.

    Below are instructions for upgrading the Basic SKU Dynamic Public IP associated to VM interface. You'll want to schedule this during off hours since there will be brief interruption of network traffic.

    In my experience the Public IP address is retained if you switch to Static first. There should be no need to update DNS records. Process only takes a couple of minutes.

    1. Please navigate to the Basic Public IP address -- Settings -- Configuration, select Static, click Save.

    User's image

    After several seconds you should see notification in upper right corner saying that it saved public IP changes.

    User's image

    A message will show up at top saying that "This public IP address can't be updated because it is associated to the IP configuration..", that's normal.

    2. Click on Overview blade on left, next click on Properties tab and verify it still says Static. Hit F5 to refresh the page, and double-check Properties tab again (still should say Static).

    User's image

    3. Now you are ready to click Dissociate, make note of your VM's network interface name, then click Yes to confirm. Network activity from public Internet to your VM will be interrupted at this point.

    User's image

    User's image

    User's image

    4. Once that's done click the Upgrade to Standard SKU link at top, check box and Yes. Typically only takes seconds to upgrade, look for notification in upper right.

    User's image

    User's image

    User's image

    5. When upgrade has finished, click Associate , select Resource type: Network interface and select your VM's network interface from the dropdown, and click OK. This is where the note you made above with your VM's network interface name will be helpful.

    User's image

    Please click Accept Answer and upvote if the above was helpful.

    Thanks.

    -TP

    Was this answer helpful?

    0 comments No comments

  2. Marcin Policht 103.7K Reputation points MVP Volunteer Moderator
    2025-09-19T11:38:08.44+00:00

    Up until 30 September 2025 you can continue using your current Basic SKU public IP(s) as-is: nothing needs to change immediately just because of this retirement notice. However, after 30 September 2025 the Basic SKU IPs are officially retired. That means they will no longer be supported and will become unusable for non-Cloud Services (extended support) resources. If they haven't been upgraded by then, you risk service disruptions or losing that IP functionality. You'll also lose the ability to upgrade them after that date. After retirement date, upgrades from Basic → Standard won't be supported.

    There are some exceptions and special cases. If your Basic SKU public IP addresses are part of Azure Cloud Services (extended support), those deployments are not impacted by this retirement. For some resources (e.g. VPN Gateways using Basic public IPs), there is a migration path, but sometimes with caveats (preview features, region availability, possible downtime)

    To avoid surprises and downtime, here's how you should respond:

    1. Inventory all your Basic SKU public IPs. Determine which ones are attached to VMs, Load Balancers, VPN Gateways, etc.
    2. Plan upgrade/migration to Standard SKU for each of them. Microsoft provides scripts/tools and guidance to upgrade while keeping the same IP address in many cases.
    3. Mitigate downtime—some upgrades may require temporarily disassociating the IP from the resource.
    4. Update dependencies — monitoring, ARM templates, scripts, DNS entries etc., if they refer to the Basic PIP resource, as after migration things may behave a little differently.
    5. Budget & cost — Standard SKUs may cost more (depending on features like zones, redundancy, etc.).

    For more info, refer to https://learn.microsoft.com/en-us/answers/questions/1025889/action-required-upgrade-from-basic-to-standard-sku, https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/public-ip-basic-upgrade-guidance, https://learn.microsoft.com/en-us/answers/questions/5521244/deprecation-impact-on-basic-sku-public-ips-after-s


    If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

    hth

    Marcin

    Was this answer helpful?

    0 comments No comments

Your answer

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