Thank you for all the votes and feedback. We have started work on this and the capability will be supported soon. If you would like to get in touch with us to discuss your scenarios, please fill this form: https://aka.ms/ApplicationGatewayCohort
Thank you for your feedback. We plan to address this gap.
Bridget [MSFT]Anonymous shared this idea ·
DNSSEC remains on our long term roadmap, however it is unlikely to be available in CY 2019. If DNSSEC is a critical and immediate requirement for your business we’d suggest that you consider evaluating 3rd party DNS hosting solutions that provide this feature.
This is good feedback. Can you give a few more comments on WHY you want this?
Thanks for the feedback. We do plan to improve the performance and scale of Azure VPN gateways. We will provide more updates once we have concrete plans and measurements.
This remains on our long-term backlog as something we want to offer.
Thank you for your feedback and sorry for the inconvenience of the previous update.
- Tim M [MSFT]
Support for both public and private IP at the same time is available on both V1 and V2 SKU. Customers can host multiple sites behind the same IP and port using multi-site listener today.
Support for allowing same port on both public and private IP is in the roadmap.
Thank you for your suggestion. We are reviewing it at this time.