Background
Our company develops and hosts websites for approx. 500 customers, each customer has one website. Each site is built on ASP.net. Our current hosting infrastructure is built on hypervisors with virtual machines running Windows. We have 3 virtual machines that work according to the same specification (8 cores, 24 GB of RAM). 500 client sites are divided into these three web servers, there is no load balancing or fault tolerance - the site exists in only one place.
Consequently, as customers accumulate, the number of web server sites increases. When we maximize each server, we start another one online and start again, and then when it is full, we start another virtual machine, etc.
purpose
We would like to (eventually) move our sites to Azure, however we do not want to copy our existing configuration to Azure, instead we would like to move each website to an Azure Web application, instead, to take advantage of the scaling.
We would also like more small-scale control over our expenses when connecting additional additional sites. We currently offer an online virtual machine and cost us X (for an empty server), it may take 3 months to complete this. We would like to steadily add not big steps to hosting hosts.
, Azure Web- 100 . , - -, 1:1. , ..
-, , , Azure Apps - , - ASP.net , , , . , - - ?
- Azure ( , -, Azure), .