azure-deprecation / dashboard

Notices about Azure services & features being deprecated
https://azure-deprecation-notices.cloud
MIT License
135 stars 6 forks source link

Basic SKU public IP addresses are retiring on October 1st, 2025 #253

Open azure-deprecation-automation opened 1 year ago

azure-deprecation-automation commented 1 year ago

Basic SKU public IP addresses are retiring on October 1st, 2025

Deprecation ID: dbdbe1d7-b6e4-4bca-b2e9-08c407fcec78 Deadline: Sep 30, 2025 Impacted Services:

More information:

Notice

Here's the official report from Microsoft:

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.

Standard SKU public IP addresses offer significant improvements, including:

  • Access to a variety of other Azure products, including Standard Load Balancer, Azure Firewall, and NAT Gateway.
  • Security by default—closed to inbound flows unless allowed by a network security group.
  • Zone-redundant and zonal front ends for inbound and outbound traffic.

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.

Timeline

Phase Date Description
Announcement Oct 07, 2022 Deprecation was announced
Creation Disabled Mar 31, 2025 Customers will no longer be able to create new basic SKU public IP addresses.
Deprecation Sep 30, 2025 Services will no longer work.

Impact

Basic SKU public IP addresses are retiring on October 1st, 2025 and upgrade to Standard SKU is required.

Required Action

A migration guide is provided here.

Here's the official report from Microsoft:

To avoid any potential service disruptions, review pricing and then upgrade to Standard SKU public IP addresses by 30 September 2025.

Contact

You can get in touch through the following options:

azure-deprecation-automation commented 1 year ago

This issue is automatically managed and suggest to use GitHub Discussions to discuss this deprecation.