Windows Azure Multi Tenancy To Do or What to Do
===

at the base of starting a new enterprise web application. It will be hosted up on windows azure and will be an asp.net mvc application talking to an sql database.

My question relates to multi-tenancy and the correct way to accomplish it. In the past I've created a multi-tenant application by having a tenant table and than putting TenantID column in every table, this worked fine (but it was only on a smaller scale so didnt really exercise it to the nth degree). Looking into the multi-tenant stuff on Azure and it doesnt seem to recommend this way. They talk about subdomain splitting tenants etc. To me that just seems like a management nightmare. I would like the user to hit a website, enter in their tenant login details and boom they are off.

1. Is there a simpler way to implement multi-tenancy in azure that still allows me to use Azure's scalability strengths? 
2. Should I just use the simple TenantID method? Will the azure framework still scale well to suit?
3. Should I worry about tenancy at the start or just leave it til the end?


Advice needed.

Thanks