Retirement Announcement - Basic SKU Public IP addresses will be retired on 30 September 2025

ChaitanyaNaykodi-MSFT 26,536 Microsoft Employee

Basic SKU Public IP addresses will be deprecated on September 30, 2025. Below are timelines to keep in mind for deprecation:

March 31, 2025 - Last day to create new Basic SKU Public IP addresses. After this date, you will not be able to create new Basic SKU Public IP addresses. Basic SKU Public IP addresses created prior to this date will continue to work.

September 30, 2025 - Retirement Day of Basic SKU Public IP addresses. After this date, you will not be able to use Basic SKU Public IP addresses.

Please note that this retirement will not affect customers that are on Azure Cloud Services (extended support).

Francesco 16 Reputation points

2022-10-03T16:36:28.047+00:00

Does this change affect dynamic IPv4 adrresses as well, or just static IPv4?
As I see in the specs that no standard SKU is forseen for dynamic IPv4.
ChaitanyaNaykodi-MSFT 26,536 Reputation points Microsoft Employee

2022-10-04T21:36:45.877+00:00

Hello @Francesco ,

Both static and dynamic allocated Basic SKU Public IP addresses will be deprecated.
Mark-i 31 Reputation points

2022-10-05T01:33:50.49+00:00

I am using a static public IP address for the Basic SKU.
If I upgrade to Standard, will my current IP address change?
Francesco 16 Reputation points

2022-10-05T13:20:42.81+00:00

Thanks @ChaitanyaNaykodi-MSFT , but in the MS docs describing the upgrade stps it's noted that dynamic IPs cannot be upgraded to standard SKU (https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/public-ip-upgrade-portal).
Also, some resources like Virtual Network Gateways only support dynamic IPs, so there is no way to upgrade it.
ChaitanyaNaykodi-MSFT 26,536 Reputation points Microsoft Employee

2022-10-10T15:48:25.707+00:00

Hello @Mark-i ,
No, the IP address will not change. You can follow this guide to upgrade your IP address SKU.
ChaitanyaNaykodi-MSFT 26,536 Reputation points Microsoft Employee

2022-10-10T15:53:52.46+00:00

Hello @Francesco ,

Apologies for the delay here. For basic sku of Virtual Network Gateways, the current work around is to recreate a new VPNGW with a non-Basic VPNGW SKU. The team is still working on finalizing this migration and will provide an update.
Francesco 16 Reputation points

2022-10-12T15:07:37.047+00:00

Thanks @ChaitanyaNaykodi-MSFT , but I'm still missing one point. Currently, Dymanic IPs don't have a standard SKU. Dues this mean that from 2025 they won't exist anymore?
Or a new Dynamic Standard SKU is going to be introduced?

Additionally, when a Dynamic IP is detached to be upgraded (if possible) will it change it's IP address?
Jason Miller 1 Reputation point

2022-10-14T19:24:13.177+00:00

Does this apply to those who deploy virtual machines into the DevTestLabs feature? We have a Azure DevOps pipeline that deploys a VM into the DevTestLabs area of Azure. It would seem cumbersome and wasteful to have to get an IP address for every VM we deploy there. Right now we could have a total of 9 VMs that could be deployed at any given time due to multiple version of windows testing, service manager testing and other various variables.

thanks.
Carlos Duran 1 Reputation point

2022-12-12T21:34:21.433+00:00

Hi, we are using Azure Cloud Services Classic and we are working on the migration to Cloud Services Extended Support, but I have concerns about the retirement of the basic SKU Public IP, currently in our solution we have unused Reserved public IP classic in case for disaster recovery plans for the azure cloud service, and we are going to migrate them to Basic SKU when we finish the migration of cloud services classic to extended, but after the retirement of basic SKU IP can we still have those unused IPs available without an active cloud service (extended)?
Kyle Daley 6 Reputation points

2023-01-18T16:04:41.37+00:00

Like Francesco mentioned, Basic Dynamic IPs cannot be upgraded. Attempting to do so results in a StandardSkuPublicIPAddressesMustBeStatic error.

Cloud Services (extended support) with only a worker role requires the use of a dynamic IP. It does not make sense to create a static IP for a worker role.

Please advise.
Kyle Daley 6 Reputation points

