question

KumarYogender-2631 avatar image
0 Votes"
KumarYogender-2631 asked GitaraniSharmaMSFT-4262 commented

Change Std SKU Public IP to Basic SKU

Hi Team,

We are using Std SKU public IP address , we are moving resources from one subscription to another. By default we can not move Std SKU public IP from one subscription to another. I don't want to loss the public IP else we have to do lot off change in our infra. Is there any way to retain same public ip address in target subscription as well.

is there any way to change the SKU from std to basic?

azure-virtual-network
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

To follow-up, Please let us know if you have further query on this.
Please don’t forget to Accept the answer

0 Votes 0 ·
learn2skills avatar image
0 Votes"
learn2skills answered learn2skills edited

Hi @KumarYogender-2631

This feature is now available in few regions (upgrade IP from Basic to Standard-no zone)

Upgrade public IP addresses
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

Note-
- 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.
- Public IPs upgraded from Basic to Standard SKU will continue to have no availability zones and therefore cannot be associated with an Azure resource that is either zone-redundant or zonal. Note this only applies to regions that offer availability zones.
- You cannot downgrade from Standard to Basic.

You can ask in the product team with feedback form

If the Answer is helpful, please click Accept Answer and up-vote, this can be beneficial to other community members.





5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

prafulbusa avatar image
1 Vote"
prafulbusa answered

Why are we even pushing customers to have standard IP then? If we can't support the move operation from one subscription to another.
I remember warning that basic IP will be changed to standard but I am sure there will many customers would like to change their subscription every year.
Then what? It's just not good design. People should be warned about that too before changing from basic to standard that, "hey if you change basic public IP to standard type, it's not allowed to move to another subscription" so that people can move the basic first before changing to the standard.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

JasonKittelstad-2451 avatar image
0 Votes"
JasonKittelstad-2451 answered GitaraniSharmaMSFT-4262 commented

Where do we change the SKU from Basic to Standard?

· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hello @JasonKittelstad-2451 ,

To change a Public IP SKU from Basic to Standard, it must not be associated with any resource and should have a Static allocation method.

You can then use Azure portal, PowerShell or CLI to upgrade the Public IP.

In Azure portal, you can select the upgrade banner at the top of the overview section in your Public IP resource:

177488-image.png

Regards,
Gita


0 Votes 0 ·
image.png (195.4 KiB)

Our concern with this is as follows:

  • if the IP address is dissociated, is it lost/changed? Does the VM remain accessible?

  • If the upgrade is done, same question as above?

this all goes to downtime to be expected when following the recommended upgrade prompt.

  • remember that there may be lots of configs talking to the existing public IP as well, but even if everything is routed to the CNAME DNS entry associated with the IP/VM, the question remains. Will there be a change in IP and should downtime be expected.



0 Votes 0 ·

Hello @DominiqueSeptember-4358 ,

The Basic public IP you are upgrading must have the Static allocation type.

Static IP address remain unchanged until the Public IP resource exists. The IP address is only released when the Public IP resource is deleted.

Any associated IP address is unchanged if the allocation method is changed from dynamic to static. You can set the allocation method of your Public IP address to static to ensure the IP address remains the same.
Changing the Public IP allocation method from dynamic to Static could reboot the associated VM.

When the Public IP is dissociated, the VM will not be accessible via that Public IP anymore.
Once you upgrade the Public IP SKU, you can associate it back to the VM for access.

Since you change the IP allocation to Static and then dissociate and upgrade it to Standard SKU, the IP address will not change.

NOTE:
- Upgrading a basic public IP to standard SKU can't be reversed.
- Public IPs upgraded from Basic to Standard SKU continue to have no availability zones. This 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.
- Matching SKUs are required for Load Balancer and Public IP resources. You can't have a mixture of Basic SKU resources and standard SKU resources. You can't attach standalone virtual machines, virtual machines in an availability set resource, or a virtual machine scale set resources to both SKUs simultaneously.

Regards,
Gita

0 Votes 0 ·