This is a good question. I don't know of one.<p>There are some issues I've seen while trying to run systems there. Some of the network configuration there is very strange, and I've seen some crazy performance issues. Their API is very painful to use as well. Lastly, they run an agent on your node that can gain someone root access (worse than Linode's ability for someone to do that). Finally, their control panel has a basically unlimited session lifetime. I don't think I've had to log in once within the past 60 days.<p>I've found that systems running in Azure reliably perform worse than AWS. Systems in Azure with about the same CPU and RAM have worse performance by anywhere from 2x to 10x. I'm using this based on seeing things like GC run times in both Go and the JVM. The systems report 0.00% CPU steal, no idea where the bottleneck is.<p>Their network also leaves some to be desired. One of the biggest pain points is that they drop ICMP Echo / Echo Reply on the edge of the network. So doing network troubleshooting across the WAN is challenging. Another issue is that they seem to often either drop or de-prioritize UDP packets within their Fresno location. This causes some issues with software that uses UDP for communication. With that are the weird, and confusing, mix-match between NetworkSecurityGroups and Endpoints, with only one of them being configurable in the UI.<p>The last thing is their API and the SDK (at least Ruby). Their API is an XML behemoth with incorrect documentation (e.g., the example URL using a wrong path in the docs), and severe performance problems. There are times where the API takes over a minute to respond to a request, sometimes taking longer to respond with an HTTP 500. Their Ruby SDK, at least, isn't so much as an SDK as a library that's meant to be consumed via IRB.<p>Lastly, the nodes all run an agent called WALinuxAgent. This allows Azure to take action on your node without your approval. It can also do things like add new users to your node, and give then full sudo access. This is also done without a reboot, so you have no indicator that someone just took this action on your system. Scary!<p>I've also seen this agent get weird responses from the endpoints it talks to causing it to think it should reprovision your node. It proceeds to then rewrite your SSH host keys, vomit an exception, and then exit. It's brilliant.<p>Trying to get help from support is impossible. I've had issues with the quality of the responses given, but also issues with them just never responding to open issues. AWS's support team should be commended in comparison.