"cloud services" isn't really an IaaS at all. Kinda. Cloud services were a deployment model where you basically built code that deployed to two types of "roles"

"cloud services" isn't really an IaaS at all. Kinda. Cloud services were a deployment model where you basically built code that deployed to two types of "roles". Web roles serviced http calls. Worker roles just executed code from a given entry point/method. Typically an app would be user facing web roles, azure storage or azure sql for persistence, and then worker roles for async processing. They are trying to get cloud service customers to migrate to Service Fabric, which, to be fair, is super dope. Not kidding. It's rad. I've deployed a couple of things on it and its bad ass. Love it. Never really used cloud services. Azure IaaS is really just what you would think. It's actually quite good. They don't have the "spot market" type instances that Amazon does. They don't oversubscribe CPU cores. (I think they may have one VM type that gives you a "partial core", otherwise your VM core is yours.) To get the most out of it you need to build with update and fault domains in mind. Here's a link... https://docs.microsoft.com/en-us/azure/virtual-machines/virtual-machines-windows-manage-availability https://docs.microsoft.com/en-us/azure/virtual-machines/virt...