Share via

Azure Application Gateway IPv6 enablement

Alex 330 Reputation points
2024-06-20T13:18:34.48+00:00

Hello,

Good day!

I was working on enabling IPv6 support in Application Gateway and stumbled upon the documentation which mentioned below,

Currently you can’t upgrade existing IPv4 only Application Gateways to dual stack (IPv4 and IPv6) Application Gateways.

But, I just observed that after updating the Vnet and Subnet with IPv6 address space where the AppGw is deployed, I was able to see an option to configure IPv6 frontend IP on it.

So, I went ahead and configured the IPv6 FIP, listeners, routing rules, etc on the existing AppGw and I was able to ping the endpoint, but not able to connect through curl/browser, which I believe it is proving/conforming to the above highlighted statement.

But, isn't it kind of misleading to see an option to setup IPv6 on existing IPv4 AppGw's? :)

Just wanted to share across my experience and get clarified regarding my approach and confusion as stated above.

Thank you in advance.

Azure Application Gateway
Azure Application Gateway
An Azure service that provides a platform-managed, scalable, and highly available application delivery controller as a service.
993 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Adharsh Santhanam 2,310 Reputation points
    2024-06-20T14:49:09.97+00:00

    Hello Alex, I believe that the documentation is correct about stating that an existing IPv4 app gateway cannot be upgraded to IPv6. My reading is that while the option is visible, it's essential to recognize that enabling IPV6 on an existing IPv4-only gateway doesn't guarantee functionality. As you observed, pinging the endpoint works, but more complex functions *such as using curl, browser etc.) remains constrained by the original IPv4-only design.

    Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.