Ask HN: Is Azure capacity this constraind or am I doing it wrong?

10 points by lanycrost 9 hours ago | 12 comments

I'm working with AWS for many years, and currently I'm working in product with suppose to be cloud agnostic.

I started with AWS and now it's time to spin up it into Azure (because many enterprises using azure for some reason).

I started in US EAST region in azure and at beginning I had an issue with Postgres Flexible, raised a support ticket, and in the result they recommended me to move to another region. The overall conversation to say this takes about 1 day.

I've moved to US EAST 2, and after AKS deployment I stuck with vCPU (Standard Dasv7 Family vCPUs) quote (100) and here we go again... They send me the same message template as they do for previous ticket...

> ... > Your ask for quota has been reviewed and backlogged at this time. It will be reviewed again when additional capacity becomes available. We do not have an ETA for when your request can be fulfilled but please be assured that we will continue working on it and update you as soon as we have more details to share and/or process the request. > ...

I'm already waiting for more then 1 day, and there is no responses from their support.

Long Story Short: Because I don't want to wait for days, weeks and months to be able to test infrastructure on Azure. If it will be my decision I just stop and forget about this nightmare. Please suggest the regions and instance types with which I will not have issues.

wmhmccarty 9 hours ago |

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.

lanycrost 8 hours ago | |

I'm not sure is it right but I'm requesting Total Regional vCPUs (100) and after getting approval Standard Dasv7 Family vCPUs (100) and this one always rejected I've tried many regions.

lanycrost 9 hours ago | |

I'm trying to increase the quotes region by region, already tried your mentioned ones and got the same issue. I've tried poland with tbe same issue, that's why I'm asking :(

rconti 2 hours ago |

This is absolutely the case. I don't have great insight into their capacity but we're mostly using `canadacentral1`

bob1029 8 hours ago |

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).

lanycrost 7 hours ago | |

It's not for me, it's for the enterprises who will integrate our ecosystem in their environment. If it will be my decision I will just forget about the azure, I hate their culture and way they working.

cjcampbell 7 hours ago |

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.

lanycrost 7 hours ago | |

will be great if you'll share the family name you are using.

beaviskhan 7 hours ago |

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.

lanycrost 7 hours ago | |

what type you use, seems it allows me to increase the quote for dasv5 to 100. Hope I will not have issues further.

beaviskhan 7 hours ago | | |

We are mostly using Standard_DXds_v4

SideburnsOfDoom 5 hours ago |

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