CODEWITHSUNDEEP
azure
Tomas Aschan
Tomas Aschan

Reputation: 60574

"No quotas available" in brand new Azure subscription

We have a brand new (as in, created a couple of days ago and no resources in it yet) Azure pay-as-you-go subscription, and now when I try to provision something, I'm not allowed.

Looking at the subscription in the portal, under "Usage + quotas" the list is empty.

Did we do something wrong when signing up? How do we enable it?

Upvotes: 5

Views: 4085

Answers (3)

edwin chantre velasco
edwin chantre velasco

Reputation: 1

The solution is to register Microsoft.Compute.

Same solution applies when you create the kubernetes service for the first time, the quotas is empty in your account, and you receive the following message when trying to create kubernetes:

Preflight validation check for resource(s) for container service aksdemo1 in resource group aks-rg1 failed. 
Message: Insufficient regional vcpu quota left for location eastus. left regional vcpu quota 0, requested quota 32. Details: 
(Code: ErrCode_InsufficientVCPUQuota)

Upvotes: 0

Hick
Hick

Reputation: 459

You only need to register to the Microsoft.Compute Resource Provider on the Subscriptions Blade.

  • Go to Subscriptions
  • Select the desired subscription
  • Click on Resource Providers
  • Register to the option "Microsoft.Compute"

Upvotes: 9

Tomas Aschan
Tomas Aschan

Reputation: 60574

Turns out there were some things I could do myself on this, and some things I had to turn to Azure Support for.

Thing I could do myself: Enable a bunch of resource providers

It turned out the subscription did not have a single resource provider enabled. To fix, I found the Subscription blade, and clicked the "Resource Providers" menu item (toward the bottom). That opened up a list where I could register lots of stuff. This also enabled corresponding quotas on the subscription.

Thing I couldn't do myslef: Increase e.g. VM quotas

Some of those quotas, however, I wasn't able to figure out how to turn on myself. Crucially, one of them was for provisioning VM:s (including "hidden" ones, e.g. the underlying VM:s in an AKS cluster or an App Service). Thankfully, Azure Support were really responsive and from first contact until I was able to provision stuff took less than a business day.

Upvotes: 1

Related Questions