Support IPv6 Throughout the Azure Platform
IPv6 has been a standard for years and ISPs are starting to roll out native IPv6 stacks to consumers. The time is now to support IPv6.
IPv6 in Azure VNETs is now generally available in all Azure Public cloud regions and Azure Government cloud.
Announcement (Service Update): https://azure.microsoft.com/en-us/updates/ipv6-for-azure-virtual-network-is-now-generally-available-2/
Links to Documentation & Samples
Full documentation including sample scripts is available here: https://aka.ms/IPv6ForAzureVNETdoc
A sample JSON template is posted in the quickstart repository:
can't get on VM from work due to not been able to add ipv6
André Melancia [MCT] commented
This ticket is THREE years old, and 2½ years ago there was an official response.
That FAQ is exactly the same as it was 3 years ago, and no IPv6 connectivity in sight.
Practically all Microsoft products (Windows included) support IPv6.
How hard is it to have it in Azure? Half the world has done it!
Ahmed Eltawil commented
Is there any updates on this ticket? I see that it has started 2 years ago.
Ondřej Sojka commented
Currently, Azure has NO support for IPv6. How can this be?
Olivier Hault (Level IT) commented
This issue is not really a good brand image for Azure. How is it possible IPV6 in not yet supported (May 2016) ?
Steven Walsh commented
This issue is almost 5 years old, but heck.... i still have hope it might make it. It would be wonderful to connect to my database from my tethered phone on a train :(
Dali Kilani commented
+1 on Michael's comment below. CG-NAT and Ipv6-only CPE's (even for business customers, say a remote office ...) are becoming more and more common for cable ISPs. This leaves potential customers without an option at all ...
really looking forward to being able to provide an IPv6 address instead of the currently required public IPv4 address.
any news 2015 is going to end soon.... when can we except ipv6 support?
Rodrigo Oliveira commented
If we make a simple test with the quagga.conf in VM Ubuntu? Just for a example?
Lol, feedback.azure.com has IPv6 support.
Why is it taking so long to get IPv6?
Patrick Laughton commented
Apparently Microsoft "started" their efforts two months after this was first suggested, but there's no indication what progress has actually occurred: http://feedback.azure.com/forums/217313-networking-dns-traffic-manager-vpn-vnet/suggestions/4992369-support-ipv6-throughout-the-azure-platform
Patrick Laughton commented
Speaking with both my Microsoft enterprise customer and IPv6 expert hats on, IPv6 support in Azure is long overdue.
ISPs started providing IPv6 only to home customers - sometimes using DS-lite and similar plus CG-NAT for IPv4 connectivity. We need IPv6 in Azure to implement scenarios where connection to client's network (which is IPv6 only in that case) is possible. I.e. we require IPv6 in Azure!
I won't use Azure before it supports IPv6
It is kind of ridiculous for Microsoft to push the stack so hard in all the software and not support it inside its own cloud infrastructure
IPv6 us needed for every service on thé internet. As a mater of fact, in 2015, no new product should ship without IPv6 support. Period.
Lawrence Hughes commented
Remember that Cloud uses NAT to allow the provider to move your data and app servers around wherever it is cheaper or more convenient FOR THEM. Guess what IPv6 doesn't have. This could be the reason NONE of the Cloud providers include IPv6 support. Unless I've missed something, Cloud is a legacy technology that won't survive the transition to IPv6 (or at least we will have to keep IPv4 around to support it). MS keeps encouraging me to use Azure. First, it has no IPv6, which I use in pretty much everything I do. Second, it's Cloud XOR Security - that's an EXCLUSIVE OR - choose one.
I cannot use Azure for clout or IOT without real IPv6 support. IPv6 is absolutely required for cloud and iot scale.
On desktops and servers MS are close to best in class when it comes to IPv6 support - and so shoud Azure. Shame on you ;)