Cannot specify basic sku Public IP for an IPv6 network interface IP configuration

Rich Watts 6

If I try to attach a basic sku public IPv6 address to a network interface I get this message:

Cannot specify basic sku Public IP for an IPv6 network interface IP configuration.

This means I cannot attach a public IPv6 address to my network interface as it already has a basic sku IPv4 address associated to it (which I don't want to change).

What is the reason for preventing basic sku public IPv6 addresses from being attached to network interfaces?

msrini-MSFT 9,256 Reputation points Microsoft Employee

2022-08-17T04:30:18.387+00:00

Hi,

As per current design, Standard SKU and the Basic SKU cannot co-exist. If you have 2 interfaces and if you need to assign a IPv6 then both interface should be using Standard Public IP.

This is by design behavior.

You can create a new Standard IP and then assign it to the Ipv4 interface. Unfortunately that is the only possible solution you have now.

Regards,
Karthik Srinivas
KapilAnanth-MSFT 35,001 Reputation points Microsoft Employee

2022-08-17T08:20:33.247+00:00
Hi RichWatts-6318,

Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.
I understand that you are trying to attach an IPv6 Public IP of basic SKU to an Azure VM's Nic.

There are two things to notice here,

As highlighted by @msrini-MSFT , the co-existence of Basic and Standard SKU Azure resources is not supported with one or two exceptions.

Secondly, you will not be able to assign a basic SKU IPv6 to a Network Interface.

This is an expected behavior

Basic IPV6 Public IPs can only be associated with Load Balancers to provide support for legacy

You should create a standard Public IPV6 and associate it with the NIC

Also, you must upgrade your basic IPV4 to standard, if you are planning to go ahead with the above

Refer : https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/public-ip-upgrade-portal

I hope this helps.
Please let us know if you have any follow-up questions on this.

Cheers,
Kapil.

Please don’t forget to close the thread by clicking "Accept the answer" wherever the information provided helps you, as this can be beneficial to other community members.
Rich Watts 6 Reputation points

2022-08-17T10:32:20.15+00:00

Thank you for your reply but it doesn't answer my core question. Basic sku public IPv4 addresses can be assigned to VM instances, so why can't basic sku public IPv6 addresses?
Rich Watts 6 Reputation points

2022-08-17T10:33:04.53+00:00

Thank you for your reply but it doesn't answer my core question. Basic sku public IPv4 addresses can be assigned to VM instances, so why can't basic sku public IPv6 addresses?
KapilAnanth-MSFT 35,001 Reputation points Microsoft Employee

2022-08-17T10:38:44.683+00:00

Hi RichWatts-6318,

This behavior is by design (expected) .
There maybe some internal requirements that prevent the association of Basic IPV6 SKU to a VM NIC.

We recommend customers leverage standard SKU for newer deployments as it has more features.

Thanks,
Kapil.

----------------------------------------------------------------------------------------------------------------

Please accept an answer if correct. Original posters help the community find answers faster by identifying the correct answer.
Rich Watts 6 Reputation points

2022-08-17T10:56:54.507+00:00

Standard sku IPv4 is not free, so this limitation is designed to get customers needing IPv6 to spend more money?
KapilAnanth-MSFT 35,001 Reputation points Microsoft Employee

2022-08-17T11:27:33.907+00:00

Hi RichWatts-6318,

I checked this internally and this is by design.
As stated earlier, there will be internal dependencies that require this resource to be of Standard SKU

You can always provide your feedback on our products, their features, and how we can improve them.
https://feedback.azure.com/d365community/forum/79b1327d-d925-ec11-b6e6-000d3a4f06a4

Our Product group closely monitors user feedback(s) from this forum.

Thanks,
Kapil.
Rich Watts 6 Reputation points

2022-08-17T11:46:07.987+00:00

As suggested: https://feedback.azure.com/d365community/idea/afadb0fb-211e-ed11-a81b-6045bd853c94
KapilAnanth-MSFT 35,001 Reputation points Microsoft Employee

2022-08-22T12:03:24.33+00:00

Thank you @Rich Watts .

I shall also create an internal work item as I cannot find this in our immediate roadmap.
I will keep this thread updated should there be any developments.

Thanks,
Kapil.
Rich Watts 6 Reputation points

2022-08-22T12:06:57.003+00:00

Thank you anonymous user-MSFT .