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

Question

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

ChaitanyaNaykodi-MSFT 27,486 Microsoft Employee Moderator

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 26 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 27,486 Reputation points Microsoft Employee Moderator

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 61 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 26 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 27,486 Reputation points Microsoft Employee Moderator

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 27,486 Reputation points Microsoft Employee Moderator

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 26 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 11 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 11 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 20 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?
Maya Butt 45 Reputation points

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

So dynamic IP assignments are no longer available?
Hank Pace 20 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?
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 ..?
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?
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?
Gary B 5 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 26 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 50 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."
Anavi Nahar 0 Reputation points Microsoft Employee

2024-11-26T17:57:30.1133333+00:00

Pricing can be found here: https://azure.microsoft.com/en-us/pricing/details/ip-addresses/?msockid=2757027f8bc867993cf8165a8ae5661d
Anavi Nahar 0 Reputation points Microsoft Employee

2024-11-26T18:58:15.1433333+00:00

Pricing can be found here. @Ankamma Chowdary Yerrah
https://azure.microsoft.com/en-us/pricing/details/ip-addresses/?msockid=2757027f8bc867993cf8165a8ae5661d#pricing
Anavi Nahar 0 Reputation points Microsoft Employee

2024-11-26T18:59:54.98+00:00

Hi @Todd Stevens - Basic SKU is not built for large production workloads to run while withstanding zonal failures. It is also missing monitoring capabilities. As a result, we are retiring Basic SKU.
ChaitanyaNaykodi-MSFT 27,486 Reputation points Microsoft Employee Moderator

2024-11-26T20:14:19.3966667+00:00

@Rudolph, Brian
Thank you for reaching out

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.

Yes it will constitute as an "explicit method of outbound connectivity". Azure Firewall by design only supports Standard SKU public IPs. You set-up above will not be affected by Basic IP SKU retirement and Default Outbound Access Retirement.

https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/default-outbound-access?source=docs#if-i-need-outbound-access-what-is-the-recommended-way
ChaitanyaNaykodi-MSFT 27,486 Reputation points Microsoft Employee Moderator

2024-11-26T20:22:04.8066667+00:00

@JulianPerkins-3256

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?

Yes Azure Firewall by design only supports Standard SKU public IPs. You set-up above will not be affected by Basic IP SKU retirement and Default Outbound Access Retirement.

https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/default-outbound-access?source=docs#if-i-need-outbound-access-what-is-the-recommended-way
ChaitanyaNaykodi-MSFT 27,486 Reputation points Microsoft Employee Moderator

2024-11-26T20:30:17.2866667+00:00

@Alex Anders

Does this apply just to VMs or any service that is VNet integrated, such as App Service?

The default outbound access retirement only affects the VM's more details here
https://azure.microsoft.com/en-us/updates?id=default-outbound-access-for-vms-in-azure-will-be-retired-transition-to-a-new-method-of-internet-access
VNET integrated PaaS services are not in scope as they do not use default outbound access.
ChaitanyaNaykodi-MSFT 27,486 Reputation points Microsoft Employee Moderator

2024-11-26T20:33:39.1733333+00:00

@Rick Sparks

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.

The VPN gateway team is taking action to ensure the continued operation of deployed VPN gateways that use Basic SKU public IP addresses until the retirement of Basic IP in September 2025. Before this retirement, we will provide customers with a migration path from Basic to Standard IP.

more details in the link below
https://learn.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-vpn-faq#how-does-the-retirement-of-basic-sku-public-ip-addresses-affect-my-vpn-gateways
ChaitanyaNaykodi-MSFT 27,486 Reputation points Microsoft Employee Moderator

2024-11-26T20:36:44.5466667+00:00

@Jonas Züger

Would it be possible to upgrade using the same IP?

Please go through this link

https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/public-ip-upgrade?tabs=azureportal#upgrade-public-ip-address
ChaitanyaNaykodi-MSFT 27,486 Reputation points Microsoft Employee Moderator

2024-11-26T20:39:35.29+00:00

@Luis Esteban

Any update on migration for Virtual Network Gateways?

Please take a look below, the team will update when the migration path is ready
https://learn.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-vpn-faq#how-does-the-retirement-of-basic-sku-public-ip-addresses-affect-my-vpn-gateways
ChaitanyaNaykodi-MSFT 27,486 Reputation points Microsoft Employee Moderator

2024-11-26T20:47:30.87+00:00

@Kyle Daley

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

Basic SKU public IP retirement would not impact Cloud Services Extended Support (CSES) deployments. However, we advise using Standard SKU on ARM native resources (those that do not depend on CSES) when possible, because Standard has more advantages than Basic.

