This week, I activated a free trial account on Azure Portal, mostly because I wanted to test some RDP things with my Chromebook.
I picked up a public IPv4 address for free. I first tried to go to an IPv6-only stack, but I realized how impossible that is when cloud services, especially their APIs, are mired in the 90s, and can't accommodate hosts that don't respond on IPv4.
So I was able to get some semblance of IPv6 working with a pre-assigned ULA address range (I think it was a /48). But there's no public IPv6 to be had. Apparently, free trial accounts aren't eligible for them, but there's no clear-cut error message, it's just...whatever options I choose, I receive provisioning errors. I only deployed a single VM. With no public IPv6, it defeats the purpose of even trying to use the protocol.
So why does a leading cloud service make it so, so difficult to work with IPv6? It's very discouraging.
I picked up a public IPv4 address for free. I first tried to go to an IPv6-only stack, but I realized how impossible that is when cloud services, especially their APIs, are mired in the 90s, and can't accommodate hosts that don't respond on IPv4.
So I was able to get some semblance of IPv6 working with a pre-assigned ULA address range (I think it was a /48). But there's no public IPv6 to be had. Apparently, free trial accounts aren't eligible for them, but there's no clear-cut error message, it's just...whatever options I choose, I receive provisioning errors. I only deployed a single VM. With no public IPv6, it defeats the purpose of even trying to use the protocol.
So why does a leading cloud service make it so, so difficult to work with IPv6? It's very discouraging.