We are excited to announce the public preview of IPv6 outbound support in App Service for Windows! Public preview of outbound IPv6 support for Windows multi-tenant apps is supported on all App Service plan SKUs, Functions Consumption, Functions Elastic Premium, and Logic Apps Standard running Windows. This is the next announcement in our series of IPv6 related feature work on App Service.
- Public preview of Inbound IPv6 Support on App Service multi-tenant
- This announcement: IPv6 (dual-stack) non-vnet outbound support (multi-tenant)
- Backlog - IPv6 vnet outbound support (multi-tenant and App Service Environment v3)
- Backlog - IPv6 vnet inbound support (App Service Environment v3 - both internal and external)
Limitations
- Linux sites are NOT supported at this time but will be available in the next few months
How it works
Official documentation in the Azure Learn docs will be provided once this feature is generally available. In the meantime, the following is what you need to know to get started.
IPv6 outbound (dual-stack) allows you to resolve endpoints to IPv6 addresses and call the IPv6 endpoint. There are no changes required in your code to start using IPv6 compatible endpoints.
The first iteration of the implementation does not support virtual network traffic. If your app is integrated with a virtual network and you have application traffic routing, aka "Route All" enabled, you will not be able to resolve or reach the IPv6 endpoint. If you are using virtual network integration and disable application traffic routing, you can resolve and reach public IPv6 endpoints directly. Be cautious with changing the routing though as all your public traffic will not be routed through the virtual network at that point.
Testing
To test IPv6 connectivity, you can use the console. You'll also need an IPv6 capable endpoint. In this case, I took advantage of the public preview availability of inbound IPv6 on App Service and created a web app (named `ipv6`) with inbound IP mode set to "IPv6" and then called these commands ("-6" is optional, but can be used if the endpoint supports both IPv4 and IPv6):
nslookup ipv6.azurewebsites.net
curl -6 https://ipv6.azurewebsites.netWindows will default to IPv4 if the DNS lookup returns both address types. So your app will continue to work without issues with this update.
We Want Your Feedback!
As we continue to evolve App Service to support modern web standards, your feedback is invaluable. Try out IPv6 with your Windows apps and let us know what you think. And stay tuned for updates on Linux support - this blog will be updated when that becomes available.
Microsoft