As a user of AWS/GCP/Azure, Azure is the one where we have the most issues, the most services that somewhat work but never right and where it is the biggest pain to actually get up and running successfully. We've also run into a lot of random limitations that are massive pain points in building automation against Azure where there's a mixture now of terraform, Powershell, and Azure Resource Manager templates to try and enforce state.

We have also found that we are spending almost 25% more in Azure for similar compute capabilities as we've had to launch more servers to meet expected baseline performance (or pricier systems).

The lack of proper AZ's in certain locations is also a huge bummer, on top of that, we've found that in certain regions you will have certain instance types that are available in one AZ but not the other. So you end up having to find somewhat equivalents and rewrite infrastructure as code to deal with that mess.

Last but not least is the fact that GCP and Azure both don't have great support for IPv6. AWS may have been late to the game, but it's easy to deploy, and it just works. Whereas in GCP you have to be in certain regions, and in Azure I still am not sure what they were smoking with giving such a tiny public IPv6 prefix: https://learn.microsoft.com/en-us/azure/virtual-network/ip-s...