Disclaimer: This is work in progress intended to consolidate information from various sources for learning purposes. For the latest information please consult the documentation (see the links below)!
Last updated: 13-Apr-2025
[Microsoft Fabric] Quotas
- {def} assigned number of resources for an Azure subscription
- depend on the Azure subscription type [5]
- set and enforced in the scope of the subscription [1]
- each subscription has a default value for each quota [1]
- determine the maximum number of CUs for each of the capacities on the subscription [5]
- customers don't get charged for quotas, but on capacities [5]
- each quota represents a specific countable resource
- e.g. number of VMs that can be created [2]
- e.g. the number of storage accounts that can be used concurrently [2]
- e.g. the number of networking resources that can be consumed [2]
- e.g. the number of API calls to a particular service that can be made [2]
- designed to help protect customers from unexpected behavior [1]
- e.g. inaccurately resourced deployments, mistaken consumption
- helps minimize risks from deceptive or inappropriate consumption and unexpected demand [1]
- limitations
- ⇐ some limits are managed at a regional level [2]
- ⇐ variable and dependent on several factors
- {type} adjustable quotas
- quotas for which customers can request quota increases
- via Azure Home My quotas page
- based on amount or usage percentage and submitting it directly [1]
- each subscription has a default quota value for each quota [1]
- the quickest way to increase quotas [1]
- {type} non-adjustable quotas
- quotas which have a hard limit, usually determined by the scope of the subscription [1]
- to make changes, customers must submit a support request for the Azure support team [1]
- [Fabric] limit the number of CUs customers can provision across multiple capacities in a subscription
- calculation based on
- subscription plan type
- Azure region
- {action} provision a new capacity
- {level} Azure management group limits
- {level} Azure subscription limits
- {level} Azure resource group limits
- {level} Template limits
- {level} Microsoft Entra ID limits
- {level} Azure API Center limits
- {level} Azure API Management limits
- {level} API Management v2 tiers
- {level} Azure App Service limits
- {level} Azure Automation limits
- {action} request quota increase
- via support request
- there is no cost associated with requesting a quota increase [1]
- ⇐ costs are incurred based on resource usage, not the quotas themselves [1]
- should be based on workloads' characteristics [1]
- {action} view quota
- [permission] contributor role, or another role that includes contributor access [5]
- {action} manage quota
- [permission] see Quota Request Operator
- [Azure] quota alerts
- notifications triggered when the usage of a specific Azure resource nears the predefined quota limit [4]
- facilitates proactive resource management [4]
- multiple alert rules can be created for a given quota or across quotas in a subscription [4]
Previous Post <<||>> Next Post
References:
[1] Microsoft Learn (2024) Fabric: Quotas overview [link]
[2] Microsoft Learn (2025) Fabric: Azure subscription and service
limits, quotas, and constraints [link]
[3] Microsoft Learn (2025) Fabric: Quota monitoring and
alerting [link]
[4] Microsoft Fabric Update Blog (2024) Announcing the launch of Microsoft
Fabric Quotas [link]
[5] Microsoft Learn (2025) Fabric: Microsoft Fabric capacity quotas [link]
[5] Microsoft Learn (2025) Fabric: Microsoft Fabric capacity quotas [link]
Resources:
[R1] Microsoft Learn (2025) Fabric: What's new in Microsoft Fabric? [link]
Acronyms:
API - Application Programming Interface
CU - Capacity Units
CU - Capacity Units
VM - Virtual Machine
No comments:
Post a Comment