Skip to main content
Reference

Quotas and limits

Azure Container Apps Sandboxes provide fast, secure, ephemeral compute environments designed to scale rapidly. Plan and size your solution with sandbox quotas and limits in mind, check your current quota, and find out how to request increases where supported.

Azure Container Apps Sandboxes quotas and limits​

Quota or limitAmountScopeCheck your current quotaRequest more quota
Concurrent active cores300per region per subscriptionView current quota levelsRequest more
API rate limits3,000 requests per minuteper region per subscriptionNot shown in quota managementRequest more
Number of sandboxes100,000per sandbox groupNot shown in quota managementNot changeable
Number of snapshots, volumes, disk images, secrets, egress rules and connections1 million for each resource typeper sandbox groupNot shown in quota managementNot changeable

Concurrent active cores are the total cores allocated to all active (running) sandboxes at the same time. The number of cores allocated to each sandbox depends on its size. For example, an XS sandbox uses 0.25 cores, while an XL sandbox uses 4 cores. Stopped sandboxes do not count toward this quota.

Concurrent active cores and API rate limits apply independently to each subscription and region combination. For example, if your test and production subscriptions both need a higher quota in the same region, two quota increase requests must be submitted, one for each subscription.

Each sandbox group has limits on the number of resources it can contain. If you need more sandboxes than a single group allows, distribute them across multiple sandbox groups within the same resource group or subscription.

Your current quota may differ from the defaults listed above.

View current quota levels​

View your concurrent cores quota in the Azure portal:

  1. Open My quotas in the Azure portal.
  2. Select your subscription.
  3. For Provider, select Azure Container Apps.
  4. For Region, select the Azure region you want to check.
  5. Find the Sandbox Cores quota for your organization.

You can also use the Azure CLI to view quota limit and actual usage for a subscription and region. Sign in with az login, then replace <subscription-id> and <region> with your subscription ID and the region where your sandbox groups run.

SUBSCRIPTION_ID="<subscription-id>"
REGION="<region>"

az rest \
--method get \
--url "https://management.azure.com/subscriptions/${SUBSCRIPTION_ID}/providers/Microsoft.App/locations/${REGION}/usages?api-version=2024-03-01"

API rate limits aren't shown in Azure quota management.

Reserved network address ranges​

The following IPv4 ranges are reserved for sandbox internal networking. You cannot use addresses in these ranges for private resources that sandboxes or disk image builds need to reach through a VNET connection.

Reserved rangeAddress range
192.168.0.0/24192.168.0.0 to 192.168.0.255
100.65.0.0/23100.65.0.0 to 100.65.1.255

This restriction includes private endpoints, private container registries, custom DNS servers, and resources reached through VNet peering or on-premises connectivity. A VNET connection can provision successfully while requests to these addresses fail.

Assign the resources a non-overlapping address and update their DNS records as needed. An egress allow rule does not remove this restriction. See VNet networking for guidance.

When to request quota​

Request more quota before your planned concurrent usage reaches your current core allocation. Reaching the concurrent cores quota will prevent you from creating new sandboxes or starting existing ones.

Request a higher API rate limit if your expected request volume regularly approaches the limit. Requests that exceed the limit can receive an HTTP 429 Too Many Requests response.

Quota increases can require review. Submit a support request before a planned increase in usage, and select Service and subscription limits (quotas) as the issue type.