From using both, my recommendation is AWS for anything Node-based, Azure for anything else. GCP is severely lacking to both and has never struck me as a serious

From using both, my recommendation is AWS for anything Node-based, Azure for anything else. GCP is severely lacking to both and has never struck me as a serious contender, but maybe there are industries that benefit from the simplicity. I like the control AWS gives you, but it is overwhelming at times. On Azure, everything feels easier to find, and there is not such a steep learning curve. I can set up a site, a repo, my CI/CD pipeline, and a DB within minutes, complete with qa, staging and production deployment cycles, telemetry, and alerts. The reason I wouldn't recommend Node-based deployments with this flow is because Visual Studio and VSTS does not play well with node, feels like it is constantly fighting you to use anything but Node, but for a project in React and an ASP Net Core server, it's incredibly seamless. Meanwhile on AWS, I feel like the control of VMs is a lot better to control. It is more intuitive to set up load balancing schemes on AWS, and the CDN makes just enough more sense than Azure CDN to make me prefer it, but it can't beat the productivity gains I have in Azure, though I feel I just don't have the right use cases to benefit from whatever imrpovements AWS offers. All in all, at this point, you don't lose by choosing either AWS or Azure, other than spending time to learn how AWS services are integrates and what parts of the ecosystem is relevant, so I am not surprised MS is benefiting greatly from Azure.