Working with all three of them, so here's my two cents: 1. Mostly traditional, "legacy" companies have been hit hard by this. Ones that don't have culture or technology of work-from-home. Those companies use some Microsoft products. Also, Microsoft has been poaching them heavily, handing out trials, bundling licenses and so on. A lot of them don't actually buy stuff from Microsoft, but through 3rd party vendors which have incentives of their own. Some of the end users don't actually want to use AWS, also.

2. I actually think Microsoft has much less runway. From what I understand, AWS has more modern infrastructure and backend, and they shuffle resources easily around, between services, and I think they have much more in reserve. Microsoft has concentrated much more on the sheer number of regions.

3. Azure has a strange way of handling quotas, if you ask me. Up until now, once you provision a VM, it is deducted from a quota and stays like that as long as it exists. It has never been an issue to actually power it on (unlike AWS), once you have it. It's not billed, but we always thought it stays like that. Since last week, you can see failures not only when provisioning VM's (even within your quota) but also when starting them. Nevertheless, I also think a lot of users had larger quotas allocated then they actually use. So they just started creating more VMs or other resources (because they could), and the thing came crashing. I think that's just poor planning on Microsoft's side.

But the thing I'm mostly pissed of is the status page. VM's are failing left, right and center and everything is nice and green on the status page. Once you open a ticket, they send you an incident-in-progress report.