Better support for wildcard domain mappings
I have a web site with a separate subdomain for each client:
To add a new client in azure websites at the moment I have to
1. Go to my DNS provider and add a mapping for awverify.client3.domain.com (I already have *.domain.com mapped - this is only needed for verification)
2. Wait patiently for that to propagate
3. Add a domain name mapping to the web site configuration
4. Map the new subdomain onto the same wildcard certificate used for every other client sibdomain
If I have a control of awverify.domain.com then surely I will always have control of awverify.anything-else.domain.com - why do I need to verify each subdomain separately?
Ideally I should be able to configure the *.domain.com CNAME record with my DNS provider and then set up Azure once for all subdomains
Wildcard domain support is live. You can assign a wildcard certificate to your wildcard domain with an SNI SSL binding. Look for IP SSL support at the end of April. For more info, see our blog: http://blogs.msdn.com/b/windowsazure/archive/2014/04/23/azure-websites-and-wildcard-domains.aspx
Bhavit Naik commented
Hey, we are seriously waiting for this. We are launching a multi-tenant application which needs per tenant subdomains....
Please respond whether we can expect this soon or have to spin up a VM for that.
Is this up yet? This is the one feature that will allow me to save months of work not having to port an application (build process, etc) to cloud services... REALLY FRUSTRATING. We are coming up on the 8 week mark. Please let me know when I can plan to be able to use this feature so I can plan accordingly. Thank you.
Eliott Stephen commented
Any update on this?
Is there an ETA on this?