Azure Application Gateway IPv6 enablement

Alex 375

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.

KapilAnanth-MSFT 47,196 Reputation points Microsoft Employee

2024-06-24T06:19:05.53+00:00
@Alex ,

Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.

Just checking in to see if the Adharsh Santhanam's answer helped.

We recommend customers to follow the documentations,

If it does, please don’t forget to click "Accept the answer" and Up-Vote for the same, which might be beneficial to other community members reading this thread.

And, if you have any further query do let us know.

Thanks,

Kapil
Alex 375 Reputation points

2024-06-25T08:56:40.2766667+00:00

Hello Kapil,

Yes, that answer did help, but I still feel like the documentation is wrong or resource restrictions need to be updated.

When the documentation says that we 'can't' upgrade, then, we as customers shouldn't even be able to upgrade or configure IPv6 listeners on a IPv4-only AppGw, right?, but we are able to configure it now, which is misleading.

Either the documentation needs to be updated properly or I need help in passing this info to product group, so they can fix the restrictions policy on IPv4-only AppGw's :).

And also, how can the customers know if the AppGws are IPv4-only or dual-stack? Where can we find this information from AppGw? Because at this point, even my IPv4-only AppGw shows options to configure IPv6. Thank you again for all the help :).
KapilAnanth-MSFT 47,196 Reputation points Microsoft Employee

2024-06-27T12:40:03.9766667+00:00
Hi @Alex ,

You are welcome and I totally understand your concern.

Wrt, "When the documentation says that we 'can't' upgrade, then, we as customers shouldn't even be able to upgrade or configure IPv6 listeners on a IPv4-only AppGw, right?"

I disagree

It is possible that there are some features in the pipeline and hence, you are able to make these configurations.

However, we recommend customers to review our documentations for limitations and unsupported scenarios.

Wrt,"Either the documentation needs to be updated properly or I need help in passing this info to product group, so they can fix the restrictions policy on IPv4-only AppGw's"

I agree.

I have started working with the Product Team to get the document updated.

Meanwhile, you can also raise a support incident to bring more traction to this.

Wrt, "how can the customers know if the AppGws are IPv4-only or dual-stack? Where can we find this information from AppGw?"

I couldn't find a property that differentiates between a IPv4-only or dual-stack App Gw.

I will revert back with the details on how the platform differentiates between a IPv4-only or dual-stack and if the end user can check it from Portal or not.

Cheers,

Kapil
KapilAnanth-MSFT 47,196 Reputation points Microsoft Employee

2024-07-01T05:04:17.1533333+00:00

@Alex ,

Greetings.

I got an update from Product Team and they informed me that there are plans to block upgrading IPV4 App gateway to dual stack in the Pipeline (currently, no ETA).

There isn't any specific property you can use to identify if a gateway was originally created as IPV4 only or dual stack.

If a user has missed the instructions/not documented where activity is performed (adding IPv6 frontend), the suggestion is to leverage Activity logs to identify the addition/change.

Let me know should you require more information.

Thanks,

Kapil

Please don’t forget to close the thread by clicking "Accept the answer" wherever the information provided helps you, as this can be beneficial to other community members.
Alex 375 Reputation points

2024-07-01T05:25:14.12+00:00
Thank you, @KapilAnanth-MSFT for all the follow-ups and support.

Yes, I do agree Platform should block the upgrade of an IPv4 Appgw to dual-stack.

And also, it would be better to have that specific property which can be used to identify the AppGw network stack. Can you help in passing on this feedback to Product team?
KapilAnanth-MSFT 47,196 Reputation points Microsoft Employee

2024-07-01T05:32:09.9933333+00:00

@Alex ,

You are most welcome.

Sure, I shall do that.

Thanks for your continued contribution on Q&A and appreciate much for taking the time to share your feedback.

Meanwhile, I'd highly appreciate if you could Accept the answer by Adharsh Santhanam and close this thread

Original posters help the community find answers faster by identifying the correct answer and this helps with SEO

Cheers,

Kapil

1 answer

Adharsh Santhanam 4,370 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.
Please sign in to rate this answer.
Alex 375 Reputation points

2024-06-20T15:16:45.5+00:00

Hello Adharsh, yes, that's right. Thank you for your prompt inputs on this. :)

I just thought it would be good if the Properties of the AppGw or the resource JSON of the AppGw highlights or points out that it is only IPv4 or supports dual stack, etc and the users have the visibility to see this information.

Because right now, that info is not visible and users can also configure IPv6 on a IPv4-only AppGw, which should be restricted/not allowed I believe, so that it isn't misleading.

Adharsh Santhanam 4,370 Reputation points

2024-06-21T04:57:32.29+00:00

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.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Azure Application Gateway IPv6 enablement

1 answer

Your answer