ErrorCode: IPv4BasicSkuPublicIpCountLimitReached, ErrorMessage: Cannot create more than 0 IPv4 Basic SKU public IP addresses for this subscription in this region

Hi Rick Seiler

Thanks for using the Q&A platform.

That error means your subscription has a quota of “0” for IPv4 Basic SKU Public IPs in the region you’re trying to use, so Azure is blocking the migration when it tries to create one. It’s an enforced subscription policy that Microsoft has been phasing in since it started deprecating Basic SKU Public IPs.

Basic SKU Public IPs are deprecated for new creation in most regions; Microsoft’s guidance is to use Standard SKU Public IPs instead.

Kindly find: https://learn.microsoft.com/en-us/answers/questions/1033456/retirement-announcement-basic-sku-public-ip-addres?

To fix the issue, you can switch to the standard SKU or remove the dependency on a public IP during migration.

If the response was helpful, please feel free to mark it as “Accepted Answer” and consider giving it an upvote. This also benefits others in the community.

Regards,

Obinna.

Hi Rick Seiler,

Adding few more details to the answer provided by Obinna Ejidike,

 This error occurs because your subscription has a quota of 0 for IPv4 Basic SKU Public IPs in the target region. During Classic to ARM migration, Azure defaults to creating the Classic public IPs as Basic SKU in the ARM model. The IPv4BasicSkuPublicIpCountLimitReached message means your subscription policy now blocks new Basic SKU public IPs This is a preventative measure by Microsoft to enforce the use of the more modern and secure Standard SKU.

 Microsoft is actively retiring Basic SKU public IPs. The search results confirm a key date to highlight: March 31, 2025, which is the last day to create new Basic SKU public IPs. After this date, creating new ones will be impossible, which explains why your migration is failing now. The final retirement date is September 30, 2025.

Retirement Announcement - Basic SKU Public IP addresses will be retired on 30 September 2025 - Microsoft Q&A

 You can fix the error by either migrating to a Standard SKU or removing the IP Dependency. This can be achieved by:

 1.Migrate to Standard SKU

The migration tool can't directly upgrade a Basic SKU to a Standard SKU. You will likely need to perform a manual upgrade. The procedure is as follows:

·       Disassociate the Basic SKU public IP from its resource (this causes downtime).

·       Upgrade it to Standard SKU in the portal or via PowerShell/CLI.

·       Reassociate it with the resource.

For better idea refer these documents: Upgrade Basic Public IP Address to Standard SKU in Azure | Microsoft Learn

Migrate a classic reserved IP address to a public IP address - Azure Virtual Network | Microsoft Learn

 2.Remove the Public IP Dependency

If the virtual network's resources do not need a public IP address, you can remove the public IP association entirely before the migration. This might be a viable option for backend services that only need to communicate with other resources within the virtual network. But may not be an option for services that require inbound or outbound internet access.

3.Request a temporary quota increase

In some cases, you can request a quota increase for Basic SKU IPv4 public IPs via Subscriptions → Usage + quotas → Request increase

Kindly check the responses and let me know if you require any further assistance.I am happy to help you with your queries. If the information is helpful, please click on Upvote and Accept Answer on it so that it can help other community members.

Thank you,

Rashmika