Comment by kjs3

I don't think that's it. I think Microsoft wanted a way to migrate already Microsoft workloads to something they could more aggressively bill by the GB or second or user or whatever revenue extraction metric you're down with. Basically, O365 extended to the entire M$ ecosystem. And for that it seems...er...ok. We've migrated a couple of dozen major M$ workloads from on-prem reasonably easily, and a bunch of little ones. Lots of skillsets transferred easily...I vividly recall talking a really fine SQLServer admin off the ledge when the "move to cloud" mandate came out who's now like "I had to learn a few new things, but it's pretty much like what I was doing before". Big win.

But then everyone said "a cloud should do X and Y and Z", and they try to bolt X/Y/Z on to the side with various levels of success. And now all the app owners who aren't native M$ have declared Azure not fit for purpose and picked up the torches and pitchforks. So we're going to support AWS, too.