https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/public-ip-basic-upgrade-guidance#will-the-basic-sku-public-ip-retirement-impact-cloud-services-extended-support-cses-deployments
ChaitanyaNaykodi-MSFT 27,486 Reputation points Microsoft Employee Moderator

2024-11-26T20:51:54.9733333+00:00

@tstrong

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?

You can find the required details here "The Basic SKU currently supports only Basic SKU public IP addresses. We're working on adding support for Standard SKU public IP addresses for the Basic SKU."

https://learn.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-vpn-faq#can-i-request-a-static-public-ip-address-for-my-vpn-gateway
ChaitanyaNaykodi-MSFT 27,486 Reputation points Microsoft Employee Moderator

2024-11-26T21:08:29.8933333+00:00

@Francesco

Or a new Dynamic Standard SKU is going to be introduced?

Basic Dynamic IPs can be converted to Standard prior to upgrading. We don't have plans to introduce dynamic IPs for Standard SKU currently.
ChaitanyaNaykodi-MSFT 27,486 Reputation points Microsoft Employee Moderator

2024-11-26T21:10:15.8+00:00

@Carlos Duran

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)?

This retirement does not impact Cloud Services Extended Support. Cloud Services Classic is already retired. However, reserved IPs can be upgraded as well. Migrate a classic reserved IP address to a public IP address - Azure Virtual Network | Microsoft Learn
ChaitanyaNaykodi-MSFT 27,486 Reputation points Microsoft Employee Moderator

2024-11-26T21:11:36.39+00:00

@veliko.ivanov

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?

Would recommend upgrading to App GW v2

https://learn.microsoft.com/en-us/azure/application-gateway/migrate-v1-v2
ChaitanyaNaykodi-MSFT 27,486 Reputation points Microsoft Employee Moderator

2024-11-26T21:16:25.7066667+00:00

@Billy O'Neal (vcpkg)

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?

There will be no change to the pricing model. Standard IPs are billed in the same manner as Basic Public IPs. There is a difference of only $0.001/hour. Please refer to pricing here: Pricing - Virtual Machine IP Address Options | Microsoft Azure
ChaitanyaNaykodi-MSFT 27,486 Reputation points Microsoft Employee Moderator

2024-11-26T21:18:24.1733333+00:00

@Chao Yan

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?

Yes, that is correct
ChaitanyaNaykodi-MSFT 27,486 Reputation points Microsoft Employee Moderator

2024-11-26T21:19:55.28+00:00

@Gary B

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?

CSES will be allowed to be created. Only ARM / non CSES basic IPs will be blocked.

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?

No this is not in the current plan. We advise using Standard SKU on ARM native resources (those that do not depend on CSES) when possible, because Standard has more advantages than Basic.
https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/public-ip-basic-upgrade-guidance#will-the-basic-sku-public-ip-retirement-impact-cloud-services-extended-support-cses-deployments
Holger Bock Axelsen 16 Reputation points

2024-11-28T16:57:32.6966667+00:00

@ChaitanyaNaykodi-MSFT ,

Can you please clarify your above answer? Assuming we don't have spare Basic SKU IP addresses lying around, does this mean that we just cannot create a new Cloud Services (Extended Support) deployment after 31 March 2025?

Not being able to deploy a new CSES is pretty affecting.
ChaitanyaNaykodi-MSFT 27,486 Reputation points Microsoft Employee Moderator

2024-12-06T17:54:34.2533333+00:00

@Holger Bock Axelsen

Thank you for reaching out.

Actually, I just edited my response above.

CSES will be allowed to be created. Only ARM / non CSES basic IPs will be blocked.
Kindred Dev 26 Reputation points

2024-12-06T18:15:02.9766667+00:00

@ChaitanyaNaykodi-MSFT , as part of my CSES deployment, I have one ARM template deploying two Basic Public IP Addresses, but the CSES resource is not deployed in the same ARM template. Will the retirement exception for CSES cover this scenario? What will happen to temporarily unassociated Basic Public IP Addresses that are routinely used for swappable deployments (e.g. I have many Basic IP Address resources that are set aside for a staging deployment)
Holger Bock Axelsen 16 Reputation points

2024-12-09T16:16:58.31+00:00

@ChaitanyaNaykodi-MSFT ,

Thanks for replying, but I don't understand: CSES is ARM-based and the IPs used in CSES are ARM Basic IPs. To deploy a CSES (with a public IP) you literally have to reference the IP in the ARM template for the CSES deployment. That's pretty hard to do if I cannot create such IPs anymore?
Jose P. Cisneros M 0 Reputation points

2025-01-19T23:54:55.13+00:00

As this will be part of the change of the default outbound connectivity be disabled as well on new deployments, will this be affecting old VNETs or only new VNETs? or it means each VM created after the change will have the default outbound connectivity disabled?
ChaitanyaNaykodi-MSFT 27,486 Reputation points Microsoft Employee Moderator

