That's because Azure is a poor service with mediocre support. My anecdotal experience: I spent a couple of weeks (!) setting up our environment (Bitbucket, Dja

That's because Azure is a poor service with mediocre support. My anecdotal experience: I spent a couple of weeks (!) setting up our environment (Bitbucket, Django, Ubuntu, Dockerized) on Azure App Service and Azure Pipelines. Their documentation was incomplete, out-of-date and MS support staff struggled to help if you didn't have a Windows machine (their RDP software doesn't support Linux, Skype for Business doesn't support Linux and normal Skype for Linux doesn't support screen sharing). Little things like trying to SSH into any machine so that you can execute commands on your docker container (for, say, database migrations or to check logs) is almost impossible. If it wasn't for the help of a lot of people on #docker in Freenode I would probably still be working on it. I had to use Google Hangouts with a Microsoft support person's personal gmail account, while he was connected over VPN (since he was based in Shanghai), so I could show my issue. The support person was extremely pleasant to deal with and understanding, though, and he went above and beyond to help get my issue resolved even though it turned out to not be from his department. However, after getting set up, I noticed I was getting 12 second (!) responses from an API I had written just to retrieve a logged-in user's first name, last name and email in JSON. This API resolves locally in 20ms - including layers of authentication. This turned out to be a known issue when running a managed "Azure Database for PostgreSQL" service and was common on MS support forums. After reaching out to Microsoft support for Azure Database for PostgreSQL, their response was this, copy-and-pasted: > As you are currently using Basic Tier (2 vCores, 51200MB), the bad performance is expected. > When comparing with the performance in your VM, the on-prem is supposed to be better than cloud even within the same hardware environment. > Please give it a test in higher tier and configure it with a compatible settings compared with your VM. In the meanwhile, you can monitor the slow queries via Query Performance Insight to find out what queries were running at a long time when those API were called. > Pricing tier information can be found at https://docs.microsoft.com/en-us/azure/postgresql/concepts-pricing-tiers#storage https://docs.microsoft.com/en-us/azure/postgresql/concepts-p... . ...they tried to upsell me on the higher tier database 3 times in that email chain, believing that this level of performance was acceptable for my database tier. Of course the next tier up from the $60/month that I was on was $160/month, and since we only have maybe two concurrent users at most it didn't make sense to triple our costs just to avoid 12 second database calls. I moved the entire service to AWS last week. The set up was painless and swift. Using equivalently priced services, the API now resolves in 50ms. I don't think I'll ever go back. Not even for free.