Source
r/AZURE•
magicwuff

vCPU quota limits have me worried

Question

Hey y'all,

​

My company is launching a new website using Azure. I had no problem spinning up the Dev environment months ago using a total of 12 FsV2 vCPUs among 3 servers. I had to increase the vCPU quota a couple of times to set up these servers along with the domain infrastructure.

​

I have begun testing to spin up the the staging environment which will be needed soon. Due to always on requirements there will be redundancy which will add around 68 more Fsv2's to our quota requirements among a total of 9 VMs. I tried to increase by 68 and was denied, then had to place a ticket.

​

They have since increased the quota, but only for what we need right now. They would not add the other 136 vCPUs that will be needed once Production goes live. However, they also won't give me an answer on how much lead time I will need to give them to get those additional cores.

​

Not sure if this matters, but I have been deploying to East US so far, and half of Prod will go to West US. Another point is that the server requirements are in flux and can change right up until launch. Therefore, we can't feasibly buy reservations this year.

​

So my questions to you all are:

​

  1. Have you ever hit a hard limit on quota increases? Meaning, have you ever been denied when submitting the ticket?
  2. What is the max lead time you have seen when requesting an increase?
  3. Is there something I can do differently to avoid this anxiety all together?

​

Thanks so much for any insight you can give!

Posted May 18, 2022, 3:00 PM UTC

19
RedditBeaver42•

Why would you develop a website to run on VMs?

7
magicwuffOP•

Admittedly, saying "hosting a website" was extremely reductive.

1
karltremain:Microsoft: Microsoft Employee•

Plan in advance your requests for quota increases, (1-3 months in the current supply chain issues) but do be aware a quota doesn't guarantee you capacity, for that you'll need to look into capacity reservations.

Some specific region/sku combinations can occasionally have capacity constraints, so as long as you are flexible on sku's (d/e/f series etc) you shouldn't run into any major issues right now.

quotas are set per subscription, and new/free/payg subs are the least-likely to get approvals if/where capacity constraints exist. Do you have an EA agreement in place, and existing subscriptions?

us west and us east you shouldn't really have any issues (just confirming you dont meant "east US 2" & "west us 2"?)

5
magicwuffOP•

Hello, thanks for your reply.

1-3 months is disheartening since I have historically had 2 weeks notice for standing these up. Though it isn't surprising since we have been waiting for months on hardware quotes for other projects.

I just found out that we have more flexibility in sku's, so I'm not stuck to Fsv2's any more.

I will definitely look into capacity reservations, thanks for that tip.

We are purely payg for now, since the requirements have been so amorphous. We didn't want to pigeonhole ourselves into specific hardware. We just have one subscription right now. I'm not sure about any agreements since that was handled higher up.

Yes, I am using East US and West US for now.

1
karltremain:Microsoft: Microsoft Employee•

although I say 1-3 months, I do mean that more as planning and allowing contingency room. You should expect most quota increases to be quicker, just don't try and do "I'm deploying it tomorrow, i need quota right now" that some people do...

great to see you have some flexibility, you shouldn't have an issue :)

1
magicwuffOP•

Thanks for clarifying!

​

And to follow up, I just requested an increase for EBDSv5's and it went through instantly, no ticket needed.

1
2003tide•

They are having capacity issues now. Prior to all the supply chain madness, quota increase were pretty much automatic.

3
ScarcityNo1073•

I had frustrating experience recently with Azure quotas. 2 months ago we created a new account for our new project. We needed ~300 vCPUs in UK South region, but default quotas were extremely poor (10 vCPUs for most SKUs). All our quota increase requests were automatically denied, so we submitted a ticket. After spending a week with Azure support we were able to get 200 Ds_v5 vCPUs. But that was maximum they agreed to give without changing payment method from "credit card" to "invoice" as per https://docs.microsoft.com/en-us/azure/cost-management-billing/manage/pay-by-invoice. As part of payment method switch our company needed to pass credit check and send some documents to MS for verification.

So, my advice is to check your current payment method and if it's not "invoice", then check with support whether they have similar "200 vCPU max" policy in East/West US regions. I find this policy really annoying, but maybe it's something specific to UK region.

1
karlochacon•

if you go with SAP projects check with your TAM first, in our case we use EU2 but for SAP we have been using EU, also WU2 use WE3 or WU

for example EU2 for Dv4 and Dv5 in AZ1 and AZ2 there is not quota but AZ3 yes, so if you have AZ availability requirements for Dv4 and Dv5 go with EU / WU / WU3

they say it is all Cloud providers not only azure

1