I believe it is well known that Azure East US has capacity issues, and particularly with regards to Postgres instances for some reason. People I know are looking to move workloads to one of the central US regions ("North Central US", "South Central US", ...) as an alternative to East US. I believe this is based on a direct recommendation from Microsoft.

I've always had capacity/quota issues with Azure compute. I would never pick them as my primary vendor. They're great at some cloud stuff (AAD/EntraID/Office/MDM), but everything else is a really bad time. Using AWS & Azure together is generally the best path.

Setting up federated access into AWS via Azure is good way to make this not suck. You can put a VPN between Azure and AWS and it almost feels like one cloud. You can spin up EC2 machines and have them talk to your private resources in Azure (and vice versa, I suppose).

I’ve also run into various capacity issues in each US region I have worked in. East US 2 has been least constrained for me, but I recall that I was still bouncing around between VM instance types to find one that worked last time I deployed fresh.

Newer generation SKUs (which that one is) are often in short supply. I have plenty of bad things to say about Azure, but I've never had trouble getting capacity older than bleeding edge in eastus2 and centralus regions, at least.

I hear that yes, Azure is capacity constrained at present.