And using the Rewrite Module pass parameters to pages, so you can change LOGOS or CSS files to fit the desires of your clients.
So a Redirect is not an option as we want to keep the subdomain visible. Also to say that having a subdomain tells your client that he is not another parameter, but a special client.
Francisco Gutiérrez Domínguez
It's a common practice for WebApps to provide subdomain processing:
client1.domainApp.com,
client2.domainApp.com
...
clientN.domainApp.com
And using the Rewrite Module pass parameters to pages, so you can change LOGOS or CSS files to fit the desires of your clients.
So a Redirect is not an option as we want to keep the subdomain visible. Also to say that having a subdomain tells your client that he is not another parameter, but a special client.
I've read a lot of threads (http://social.msdn.microsoft.com/Forums/en-US/windowsazure/thread/1ba9ec61-10b5-464f-8f34-bb7d5fa84697/) and just cannot get a clear picture of how to do this. I think that implementing DNS or giving us information of DNS providers and AZURE accepting any subdomains (having a wildcard) will do it.
¿Correct?