What is the best way to organize an ASP.NET application in the Azure cloud?

Question

ASP.NET

Good afternoon!
There is an ASP.NET application hosted in Azure which works with SQL DB. The application is roughly speaking a highly specialized CRM system. Used within the same organization, i.e. works with one DB.
Now you need to raise a cloud service with this application for other organizations.
The application has a Web.config which specifies the database connection string and which modules to use. Of course, each organization should have its own database and its own set of modules.
1. I understand that the best option is to deploy one cloud service, and not for each client an application instance? In the second case, there will be hell for the administrator.
2. In this case, what is the best way to organize the pickup by the same Web.config application for different clients?
3. Or maybe you need to rewrite the logic and make Web.config default for everyone, and take the connection string and other client/organization data from another place?
Knowledgeable people, please tell me where to dig and how best to organize. Thank you!

Answer 1

Hell is hell, but if some fall, others will not suffer. More beautiful, of course, is the option with a single webconfig, but these are all eggs in one basket.

Answer 2

Azure claims 99.95% uptime.
It's different here - we have updates quite often, once a month it's stable, so even 50 cloud services to update is still that task.