2025-01-21T17:32:02.2466667+00:00

@Jose P. Cisneros M
You can find more details about this here

https://azure.microsoft.com/en-us/updates?id=default-outbound-access-for-vms-in-azure-will-be-retired-transition-to-a-new-method-of-internet-access

On 30 September 2025, default outbound access connectivity for virtual machines in Azure will be retired. After this date, all new VMs that require internet access will need to use explicit outbound connectivity methods such as Azure NAT Gateway, Azure Load Balancer outbound rules, or a directly attached Azure public IP address.

Also

Your existing VMs that use default outbound access will continue to work after this retirement, however, we strongly recommend transitioning to an explicit outbound method

Hope this helps! Thanks!
Morné Zaayman 46 Reputation points

2025-03-06T06:42:03.09+00:00

The email states:

If you have any Basic SKU public IP addresses deployed in Azure Cloud Services (extended support), those deployments won't be affected by this retirement and you don't need to take any action for them.

What about new Cloud Services (extended support) deployments? Will we still be able to create Basic SKU public IP addresses for them?
Morné Zaayman 46 Reputation points

2025-03-06T06:48:51.8233333+00:00

The email states:

If you have any Basic SKU public IP addresses deployed in Azure Cloud Services (extended support), those deployments won't be affected by this retirement and you don't need to take any action for them.

What about new Cloud Services (extended support) deployments? Will we still be able to create Basic SKU public IP addresses for them?
Arnel Joaquin 40 Reputation points

2025-03-06T15:06:25.5966667+00:00

If I follow the instructions to upgrade from Basic to Standard. Is our current static ip addresses going to change? Is it going to break users access once we convert/upgrade? Is there any down time?
Steven Lewin 0 Reputation points

2025-03-07T12:04:12.3533333+00:00

Hi.

What will happen if we do nothing and are not planning to add any more Basic SKU IP's to our environment will anything stop working?

Thanks

Steven
Ojas Chopade (LTIMINDTREE LIMITED) 0 Reputation points Microsoft External Staff

2025-03-11T09:03:17.56+00:00

Does this change impact automatically created VM's by Databricks resource in Azure? If yes, do we have to establish explicit outbound access after the VM is created by databricks resource?
EPNAdam 115 Reputation points

2025-03-19T14:45:36.7866667+00:00

Following. Have the same question.
Namrata Soni 0 Reputation points

2025-03-19T16:43:39.6166667+00:00

For what reason has it been removed?
Coughtry, Ben 0 Reputation points

2025-03-20T22:50:30.04+00:00

Hello Microsoft, please excuse the multiple questions on this post, but can you please confirm the following?

Stand alone VM PIP Sku upgrade powershell script:
https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/public-ip-upgrade-vm

Availability Set VMs PIP Sku upgrade powershell script:
https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/public-ip-upgrade-availability-set

Load Balancer PIP Sku upgrade - upgrade the entire LB sku via script to also upgrade PIP sku?:
https://learn.microsoft.com/en-us/azure/load-balancer/upgrade-basic-standard-with-powershell

ExpressRoute Gateway - Use ER Gateway Sku Migration wizard via Portal. This process appears to create a new PIP - is there no way to retain the existing public /32 IP address?
https://learn.microsoft.com/en-us/azure/expressroute/gateway-migration

VPN Gateway - MS does not have an upgrade path for VPN Gateway PIP Sku yet? Roughly when can one be expected?

Application Gateway PIP sku upgrade: Upgrade the SKU of the gateway itself to also upgrade PIP sku?
https://learn.microsoft.com/en-us/azure/application-gateway/migrate-v1-v2

Please let me know the answers to the above questions. Thanks so much!
ChaitanyaNaykodi-MSFT 27,486 Reputation points Microsoft Employee Moderator

2025-03-27T21:08:53.84+00:00

@Morné Zaayman ,

Thank you for reaching out. Can you please let me know what new Cloud Services (extended support) deployments you will be doing? So that I can make sure I understood your question.

As per the announcement
https://azure.microsoft.com/en-us/updates?id=upgrade-to-standard-sku-public-ip-addresses-in-azure-by-30-september-2025-basic-sku-will-be-retired

If you have any Basic SKU public IP addresses deployed in Azure Cloud Services (extended support), those deployments will not be affected by this retirement and you don't need to take any action for them.

More details here

https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/public-ip-basic-upgrade-guidance#will-the-basic-sku-public-ip-retirement-impact-cloud-services-extended-support-cses-deployments

Thank you!
ChaitanyaNaykodi-MSFT 27,486 Reputation points Microsoft Employee Moderator

2025-03-27T21:21:44.95+00:00

@Steven Lewin

What will happen if we do nothing and are not planning to add any more Basic SKU IP's to our environment will anything stop working?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.