2023-01-18T16:39:03.14+00:00

Well, this is fun. Just attempted to deploy a Cloud Service (extended support) to a Standard Public IP and received the following error: StandardPublicIPAddressNotSupportedCloudService

It would appear that MSFT is not prepared for us to truly migrate to Standard SKU IPs.
Rudolph, Brian 5 Reputation points

2023-09-29T13:13:21.9533333+00:00

We currently use a VWAN with a secured hub. All Internet bound traffic is 'forced' through the FW. Will this constitute as an "explicit method of outbound connectivity"? We consider this to be true but want clarity.
veliko.ivanov 1 Reputation point

2023-10-02T16:01:38.4+00:00

Hi,

What about Application Gateway v1 between 30 September 2025 and 28 April 2026 (The current data for Application Gateway v1 deprecation) since it is using exactly this IP address tier/SKU?
Ricardo Del Rio Fuente 5 Reputation points

2023-10-05T11:21:18.4666667+00:00
Regarding the "default outbound access for VMs in Azure will be retired—transition existing VMs to a new method of internet access" email notification sent out, it links to this Q&A for reference. However default outbound access doesn't seem to have much to do with Basc/Standard Public IP SKUs...

Can you please clarify -

How does one diagnose which VMs are using 'default outbound access' and,

Is updating the public IP SKU from basic to standard sufficient to mitigate against retirement of 'default outbound access for VMs?'
JulianPerkins-3256 0 Reputation points

2023-10-05T16:54:11.8433333+00:00

I would also like clarity around a secured vWAN hub that is deployed with Azure Firewall. Our understanding is outbound Internet traffic is routed to the Azure Firewall instance and NAT is accomplished there which should in effect act as a NAT gateway and provide an "explicit outbound access" method?
Billy O'Neal (vcpkg) 0 Reputation points Microsoft Employee

2023-10-05T20:18:57.7133333+00:00

In addition to the 'we don't care what IP we get so why are we getting a fixed one allocated' statements above, does this mean we're now going to get double charged for bandwidth to the NAT and then from the NAT to the internet, or is the traffic to the NAT the traffic that counts?
Alex Anders 0 Reputation points Microsoft Employee

2023-11-16T20:24:43.8866667+00:00

Does this apply just to VMs or any service that is VNet integrated, such as App Service?
Rick Sparks 10 Reputation points

2024-02-08T11:17:27.4133333+00:00

Has there been any update on this:
"Apologies for the delay here. For basic sku of Virtual Network Gateways, the current work around is to recreate a new VPNGW with a non-Basic VPNGW SKU. The team is still working on finalizing this migration and will provide an update."

I have two VPNGW with Basic Sku public IPs (set to dynamic). One is VpnGw2 and one is VpnGw1. I am being offered the upgrade prompt which I thought should not be the case:

Will this work or is the process still to create a new VPNGW and then copy all of the VPN configuration to the new one. It is pretty important to know that the public IP will not change if the old VPNGW is removed as all of the remote endpoints would need to be reconfigured which would be pretty cumbersome.
Roy Hekkert 5 Reputation points

2024-02-08T12:19:25.38+00:00

Exactly the same situation as Rick Sparks has, how can we upgrade our Basic public IP which is binded to our Virtual Netwerk Gateway to a Standard SKU?
Jamie Butt 45 Reputation points

2024-02-08T21:41:00.6066667+00:00

So dynamic IP assignments are no longer available?
Hank Pace 0 Reputation points

2024-02-08T23:25:35.0566667+00:00

Same ask Rick. To upgrade an IP attached to a VNG, it takes creating a new VNG? Will that change the IP? Is there a way to preserve the IP and upgrade?
Jonas Züger 0 Reputation points

2024-02-29T18:24:23.4966667+00:00

Would it be possible to upgrade using the same IP?
Jason Miller 1 Reputation point

2024-04-11T17:20:19.03+00:00

How does this affect azure lab vms that are spun up and broken down on a need to need basis?
Chao Yan 60 Reputation points Microsoft Employee

2024-05-07T10:05:37.5233333+00:00

