Quotas
Quotas
Overview
Quota management gives operators a consistent way to view and manage tenant resource limits across Azure Stack and CloudStack. The operational quota surface is the Quotas tab on the Subscriptions page.
Supported Platforms
| Platform | Quota model |
|---|---|
| Azure Stack | Tenant plan and quota resources for compute, storage, and network quotas. |
| CloudStack | Tenant domain and account resource limits. |
Azure Local and Public Azure quota management are not documented as active quota platforms in the current feature set.
Region Defaults
Platform administrators manage region-level quota templates. These defaults are used when platform provisioning creates or reuses the tenant quota resources for supported platforms.
For Azure Stack, region defaults replace the previous static compute, storage, and network quota payload values.
For CloudStack, region defaults are applied to supported standard domain limits during tenant domain/account provisioning. Extended rows without a concrete backend resource type remain CMS-tracked only.
Subscription Page Quotas Tab
The quota tab lets the operator select:
- Tenant.
- Platform.
- Region.
The selected scope shows current quota or limit state, pending values, approval state, backend sync state, and change history.
When no enabled regions exist, the page shows a no-region empty state.
Approval Workflow
Delegated administrators submit changes as pending quota changes. Platform administrators approve, reject, and apply supported backend changes.
| Role | Can view | Can request | Can approve/apply |
|---|---|---|---|
| TenantUser | Yes | No | No |
| TenantAdministrator | Own tenant | Yes | No |
| PartnerAdministrator | Partner tenants | Yes | No |
| DistributorAdministrator | Distributor hierarchy | Yes | No |
| PlatformAdministrator | All quotas | Yes | Yes |
Only platform administrators can approve quota changes intended for the Azure Stack backend.
Backend Sync
Quota records track approval state separately from backend sync state. Backend sync values include states such as not required, pending, synced, failed, or deferred.
Azure Stack quota reads synchronize live quota values before returning tenant quota state. Platform administrator edits apply directly to supported Azure Stack quota payloads.
CloudStack quota reads synchronize live supported standard domain limits. Platform administrator edits apply supported CloudStack limits with updateResourceLimit. Extended CloudStack limits remain blocked from direct backend apply until a concrete backend API exists.
Visibility Settings
Platform > Quotas settings control whether tenant, partner, and distributor role families can see quota management and call tenant or region quota routes.
Missing settings default to enabled for backwards compatibility. Platform administrators are not restricted by these visibility settings.
Security and Scoping
Quota APIs enforce hierarchy access server-side. Tenant, partner, and distributor quota routes also enforce the matching Platform > Quotas visibility setting before returning data or accepting changes.
Tenant users are read-only. Quota changes are audited through quota change history.
Operational Notes
Apply quota management and quota visibility scripts only after taking a MySQL backup. The feature document records a prior development backup for the initial quota table setup, but each environment still needs its own backup before applying scripts.
Related Pages
- Regions and Platforms
- Subscriptions and Resource Groups
- Catalogue, Pricing, and Calculator