You can follow this guideline to upgrade the IP SKU

https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/public-ip-basic-upgrade-guidance

Thanks!
ChaitanyaNaykodi-MSFT 27,486 Reputation points Microsoft Employee Moderator

2025-03-27T21:22:42.2433333+00:00

@Steven Lewin

What will happen if we do nothing and are not planning to add any more Basic SKU IP's to our environment will anything stop working?

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.
You can follow this guideline to upgrade the IP SKU

https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/public-ip-basic-upgrade-guidance

Thanks!
Morné Zaayman 46 Reputation points

2025-03-28T12:22:21.3366667+00:00
@ChaitanyaNaykodi-MSFT

Thank you for reaching out. Can you please let me know what new Cloud Services (extended support) deployments you will be doing? So that I can make sure I understood your question

There are two scenarios:

When updating our Cloud Service, we first deploy a new Cloud Service resource and then swap the IP addresses with the currently deployed Cloud Service resource.

We occasionally have to set up completely new Cloud Service resources for customers who have purchased our product. This also entails creating a new resource group in a new subscription with new resources for everything the Cloud Service requires, including IP Addresses.
ChaitanyaNaykodi-MSFT 27,486 Reputation points Microsoft Employee Moderator

2025-03-28T15:01:38.8266667+00:00

@Arnel Joaquin

If I follow the instructions to upgrade from Basic to Standard. Is our current static ip addresses going to change? Is it going to break users access once we convert/upgrade? Is there any down time?

Since IP address is static, Upgrading a public IP resource retains the IP address. More details here https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/public-ip-upgrade?tabs=azureportal#upgrade-public-ip-address

Since the IP address will be retained I do not see any reason why user access will get affected, but there will be a downtime as you will have to diss-associate the IP address. You can refer the link above for more details. Thanks!
ChaitanyaNaykodi-MSFT 27,486 Reputation points Microsoft Employee Moderator

2025-03-28T15:03:22.8866667+00:00

@Ojas Chopade (LTIMINDTREE LIMITED) , @EPNAdam

Databricks related question is answered here

https://learn.microsoft.com/en-us/answers/questions/2123428/basic-sku-public-ip-retirement-databricks-query
ChaitanyaNaykodi-MSFT 27,486 Reputation points Microsoft Employee Moderator

2025-04-01T14:18:51.4766667+00:00

@Morné Zaayman

You can find the details about new Cloud Services Extended Support (CSES) deployments here
https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/public-ip-basic-upgrade-guidance#will-the-basic-sku-public-ip-retirement-impact-cloud-services-extended-support-cses-deployments

No, this retirement will not impact your existing or new deployments on CSES.

Thank you!
Venkatesh Kacham 6 Reputation points Microsoft Employee

2025-04-17T13:11:25.2566667+00:00

PrivateSubnetSetting.pdf

I have checked the checkbox "Enable Private Subnet" in my subnet and saved. It persists and shows when the subnet config is closed and re-opened.

But, the checkbox remains unchecked when navigated to subnet from the AppService Virtual network configuration.

Attached screenshots with evidence.
Yaniv Shmulevich 0 Reputation points

2025-07-16T13:18:43.93+00:00

Hi.
What is the impact of this change, on all my Azure live, Production environments?
Ming Yu 40 Reputation points

2025-07-16T19:53:37.75+00:00

According to https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/virtual-network-public-ip-address#view-modify-settings-for-or-delete-a-public-ip-address:

Can someone help understand what is means "they cannot be associated with an azure resource that is either zone-redundant or tied to a pre-specified zone in regions where this is offered"?

We have a bunch of azure VMs using public IPs of basic SKU; some of the VMs are associated with an azure zone and some not.

Does the verbiage mean that, after the IPs are upgraded to standard SKU, they won't be able to be associated with VMs, which are not associated with an azure zone?

Thanks for the clarification!

3 answers

Your answer

Francesco 26 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 27,486 Reputation points Microsoft Employee Moderator

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 61 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 26 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 27,486 Reputation points Microsoft Employee Moderator

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 27,486 Reputation points Microsoft Employee Moderator

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 26 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 11 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 11 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 20 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?
Maya Butt 45 Reputation points

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

So dynamic IP assignments are no longer available?
Hank Pace 20 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?
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 ..?
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?
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?
Gary B 5 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 26 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 50 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."
Anavi Nahar 0 Reputation points Microsoft Employee

2024-11-26T17:57:30.1133333+00:00

Pricing can be found here: https://azure.microsoft.com/en-us/pricing/details/ip-addresses/?msockid=2757027f8bc867993cf8165a8ae5661d
Anavi Nahar 0 Reputation points Microsoft Employee

2024-11-26T18:58:15.1433333+00:00

