I've been doing a lot of work with VMs recently and can see the massive advantages of the platform.

It's my understanding that subscriptions are a very good way of managing your clients. For example I have some software which requires a VM, a SQL database and two websites. When I sign up a new client I create a new Subscription which they pay for and deploy my various components to it - they get the hosting bill.

However, it seems to me that where Azure doesn't scale particularly well is when I have a hundred or a thousand clients. It's my understanding I'd need a publish profile for each one and every time we do a release I'd need to deploy 400 components.

Is there a better way of managing multiple instances of your solution?

Hi techhub1337,

I recommend you post the question in the Azure Management Portal forum for better answer.

You can also check the following articles about scaling in Azure.
Designing for Big Scale in Azure
http://blogs.msdn.com/b/kdot/archive/2014/10/09/designing-for-big-scale-in-azure.aspx

Azure Subscription and Service Limits, Quotas, and Constraints
http://azure.microsoft.com/en-us/documentation/articles/azure-subscription-service-limits/



Thanks,
Lydia Zhang