Any of those help I have a multi-tenant app on Azure not to dissimilar to what you describe. For a largish multi-tenant app I would forget about Web Sites and use Web Roles. I also would avoid having a separate site for each client, they should ideally be running through the same role which can be load balanced over several instances. You can still set up host headers (i.e. site1.mysite.com) for each individual user, all running off the same web role. I have all my clients running in the same database, this is not to hard to implement and will scale better (you think Google has a database per client?). There is no reason you can't go to more databases later or you can use SQL Azure Federations and have a federation for each client, but going the other direction is much harder. If you have a separate database for each client you will then have to manage each database (schema updates, backups) individually which could be a lot more work (and expense). Cost will influence design here. A 1gb database will cost $10 a month, so if your clients are only paying $20 a month it is not really viable. But if they pay $1000 month then it is not a problem.
Django doesn't respond on some requests after deployment on server
may help you . Presenting the approach we used to solve this issue. Hope it may help others struck in similar cases. With the problem statement tied to having a single root image and having any customization being applied at runtime, we knew that there needs to be a transformation of web.config at time of loading of the corresponding containers.
Writing a multi-tenant Rails 3 app for deployment on Heroku