Pricing can be found here. @Ankamma Chowdary Yerrah
https://azure.microsoft.com/en-us/pricing/details/ip-addresses/?msockid=2757027f8bc867993cf8165a8ae5661d#pricing
Anavi Nahar 0 Reputation points Microsoft Employee

2024-11-26T18:59:54.98+00:00

Hi @Todd Stevens - Basic SKU is not built for large production workloads to run while withstanding zonal failures. It is also missing monitoring capabilities. As a result, we are retiring Basic SKU.
ChaitanyaNaykodi-MSFT 27,486 Reputation points Microsoft Employee Moderator

2024-11-26T20:14:19.3966667+00:00

@Rudolph, Brian
Thank you for reaching out

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.

Yes it will constitute as an "explicit method of outbound connectivity". Azure Firewall by design only supports Standard SKU public IPs. You set-up above will not be affected by Basic IP SKU retirement and Default Outbound Access Retirement.

https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/default-outbound-access?source=docs#if-i-need-outbound-access-what-is-the-recommended-way
ChaitanyaNaykodi-MSFT 27,486 Reputation points Microsoft Employee Moderator

2024-11-26T20:22:04.8066667+00:00

@JulianPerkins-3256

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?

Yes Azure Firewall by design only supports Standard SKU public IPs. You set-up above will not be affected by Basic IP SKU retirement and Default Outbound Access Retirement.

https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/default-outbound-access?source=docs#if-i-need-outbound-access-what-is-the-recommended-way
ChaitanyaNaykodi-MSFT 27,486 Reputation points Microsoft Employee Moderator

2024-11-26T20:30:17.2866667+00:00

@Alex Anders

Does this apply just to VMs or any service that is VNet integrated, such as App Service?

The default outbound access retirement only affects the VM's more details here
https://azure.microsoft.com/en-us/updates?id=default-outbound-access-for-vms-in-azure-will-be-retired-transition-to-a-new-method-of-internet-access
VNET integrated PaaS services are not in scope as they do not use default outbound access.
ChaitanyaNaykodi-MSFT 27,486 Reputation points Microsoft Employee Moderator

2024-11-26T20:33:39.1733333+00:00

@Rick Sparks

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.

The VPN gateway team is taking action to ensure the continued operation of deployed VPN gateways that use Basic SKU public IP addresses until the retirement of Basic IP in September 2025. Before this retirement, we will provide customers with a migration path from Basic to Standard IP.

more details in the link below
https://learn.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-vpn-faq#how-does-the-retirement-of-basic-sku-public-ip-addresses-affect-my-vpn-gateways
ChaitanyaNaykodi-MSFT 27,486 Reputation points Microsoft Employee Moderator

2024-11-26T20:36:44.5466667+00:00

@Jonas Züger

Would it be possible to upgrade using the same IP?

Please go through this link

https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/public-ip-upgrade?tabs=azureportal#upgrade-public-ip-address
ChaitanyaNaykodi-MSFT 27,486 Reputation points Microsoft Employee Moderator

2024-11-26T20:39:35.29+00:00

@Luis Esteban

Any update on migration for Virtual Network Gateways?

Please take a look below, the team will update when the migration path is ready
https://learn.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-vpn-faq#how-does-the-retirement-of-basic-sku-public-ip-addresses-affect-my-vpn-gateways
ChaitanyaNaykodi-MSFT 27,486 Reputation points Microsoft Employee Moderator

2024-11-26T20:47:30.87+00:00

@Kyle Daley

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

Basic SKU public IP retirement would not impact Cloud Services Extended Support (CSES) deployments. However, we advise using Standard SKU on ARM native resources (those that do not depend on CSES) when possible, because Standard has more advantages than Basic.

https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/public-ip-basic-upgrade-guidance#will-the-basic-sku-public-ip-retirement-impact-cloud-services-extended-support-cses-deployments
ChaitanyaNaykodi-MSFT 27,486 Reputation points Microsoft Employee Moderator

2024-11-26T20:51:54.9733333+00:00

@tstrong

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?

You can find the required details here "The Basic SKU currently supports only Basic SKU public IP addresses. We're working on adding support for Standard SKU public IP addresses for the Basic SKU."

https://learn.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-vpn-faq#can-i-request-a-static-public-ip-address-for-my-vpn-gateway
ChaitanyaNaykodi-MSFT 27,486 Reputation points Microsoft Employee Moderator

2024-11-26T21:08:29.8933333+00:00

@Francesco

Or a new Dynamic Standard SKU is going to be introduced?

Basic Dynamic IPs can be converted to Standard prior to upgrading. We don't have plans to introduce dynamic IPs for Standard SKU currently.
ChaitanyaNaykodi-MSFT 27,486 Reputation points Microsoft Employee Moderator

2024-11-26T21:10:15.8+00:00

