Support wildcard hosts in custom hostnames
Many of current SaaS applications enable customers to select it`s own subdomain in order do have a personalized url.
So let's say I own contoso.com and I let my customers select any subdomain (*.contoso.com) like:
That's cool with a couple customers but when you have a large system it's not doable setup one by one, even that you can automate that.
The ideal solution would be allowing custom hostname field to bind a wildcard domain, in this example *.contoso.com
There's a similar idea for Application Gateway that has been for a while (https://feedback.azure.com/forums/217313-networking/suggestions/19527121-application-gateway-support-wildcard-hosts-in-lis)
Similar products on AWS and CloudFlare already support this option.
Application Services already support binding wildcard domains also.
What's the dev time for a feature like this? I know it says "STarted", but does stuff like this have to release on some publish schedule or major version updates? Or can it be expected to just roll out with in a few weeks?
Mark Middlemist commented
Just checking, I know it's not mentioned explicitly, but will this be available for use in Front Door once completed?
This is a must have for us.
This is essential. We'd really like to try this or Application Gateway to replace a lot of our infrastructure, but until wildcard hostnames are supported both solutions aren't usable.