Quotas

Quotas

Overview

Quota management giveslets operators a consistent way to view and manage tenant resource limits acrossfor Azuresupported Stack and CloudStack.platforms. The operationalmain quota surfaceworkspace is the Quotas tab on the Subscriptions page.

Supported Platforms

Platform	Quota modelbehaviour
Azure Stack	TenantShows plan andtenant quota resourcesvalues for compute,Azure storage,Stack andquota network quotas.groups.
CloudStack	TenantShows domaintenant resource limits for CloudStack domains and account resource limits.accounts.

Azure Local and Public Azure quota management are not documentedpart as active quota platforms inof the current featurequota set.workspace.

Region Defaults

Platform administrators can manage region-leveldefault quota templates.templates for supported regions. These defaults are used when tenant platform provisioningresources createsare orfirst reusesprepared.

the

Use region defaults to keep tenant quota resourcessetup forconsistent supportedacross platforms.

new

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.subscriptions.

Subscription Page Quotas Tab

The quota tab lets the operatoruser select:

1. Tenant.
2. Platform.
3. Region.

The selected scope shows current quota or limit state,values, pendingrequested values, approval state, backend sync state,status, and change history.

When no enabled regions exist, the page shows a no-regionsetup emptymessage state.instead of quota controls.

Approval Workflow

Delegated administrators submitcan changes as pending quotarequest changes. Platform administrators approve, reject,review and apply supportedapproved backendchanges changes.where the platform supports it.

Role	Can view	Can request changes	Can approve/approve or 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.management. Platform administrators are not restricted by these visibility settings.

Security

If a user cannot see quota pages or quota actions, check their role, organisation access, selected tenant, selected region, and Scoping

Quota APIs enforce hierarchy access server-side. Tenant, partner, and distributor quota routes also enforce the matching Platform > Quotas visibility settingsettings.

before

Access

returning

Quota data orfollows acceptingtenant, changes.partner, distributor, region, and platform access. Users only see quota records that belong to their permitted organisation scope.

Tenant users are read-only. QuotaTenant, partner, and distributor administrators can request changes arewhere auditedenabled. throughPlatform administrators can manage defaults and approve or apply changes.

What To Check

If quota changevalues history.do not appear:

Operational

Notes

Confirm

Applya quotasupported managementplatform region exists.

Confirm the tenant has subscriptions in that platform and region.

Confirm quota visibility scriptssettings only after taking a MySQL backup. The feature document records a prior development backup forallow the initialuser's quotarole tablefamily.

setup,

Confirm butthe eachselected environmenttenant, stillplatform, needsand itsregion owncombination backupis beforevalid.

applying scripts.

Related Pages

• Regions and Platforms
• Subscriptions and Resource Groups
• Catalogue, Pricing, and Calculator