@Carlos Duran

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)?

This retirement does not impact Cloud Services Extended Support. Cloud Services Classic is already retired. However, reserved IPs can be upgraded as well. Migrate a classic reserved IP address to a public IP address - Azure Virtual Network | Microsoft Learn
ChaitanyaNaykodi-MSFT 27,486 Reputation points Microsoft Employee Moderator

2024-11-26T21:11:36.39+00:00

@veliko.ivanov

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?

Would recommend upgrading to App GW v2

https://learn.microsoft.com/en-us/azure/application-gateway/migrate-v1-v2
ChaitanyaNaykodi-MSFT 27,486 Reputation points Microsoft Employee Moderator

2024-11-26T21:16:25.7066667+00:00

@Billy O'Neal (vcpkg)

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?

There will be no change to the pricing model. Standard IPs are billed in the same manner as Basic Public IPs. There is a difference of only $0.001/hour. Please refer to pricing here: Pricing - Virtual Machine IP Address Options | Microsoft Azure
ChaitanyaNaykodi-MSFT 27,486 Reputation points Microsoft Employee Moderator

2024-11-26T21:18:24.1733333+00:00

@Chao Yan

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?

Yes, that is correct
ChaitanyaNaykodi-MSFT 27,486 Reputation points Microsoft Employee Moderator

2024-11-26T21:19:55.28+00:00

@Gary B

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?

CSES will be allowed to be created. Only ARM / non CSES basic IPs will be blocked.

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?

No this is not in the current plan. We advise using Standard SKU on ARM native resources (those that do not depend on CSES) when possible, because Standard has more advantages than Basic.
https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/public-ip-basic-upgrade-guidance#will-the-basic-sku-public-ip-retirement-impact-cloud-services-extended-support-cses-deployments
Holger Bock Axelsen 16 Reputation points

2024-11-28T16:57:32.6966667+00:00

@ChaitanyaNaykodi-MSFT ,

Can you please clarify your above answer? Assuming we don't have spare Basic SKU IP addresses lying around, does this mean that we just cannot create a new Cloud Services (Extended Support) deployment after 31 March 2025?

Not being able to deploy a new CSES is pretty affecting.
ChaitanyaNaykodi-MSFT 27,486 Reputation points Microsoft Employee Moderator

2024-12-06T17:54:34.2533333+00:00

@Holger Bock Axelsen

Thank you for reaching out.

Actually, I just edited my response above.

CSES will be allowed to be created. Only ARM / non CSES basic IPs will be blocked.
Kindred Dev 26 Reputation points

2024-12-06T18:15:02.9766667+00:00

@ChaitanyaNaykodi-MSFT , as part of my CSES deployment, I have one ARM template deploying two Basic Public IP Addresses, but the CSES resource is not deployed in the same ARM template. Will the retirement exception for CSES cover this scenario? What will happen to temporarily unassociated Basic Public IP Addresses that are routinely used for swappable deployments (e.g. I have many Basic IP Address resources that are set aside for a staging deployment)
Holger Bock Axelsen 16 Reputation points

2024-12-09T16:16:58.31+00:00

@ChaitanyaNaykodi-MSFT ,

Thanks for replying, but I don't understand: CSES is ARM-based and the IPs used in CSES are ARM Basic IPs. To deploy a CSES (with a public IP) you literally have to reference the IP in the ARM template for the CSES deployment. That's pretty hard to do if I cannot create such IPs anymore?
Jose P. Cisneros M 0 Reputation points

2025-01-19T23:54:55.13+00:00

As this will be part of the change of the default outbound connectivity be disabled as well on new deployments, will this be affecting old VNETs or only new VNETs? or it means each VM created after the change will have the default outbound connectivity disabled?
ChaitanyaNaykodi-MSFT 27,486 Reputation points Microsoft Employee Moderator

2025-01-21T17:32:02.2466667+00:00

@Jose P. Cisneros M
You can find more details about this here

https://azure.microsoft.com/en-us/updates?id=default-outbound-access-for-vms-in-azure-will-be-retired-transition-to-a-new-method-of-internet-access

On 30 September 2025, default outbound access connectivity for virtual machines in Azure will be retired. After this date, all new VMs that require internet access will need to use explicit outbound connectivity methods such as Azure NAT Gateway, Azure Load Balancer outbound rules, or a directly attached Azure public IP address.

Also

Your existing VMs that use default outbound access will continue to work after this retirement, however, we strongly recommend transitioning to an explicit outbound method

Hope this helps! Thanks!
Morné Zaayman 46 Reputation points

2025-03-06T06:42:03.09+00:00

The email states:

If you have any Basic SKU public IP addresses deployed in Azure Cloud Services (extended support), those deployments won't be affected by this retirement and you don't need to take any action for them.

