Upgrade public IP addresses

Azure public IP addresses are created with a SKU--either Basic or Standard--which determines aspects of their functionality (including allocation method, feature support, and which resources they can be associated with).

The following scenarios are reviewed in this article:

  • How to upgrade a Basic SKU public IP to a Standard SKU public IP (using PowerShell or CLI)
  • How to migrate a Classic Azure Reserved IP to an Azure Resource Manager Basic SKU public IP

Upgrade public IP address from Basic to Standard SKU

In order to upgrade a public IP, it must not be associated with any resource (see this page for more information about how to disassociate public IPs).

Important

Public IPs upgraded from Basic to Standard SKU continue to have no guaranteed availability zones. Please ensure this is kept in mind when choosing which resources to associate the IP address with.


The following example assumes previous creation of a Basic SKU public IP, using the example given on this page with a Basic public IP myBasicPublicIP in myResourceGroup.

In order to upgrade the IP, simply execute the commands below using PowerShell. Note if the IP address is already statically allocated, that section can be skipped.

## Variables for the command ##
$rg = 'myResourceGroup'
$name = 'myBasicPublicIP'
$newsku = 'Standard'
$pubIP = Get-AzPublicIpAddress -name $name -ResourceGroupName $rg

## This section is only needed if the Basic IP is not already set to Static ##
$pubIP.PublicIpAllocationMethod = 'Static'
Set-AzPublicIpAddress -PublicIpAddress $pubIP

## This section is for conversion to Standard ##
$pubIP.Sku.Name = $newsku
Set-AzPublicIpAddress -PublicIpAddress $pubIP

Upgrade (migrate) a classic Reserved IP to a static public IP

To benefit from the new capabilities in Azure Resource Manager, you can migrate existing public static IP address--called Reserved IPs--from the Classic model to the modern Azure Resource Manager model. The migrated public IP will be a Basic SKU type.


The following example assumes previous creation of a classic Azure Reserved IP myReservedIP in myResourceGroup. Another prerequisite for migration is to ensure the Azure Resource Manager subscription has registered for migration. This is covered in detail on Steps 3 and 4 of this page.

In order to migrate the Reserved IP, execute the commands below using PowerShell. Note if the IP address is not associated with any service (below there is a service named myService), that step can be skipped.

## Variables for the command ##
$name = 'myReservedIP'

## This section is only needed if the Reserved IP is not already disassociated from any Cloud Services ##
$serviceName = 'myService'
Remove-AzureReservedIPAssociation -ReservedIPName $name -ServiceName $service

$validate = Move-AzureReservedIP -ReservedIPName $name -Validate
$validate.ValidationMessages

The previous command displays any warnings and errors that block migration. If validation is successful, you can proceed with the following steps to Prepare and Commit the migration:

Move-AzureReservedIP -ReservedIPName $name -Prepare
Move-AzureReservedIP -ReservedIPName $name -Commit

A new resource group in Azure Resource Manager is created using the name of the migrated Reserved IP (in the example above, it would be resource group myReservedIP-Migrated).

Limitations

  • In order to upgrade a Basic Public IP, it cannot be associated with any Azure resource. Please review this page for more information on how to disassociate public IPs. Similarly, in order to migrate a Reserved IP, it cannot be associated with any Cloud Service. Please review this page for more information on how to disassociate reserved IPs.
  • Public IPs upgraded from Basic to Standard SKU continue to have no guaranteed availability zones. Please ensure this is kept in mind when choosing which resources to associate the IP address with.
  • You cannot downgrade from Standard to Basic.

Next Steps