Learn about Quota’s in Azure

Today, I’m going to discuss the topic Quota’s or Limits in Azure.

What is a Quota in Azure?

Quotas are nothing but limits. For each resource in Azure there is some allocated quota. These quotas are set and enforced in the scope of the subscription level and are shared across all resources within it.

Quota’s helps protect customers from inaccurate resource deployments and mistaken/unintended consumption.

A quota is shared across all the services in your subscriptions. Quota’s are measure in vCPUs. Depending on the workload we might need anywhere from a few vCores to several dozen.

How to View Quotas:

To view the Quotas, sign in to the Azure portal and enter “Quotas” into the search box. Under settings -> Select My quotas.

This page is a centralized location where you can view your quotas.

You can filter based on your subscription, Region, Current Usage.

Deciding the quota or limit involves understanding your project’s specific needs and usage patterns.

1. Assess Your Requirements

2. Estimate Resource Usage

3. Review Default Quotas

4. Request Increases if Needed

For suppose on a subscription where you plan to include Networking, an App service plan and Azure Sql Managed Instance. How would you determine the required vCPU?

Let’s break down each component.

For Azure App Service Plan, quota depends on the pricing tier you choose (Basic, Standard, Premium, etc.). Each tier has different limits on the number of VM instances and the size of those instances. For a moderate workload, you might start with a Standard or Premium tier, which can handle multiple instances and provide better performance.

Check the vCPU and Remote Storage (GB). Choose the service plan based on the project requirements. Suppose for a small to medium-sized applications, it needs at least 2–4 vCores should be sufficient for moderate workloads and development/testing environments. For production it is better to go for premium service plan to have a larger storage.

The quota for an Azure SQL Managed Instance depends on the instance. Example, a small instance might require 4–8 vCores, while a larger instance could need 16–32 vCores.

If a subscription exceeds the quota, you will see that Managed instance is not available for the chosen subscription and region.

At this point, you might need to increase the quota.

So overall how many vCores are needed for the entire subscription?

In total, you might need approximately 6–10 vCores to start with.

To Submit Quota increase from Azure Portal:

You can submit a request for a quota increase directly from My quotas.

Select a provider on the right side such as Compute.

Near the top of the page, select New Quota Request, then select Enter a new limit.

In the New Quota Request pane, enter a numerical value for your new quota limit, then select Submit.

For more information, see

https://learn.microsoft.com/en-us/azure/quotas/quickstart-increase-quota-portal

The limits can’t be raised above the Maximum Limit. If there is no Maximum Limit column, then the resource doesn’t have adjustable limits.

You can request an increase for a quota that is non-adjustable by submitting a support request. For more information, see **Request an increase for non-adjustable quotas**.

let me know your comments below.