What about new Cloud Services (extended support) deployments? Will we still be able to create Basic SKU public IP addresses for them?
Morné Zaayman 46 Reputation points

2025-03-06T06:48:51.8233333+00:00

The email states:

If you have any Basic SKU public IP addresses deployed in Azure Cloud Services (extended support), those deployments won't be affected by this retirement and you don't need to take any action for them.

What about new Cloud Services (extended support) deployments? Will we still be able to create Basic SKU public IP addresses for them?
Arnel Joaquin 40 Reputation points

2025-03-06T15:06:25.5966667+00:00

If I follow the instructions to upgrade from Basic to Standard. Is our current static ip addresses going to change? Is it going to break users access once we convert/upgrade? Is there any down time?
Steven Lewin 0 Reputation points

2025-03-07T12:04:12.3533333+00:00

Hi.

What will happen if we do nothing and are not planning to add any more Basic SKU IP's to our environment will anything stop working?

Thanks

Steven
Ojas Chopade (LTIMINDTREE LIMITED) 0 Reputation points Microsoft External Staff

2025-03-11T09:03:17.56+00:00

Does this change impact automatically created VM's by Databricks resource in Azure? If yes, do we have to establish explicit outbound access after the VM is created by databricks resource?
EPNAdam 115 Reputation points

2025-03-19T14:45:36.7866667+00:00

Following. Have the same question.
Namrata Soni 0 Reputation points

2025-03-19T16:43:39.6166667+00:00

For what reason has it been removed?
Coughtry, Ben 0 Reputation points

2025-03-20T22:50:30.04+00:00

Hello Microsoft, please excuse the multiple questions on this post, but can you please confirm the following?

Stand alone VM PIP Sku upgrade powershell script:
https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/public-ip-upgrade-vm

Availability Set VMs PIP Sku upgrade powershell script:
https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/public-ip-upgrade-availability-set

Load Balancer PIP Sku upgrade - upgrade the entire LB sku via script to also upgrade PIP sku?:
https://learn.microsoft.com/en-us/azure/load-balancer/upgrade-basic-standard-with-powershell

ExpressRoute Gateway - Use ER Gateway Sku Migration wizard via Portal. This process appears to create a new PIP - is there no way to retain the existing public /32 IP address?
https://learn.microsoft.com/en-us/azure/expressroute/gateway-migration

VPN Gateway - MS does not have an upgrade path for VPN Gateway PIP Sku yet? Roughly when can one be expected?

Application Gateway PIP sku upgrade: Upgrade the SKU of the gateway itself to also upgrade PIP sku?
https://learn.microsoft.com/en-us/azure/application-gateway/migrate-v1-v2

Please let me know the answers to the above questions. Thanks so much!
ChaitanyaNaykodi-MSFT 27,486 Reputation points Microsoft Employee Moderator

2025-03-27T21:08:53.84+00:00

@Morné Zaayman ,

Thank you for reaching out. Can you please let me know what new Cloud Services (extended support) deployments you will be doing? So that I can make sure I understood your question.

As per the announcement
https://azure.microsoft.com/en-us/updates?id=upgrade-to-standard-sku-public-ip-addresses-in-azure-by-30-september-2025-basic-sku-will-be-retired

If you have any Basic SKU public IP addresses deployed in Azure Cloud Services (extended support), those deployments will not be affected by this retirement and you don't need to take any action for them.

More details here

https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/public-ip-basic-upgrade-guidance#will-the-basic-sku-public-ip-retirement-impact-cloud-services-extended-support-cses-deployments

Thank you!
ChaitanyaNaykodi-MSFT 27,486 Reputation points Microsoft Employee Moderator

2025-03-27T21:21:44.95+00:00

@Steven Lewin

What will happen if we do nothing and are not planning to add any more Basic SKU IP's to our environment will anything stop working?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.

You can follow this guideline to upgrade the IP SKU

https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/public-ip-basic-upgrade-guidance

Thanks!
ChaitanyaNaykodi-MSFT 27,486 Reputation points Microsoft Employee Moderator

2025-03-27T21:22:42.2433333+00:00

@Steven Lewin

What will happen if we do nothing and are not planning to add any more Basic SKU IP's to our environment will anything stop working?

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.
You can follow this guideline to upgrade the IP SKU

https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/public-ip-basic-upgrade-guidance

Thanks!
Morné Zaayman 46 Reputation points

2025-03-28T12:22:21.3366667+00:00

@ChaitanyaNaykodi-MSFT

Thank you for reaching out. Can you please let me know what new Cloud Services (extended support) deployments you will be doing? So that I can make sure I understood your question

There are two scenarios:

When updating our Cloud Service, we first deploy a new Cloud Service resource and then swap the IP addresses with the currently deployed Cloud Service resource.

