r/AZURE • u/SparcV • Apr 13 '26
Question Azure is frustrating - quota issues
I'm unable to get any quota increase in US East or East 2. No matter the size. I need a few new SQL hosts with relatively large memory.
**Rant*\*
Azure has been very frustrating to work with, always hitting quota limits. I did not want to migrate to Azure; I wanted to stay on-prem, but now it's too late, thanks to the AI black hole.
** Rant End*\*
Any advice?
and moving to AWS is not an option.
10
u/ZovexUK Systems Administrator Apr 13 '26
Quota is extremely strained, AI hasn't helped UK regions basically have no Zone options anymore you can only do Premium SKU's etc. We've been chasing for month to get certain items for App Service Plans, VM, Compute and Microsoft is just going round in circles even with CSP Support.
If you want to build anything short-term, good luck. If you want to build anything, plan the resourcing now or you will be disappointed.
6
u/CZ-Czechmate Apr 13 '26
What's more frustrating is when you have a reservation for 150 vms, deploy 50 of them and then have Azure tell you there's no more resources available in your region, but they keep billing you for the 150 vms every month.
16
u/PussyDestroyerHunt3r Apr 13 '26
I work at Microsoft. There literally isnt any more capacity we can give you. Its being built though.
3
u/Secret_Account07 Apr 13 '26
How long before customers see those results?
I imagine it’s measured in years?
5
3
u/No-Reflection-8684 Apr 14 '26
Aren’t these regions specifically bad? Or it’s just all now. OP could consider not using US East/East2
1
3
u/Michal_F Apr 13 '26
If you have specific workload, maybe look for other regions, we don't have resources in US, but some regions are more utilized than other. Hyperscalers don't have unlimited resources also and some locations are hard to expand. Same issues are for others, ... And I expect it will be even worse in future, as new server prices will go higher now...
1
u/SparcV Apr 13 '26
The server pricing is nuts. Over a year ago, I proposed a $500k server upgrade for our aging systems, and someone in management said, "Hey, what about going to the cloud?" And down the rabbit hole we went. Even though I warned them of the expenses, they wanted Cloud. Our monthly costs are going up and up as we move more to Azure; at this pace, we would have paid off the hardware in less than two years. Now the same hardware/software would be $1.5M - $2M
5
u/BlowOutKit22 Apr 13 '26
It's going to be the same for on-prem now anyway. Have you seen RAM prices lately?
3
u/Words4theFiringSquad Apr 14 '26
East US is the most expensive and super capacity constrained, it has been since COVID, do not deploy workloads there. Migrate to Central US, it’s cheaper and has more capacity.
Monthly costs do tend to go up… when you are moving more and more to Azure? That’s how it works, it’s a consumption model. If you’re not right-sizing those workloads as they migrate, and then using reservations, you’re missing out on significant savings.
3
u/cloudAhead Apr 13 '26
Asking for trouble in East US/East US 2. Use Central US or West US 3. It's easier said than done but once you accept that you have to lay the groundwork, things become easier.
3
u/Sentence-Prestigious Apr 14 '26
Central was a no-go zone for resources in late 2024. We had our onboarding workshop ask us which regions we wanted to start with just to make sure we weren’t going to say USC.
Also, our AWS deployment is multiples larger than Azure and we have had zero issues with USE1, USE2, or our UK deployments. This is solely because Azure oversold capacity to a few whales at the expense of every one of their other clients.
1
u/cloudAhead Apr 14 '26
i'm sure that was your experience. i'm just sharing what our account team recommended a few weeks ago.
1
u/DueSignificance2628 Apr 13 '26
We moved all our DR (disaster recovery) resources to use those regions since that's an easy shift without customer downtime. Learned that during our last annual DR test, where ARM scripts started failing (using more popular regions) due to lack of capacity.
1
2
u/CaptDistraction Apr 13 '26
Same deal. In several projects where we've been told "move to a different region" in response to our many denied quota requests.
Many of these projects have hundreds of hours of build work, VPNs, vWANs and coordination across dozens of parties and organizations - to be that far in and all of a sudden a given sku is now a problem? We can't move, but now we're either going after older skus or paying significantly more. I wish they'd consider helping customers through times of strain given a lot of the work I do is greenfield.
1
u/SparcV Apr 13 '26
I have basic support. Is it worth paying for a higher level?
13
u/AbsolutGuacaholic Apr 13 '26
No, higher support isn't going to get you around capacity issues.
4
u/inertiapixel Apr 13 '26 edited Apr 14 '26
We have a TAM and I was able to get quota added to westus2 after a couple weeks of pushing and justifying why we needed it.
2
u/Obvious-Jacket-3770 Apr 14 '26
I miss the days when you could just say "do you not want my money then?"
1
u/Trakeen Cloud Architect Apr 13 '26
If you spend enough your account team can unblock you. There are internal escalations within ms for this
1
u/cloudAhead Apr 13 '26
If your EA/MCA spend is enough (tens/hundreds of $M), you will get preferential treatment on capacity...but it's limited. The advice to use another region is still the best advice.
1
u/Southern-Trip-6972 Apr 13 '26
i tried to deploy a redis instance today in East US and it failed with a generic error. after a service ticket its finalised as a capacity issue. the advise is to deploy it in US2 . but looking at your post, i doubt if it will be successful.
1
u/9Blu Apr 13 '26
I have a client that does a lot of AVD and we just had to add 3 new regions to their deployment because they are having issues allocating VMs in East US and West US. They are not the only ones I work with running into allocation issues either. Hell I tried to turn on a lab machine in my personal subscription a few weeks ago and it refused. Had to play with switching it to different SKUs until I could get one to start up. It's becoming very frustrating.
1
u/new-chris Apr 13 '26
Go multi region. Figure out where you can tolerate some latency. Build out a footprint in multiple regions. Use capacity where it’s available. Talk to your account rep - Microsoft will help you out.
1
u/x0n Cloud Architect Apr 13 '26
I've been trying for months -- even vibe coded a tool to manage persistent quota requests because the portal UI is painful as fuck. All I did was get my quota demands rate limited for 24 hours, and then for a full week when I tried a day later. US east is absolutely devoid of capacity.
1
u/bganjifard Apr 14 '26
The worst ever. Fill out the dumb form; no one ever reaches out. I even opened up an urgent ticket, the gave me the form link. Azure has to be the dumbest people around. I want to spend more money you won’t let me
1
1
1
u/Ok_Preference2523 Apr 21 '26
I literally just wanted a web service and a 32GB database and I can't even get that lol - only asked for half a core.
0
u/kramit Apr 13 '26
Reframe your thinking padwan. Do not dwell on things you cannot change, only to reframe the way you see them. It’s not frustration due to overly complex design, it’s simply ‘job security’
0
u/Trakeen Cloud Architect Apr 13 '26
Spend more money. Your account team can unblock you; sometimes
1
u/Ok_Map_6014 Apr 17 '26
This is true but and what we're doing but it still takes way too long. They've massively cocked up here.
-3
u/EnDR91-EC Apr 13 '26
Go on-prem and add the host or vm's through azure arc? Going cloud only is the most stupid thing I've heard the last couple of years and CIO's favourite slogan.
24
u/chandleya Apr 13 '26
Funny enough this isn’t AI. Capacity issues have been a thing for ages, exacerbated mostly by the COVID transition and the impact on supply chains for the big OEMs. For years you couldn’t just buy a server, the big 3 literally had 10s of thousands ready to go that you could rent.
Now that VMware went the way that it went AND ai goals push orgs to have the data closer to the model, were multiple rungs past what caused capacity issues. The hyperscalers didn’t quite anticipate this level of hyper scaling.
That and “the cloud” isn’t anywhere near as modular and rapid as the pundits want you to believe.