In official documents https://azure.microsoft.com/en-us/updates/default-outbound-access-for-vms-in-azure-will-be-retired-transition-to-a-new-method-of-internet-access/. It says "Your existing VMs that use default outbound access will continue to work after this retirement". Does it mean all VMs created before 30 September 2025 can still use default outbound access after 30 September 2025?
Luis Esteban 0 Reputation points

2024-09-10T11:50:54.8533333+00:00

Any update on migration for Virtual Network Gateways?
Gary B 0 Reputation points

2024-11-22T11:13:37.7566667+00:00

The Cloud Service (Extended support) work well for my products. Whilst you've confirmed that these will continue to run, does that mean that it will not be possible to make new Cloud Services?

Are there also plans to allow the Standard public IP addresses for Cloud Services and what is the current limitation preventing that at the moment?
MSDN_userSince1994_newaccount2023 0 Reputation points

2024-11-22T11:14:16.7766667+00:00

Today, Nov 22, 2024 at 10:39:15 UTC (exit time from a sending server), you suddenly sent me (on a previously used mail address) a notification about this change on a previously used e-mail. I have no idea which IPs you are writing about and the notification doesn't say anything specific, such as the Azure location or actual numeric IP address . This "page" seems to not have been updated since 2022 and the mail unhelpfully links here via an aka.ms shortlink and forced me to recreate my Q&A "profile" to even comment this. Microsoft customer facing systems are clearly falling into serious disrepair since Balmer left .
Kindred Dev 21 Reputation points

2024-11-22T18:19:54.0266667+00:00

To clarify, since it is indicated that this retirement won't apply to IPs on Azure Cloud Services (extended support), does this mean that only those Basic Public IP Addresses that are currently tied to a Cloud Service are excluded, or is this exclusion on a subscription basis if a cloud service is deployed?
tstrong 45 Reputation points

2024-11-22T22:02:21.51+00:00

I am using a Virtual Network Gateway. Type = VPN, SKU = Basic. It uses a Public IP with the Basic SKU. It is my understanding that a Basic VPN can only use an IP with a basic SKU. If that is the case, does the below information mean that we will be able to use a Basic VPN with an IP that has a SKU of Standard?

MS website says, "VPN Gateway (using Basic IPs) A migration path will be provided in the future. When this migration path is available, we'll update this decision path with migration information and send out a service health alert."

3 answers

ChaitanyaNaykodi-MSFT 26,536 Reputation points Microsoft Employee

2022-10-03T15:23:04.41+00:00

To migrate to Standard SKU Public IP addresses, please follow the instructions here.

If you have any additional questions regarding this retirement, please comment on this thread to ask your specific questions and we will try our best to answer. Thank you!
Please sign in to rate this answer.

1 person found this answer helpful.
jjisge 1 Reputation point

2022-12-04T15:45:50.863+00:00

Hi, I would like to know why Microsoft is
retiring Basic SKU public IP

veliko.ivanov 1 Reputation point

2023-10-02T14:55:07.72+00:00

Hi,

What about Application Gateway v1 between 30 September 2025 and 28 April 2026 (The current data for Application Gateway v1 deprecation) since it is using exactly this IP address tier/SKU?

武男牛島 0 Reputation points

2024-02-06T08:24:42.2066667+00:00

Hello.

When deploying with Visual Studio 2019's Publish (Extended Support), If you specify NetworkConfiguration in the service configuration file (*.cscfg), Basic static public IP address will be created.

Is this behavior still valid after September 30, 2025?

tstrong 45 Reputation points

2024-02-08T17:12:19.5333333+00:00

I'm using a Gen1 Basic VPN Gateway. It is my understanding that a Standard SKU IP will not work with a Basic VPN. What's the workaround for this? Thanks.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Todd Stevens 5 Reputation points

2024-11-22T11:08:51.9+00:00

As far as I can tell this seems to be purely a money grab. There is virtually no difference between basic and standard SKUs except the 6x cost increase. Anyone care to comment?
Please sign in to rate this answer.

1 person found this answer helpful.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Ankamma Chowdary Yerrah 0 Reputation points

2024-02-23T05:44:11.3533333+00:00

What is cost increase when we Upgrading a basic public IP address to Standard SKU...? I did not find any right article to review the cost.

Can someone help on it ..?
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Retirement Announcement - Basic SKU Public IP addresses will be retired on 30 September 2025

3 answers

Your answer