We occasionally have to set up completely new Cloud Service resources for customers who have purchased our product. This also entails creating a new resource group in a new subscription with new resources for everything the Cloud Service requires, including IP Addresses.
ChaitanyaNaykodi-MSFT 27,486 Reputation points Microsoft Employee Moderator

2025-03-28T15:01:38.8266667+00:00

@Arnel Joaquin

If I follow the instructions to upgrade from Basic to Standard. Is our current static ip addresses going to change? Is it going to break users access once we convert/upgrade? Is there any down time?

Since IP address is static, Upgrading a public IP resource retains the IP address. More details here https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/public-ip-upgrade?tabs=azureportal#upgrade-public-ip-address

Since the IP address will be retained I do not see any reason why user access will get affected, but there will be a downtime as you will have to diss-associate the IP address. You can refer the link above for more details. Thanks!
ChaitanyaNaykodi-MSFT 27,486 Reputation points Microsoft Employee Moderator

2025-03-28T15:03:22.8866667+00:00

@Ojas Chopade (LTIMINDTREE LIMITED) , @EPNAdam

Databricks related question is answered here

https://learn.microsoft.com/en-us/answers/questions/2123428/basic-sku-public-ip-retirement-databricks-query
ChaitanyaNaykodi-MSFT 27,486 Reputation points Microsoft Employee Moderator

2025-04-01T14:18:51.4766667+00:00

@Morné Zaayman

You can find the details about new Cloud Services Extended Support (CSES) deployments here
https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/public-ip-basic-upgrade-guidance#will-the-basic-sku-public-ip-retirement-impact-cloud-services-extended-support-cses-deployments

No, this retirement will not impact your existing or new deployments on CSES.

Thank you!
Venkatesh Kacham 6 Reputation points Microsoft Employee

2025-04-17T13:11:25.2566667+00:00

PrivateSubnetSetting.pdf

I have checked the checkbox "Enable Private Subnet" in my subnet and saved. It persists and shows when the subnet config is closed and re-opened.

But, the checkbox remains unchecked when navigated to subnet from the AppService Virtual network configuration.

Attached screenshots with evidence.
Yaniv Shmulevich 0 Reputation points

2025-07-16T13:18:43.93+00:00

Hi.
What is the impact of this change, on all my Azure live, Production environments?
Ming Yu 40 Reputation points

2025-07-16T19:53:37.75+00:00

According to https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/virtual-network-public-ip-address#view-modify-settings-for-or-delete-a-public-ip-address:

Can someone help understand what is means "they cannot be associated with an azure resource that is either zone-redundant or tied to a pre-specified zone in regions where this is offered"?

We have a bunch of azure VMs using public IPs of basic SKU; some of the VMs are associated with an azure zone and some not.

Does the verbiage mean that, after the IPs are upgraded to standard SKU, they won't be able to be associated with VMs, which are not associated with an azure zone?

Thanks for the clarification!

Answer 1

Arnel Joaquin 40

I just performed this task on 2 separate vm's. Had to disassociate the ip, upgrade basic to standard, and then re-associate the ip. Luckily, it was static and kept same ip address.

Jake Osborne 0 Reputation points

2025-06-20T02:59:37.02+00:00

How does this affect KMS outbound access for VMs? Do we need a NAT Gateway even if we have an appliance in this case?

Answer 2

ChaitanyaNaykodi-MSFT 27,486 Microsoft Employee Moderator

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!

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?
T Ushijima 40 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 50 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.
ChaitanyaNaykodi-MSFT 27,486 Reputation points Microsoft Employee Moderator

2024-11-26T20:52:49.57+00:00

@tstrong

You can find the required details here "The Basic SKU currently supports only Basic SKU public IP addresses. We're working on adding support for Standard SKU public IP addresses for the Basic SKU."

https://learn.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-vpn-faq#can-i-request-a-static-public-ip-address-for-my-vpn-gateway
Ming Yu 40 Reputation points

2025-07-16T19:42:22.6666667+00:00

So, we are also using Gen1 Basic VPN Gateway (i.e., SKU VpnGw1).

As mentioned in https://learn.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-vpn-faq#can-i-request-a-static-public-ip-address-for-my-vpn-gateway:
Can we know if the migration path is available and where we can find it?

Thanks.

Answer 3

Pawel Gula 96

Is it true that the Azure VMs created before that date (Sept 30) Internet access will continue to work using default outbound access as it is today ?

Carlos Cruz 0 Reputation points

2025-04-14T17:19:20.17+00:00

Interested in this
Damian Lynch 10 Reputation points

2025-05-09T09:36:57.1033333+00:00

Is there any timeline on when Basic VPN gateway will support standard public IP address? Annoucement stated there would be an upgrade path.

Share via

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

3 answers

Your answer