Critical Deadline: Mandatory Upgrade of Azure Basic Public IP Addresses to Standard SKU

Critical Deadline: Mandatory Upgrade of Azure Basic Public IP Addresses to Standard SKU

Azure is retiring the Basic SKU for Public IP addresses. This mandatory change impacts numerous deployments, introducing new technical requirements and offering enhanced capabilities. Customers must act to upgrade their IPs to the Standard SKU before the official retirement date.

Key Deadlines You Need to Know

This transition involves two critical dates that dictate your migration timeline:

EventDeadlineAction Required
New Basic IP Creation CutoffMarch 31, 2025You are no longer be able to provision new Basic SKU public IP addresses post 31st March 2025.
Basic SKU RetirementSeptember 30, 2025All existing Basic SKU public IP addresses will be retired. You must upgrade to Standard SKU by this date to avoid service disruption.

You may continue to use your existing Basic SKU public IP addresses until the September 30, 2025, retirement date.

Why Upgrade? Technical Advantages of Standard SKU

The Standard SKU is not just a replacement; it’s a significant upgrade that aligns with modern Azure networking best practices and unlocks new services:

  1. Access to Modern Services: Standard IPs are a prerequisite for key Azure networking products, including:
    • Standard Load Balancer
    • Azure Firewall
    • NAT Gateway
  2. Security by Default (Mandatory NSG): The Standard SKU operates on a “Secure by default” model. This is the most crucial technical detail:
    • Standard Public IPs are closed to inbound flows by default.
    • To allow any incoming traffic, you must explicitly configure a Network Security Group (NSG) and associate it with the public IP’s Network Interface (NIC) or subnet.
  3. High Availability: Standard IPs support Zone-redundant and zonal front ends for both inbound and outbound traffic, allowing you to build highly available architectures across Azure Availability Zones.

Technical Upgrade Mandates and Nuances

To successfully upgrade an IP, certain technical prerequisites must be met, and a specific caveat must be noted:

Technical MandateDetail
DisassociationThe Basic Public IP address must be dissociated from all Azure resources before the upgrade can be performed.
AssignmentThe Basic IP address must be statically assigned. Dynamic IPs must be converted to static first.
IP Address RetentionThe upgrade process retains the existing IP address (the IP value does not change).
IrreversiblyThe upgrade from Basic to Standard SKU cannot be reversed.
Zone NuanceWhile Standard IPs support zones, public IPs upgraded from Basic to Standard typically continue to have no availability zones. This means they cannot be associated with zone-redundant resources (unless the Basic IP was originally zone-specific, which is rare).

Exception: Azure Cloud Services (Extended Support)

If you have any Basic SKU public IP addresses deployed in Azure Cloud Services (extended support), those specific deployments will not be affected by this retirement. No action is required for these particular IPs.

Conclusion and Required Action

The retirement of the Azure Basic SKU Public IP is a hard deadline that cannot be ignored. The clock is ticking toward the September 30, 2025 final retirement date, with the inability to create new Basic IPs starting March 31, 2025.

The upgrade to the Standard SKU brings mandatory “Secure by default” networking, requiring the immediate configuration of a Network Security Group (NSG) post-migration to maintain connectivity. Customers must review their current pricing, plan the required disassociation and static conversions, and execute the upgrade well in advance of the deadline. Proactive migration ensures service continuity and positions your infrastructure to leverage the latest high-availability and security features offered by the Azure Standard SKU ecosystem.

Leave a Reply

Your email address will not be published. Required fields are marked *