So we ended on Microsoft Azure in Fresno. In hindsight, they would not be my preferred choice of a non-AWS provider to replace Linode. However, with the situati

So we ended on Microsoft Azure in Fresno. In hindsight, they would not be my preferred choice of a non-AWS provider to replace Linode. However, with the situation we were in they were the best choice. We operate all of our datacenters in a multi-master configuration across the WAN, so latency is something we need to be mindful of. We were also in the middle of an emergency situation that required a migration, so we needed a solution that would allow us to evacuate quickly. In the end we decided that we wanted a provider who supported a VPC-like network configuration, and was roughly within the same latency profile as Linode in respect to US-WEST-1 and US-WEST-2. If timing hadn't been a concern, we may have chosen differently. We felt we didn't have the luxury of time.