This repo contains best practices and helper code for managing quota in Azure.
Quota is granted regionally. Access to availability zones is requested separately.
- Query : Resource Skus – List (customer will just see the Region/Zone not available for the sub)
- Quota API : Azure Quota REST API Reference | Microsoft Learn
- Service Request : Request quota increase via Support API | Microsoft Learn
- Zonal Access : Azure region access request process - Azure | Microsoft Learn
This is the fall-back path for scenarios where quota cannot granted via the Quota API or where AZ enablement is required. There are 3 API calls involved in creating the support request – 2 of which can be cached per subscription:
Zonal capacity requests are classified differently to typical quota requests.
- Issue Type: Service and subscription Limit (quotas).
- Quota type: select Other Requests.
- In Subscription, select the relevant subscription for which you would like to request access.
- If you want to enable the region access for multiple subscriptions, you can include the additional subscription IDs in the Description section in the next page, thereby avoiding the need to fill out multiple support requests.
| Field | Value |
|---|---|
| Region to Enable | insert the region you are requesting access to |
| Deployment Model | ARM |
| Planned VM types | For example, Dv3 Series |
| Planned Compute usage in Cores | 25 |
| Planned Storage usage in TB | 10 |
| Planned SQL Database SKU | For example, S0 |
| Planned No. of Databases per DB SKU (20 DB limit per SKU) | 20 |