Azure
Ipv6 Outbound
Preview link: https://antares-blog-staging-pr-477.azurewebsites.net
- Your changes have been deployed to the preview site. The preview site will update as you add more commits to this branch.
- The preview site shows any future-dated articles. If you are publishing a future-dated article, it will not show on the production site until the file's specified date.
- The preview link is shareable, but will be deleted when this pull request is merged or closed.
This is an automated message.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Not obsolete - just stalled by CCOA and Networking not able to deliver enough IPv6 addresses. @btardif is it a problem to keep it around? I expect it to be relevant mid Q1. If yes, I can pull the resources locally or to my private git meanwhile.
@madsd no problem, I think I closed this by mistake, there were a few OLD PR that did need to get cleaned out.
@madsd Sorry to hijack this PR, but I just wanted to note that the original announcement page 404s: https://azure.github.io/AppService/2024/06/01/Announcing-Inbound-IPv6-support
I was able to find it, but it should probably redirect to the new one: https://azure.github.io/AppService/2024/11/08/Announcing-Inbound-IPv6-support.html
Is there any insight you can provide on when we can expect IPv6 inbound becoming GA?
Hi @rgrace-puck Yeah, I can see that someone changed the date on the article, which is part of the path. Can you tell me where it is linked from and I can update the link?
Our next step is to introduce outbound IPv6 in preview - we are just now starting to enable the first public regions and I should have some news here in the next month or so.
Inbound is mostly waiting for the full regional rollout. We had some regions lagging waiting for IP allocation, but they should be done soon. We also need to add it to portal to be able to declare GA - but from a usage perspective you can consider it GA and support team will also handle it accordingly.
Do you have a use case for IPv6 that you are looking at?
Hi @rgrace-puck Yeah, I can see that someone changed the date on the article, which is part of the path. Can you tell me where it is linked from and I can update the link?
Oh, I didn't find it linked anywhere but I had it saved on an internal ticket for tracking purposes and got a 404 after revisiting it.
We also need to add it to portal to be able to declare GA - but from a usage perspective you can consider it GA and support team will also handle it accordingly.
That's good to hear and basically what we're looking for in terms of confidence. We generally wait until GA but if support is treating it like that already, then it sounds good to go.
Do you have a use case for IPv6 that you are looking at?
Nothing in particular, we just want to offer better connectivity to users (i.e. avoiding NAT or CGNAT) as the global IPv4 space is exhausted and more ISPs are moving towards IPv6.
Thanks!
