580 votes9 comments · Networking » Domain Name Service (DNS, Traffic Manager) · Flag idea as inappropriate… · Admin →
We are evaluating this feature ask. However, it is not on our immediate roadmap.
We have raised the limit to 100 recently. We are regularly reviewing the limits and will continue to look for opportunities to raise the limits even further. If you have scenarios requiring limits higher than what is supported, please add your scenario details here (if you are comfortable with that) or raise an issue with Azure support and we will get back to you.David Schlum commented
Definitely need this. It just so happens that the project I'm working on with a client has exactly 10 unique domains so with http to https redirects and the https listener, I'm able to make it work. However, if the client wants to add even one more site on their multisite CMS, we'll have to spin up a whole new Application Gateway to the tune of $200/month. This seems like an artificial limitation as I've never seen another firewall strictly limit what amounts to reverse proxies behind it. I come from a Microsoft TMG world and it would be unthinkable to only be able to add 20 sites behind one.
In another month when the client is planning to move another site over to Azure and into their multisite CMS, this becomes a problem. Can support at least punch a number in on the backend to lift this limitation?
This remains on our long-term backlog as something we want to offer.- Altaf T
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 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/ApplicationGatewayCohortDavid Schlum commented
Just ran into this today. I have a multi-site CMS that supports subdomains for different sites. It would be ideal to be able to configure *.domain.com so that I don't have to set up separate listeners for every site. I also like the idea of at least giving me the option of specifying multiple hosts per listener. AND, why in the world am I only limited to 20 listeners??
We have shipped a public preview of integration with AAD DS: https://azure.microsoft.com/blog/azure-active-directory-integration-for-smb-access-now-in-public-preview/
What we have in preview is a first step along a much larger roadmap for integration with AAD/AD for authentication and authorization. As the blog post says, this initial preview is really about Windows cloud VM access to the Azure file share with an AAD identity. Future refreshes to this feature will add non-Windows (Linux, macOS, etc) support, and the ability to mount the Azure file shares on-premises with your AAD identity. You can learn more about this in our Ignite session as well (at around 22:00): https://www.youtube.com/watch?v=GMzh2M66E9o
We’ll keep you updated on our progress. In the meantime, don’t hesitate to continue posting feedback on this feature below.
Program Manager, Azure Files