Error in creating settings in container app

Question

Error in creating settings in container app

Kirill Egorov 0

I keep getting the following error when creating an infra in terraform for container apps

Attempting to set a key/value pair which when combined with all settings would exceed the portal's limit: 10240 bytes
Current: 10128 bytes
Requested: 120 bytes


az containerapp show -n analytics-api -g rg-analytics-staging -o json | wc -c
~6854 bytes

Environment details

Resource type: Azure Container Apps
Deployment method: Terraform (azurerm provider)
Region: East US
Number of affected apps: 3
Reproducible after full resource group recreation: Yes

Mohammad Altaf 190 Reputation points Microsoft External Staff Moderator

2026-07-24T15:04:10.3666667+00:00
Hello @Kirill Egorov

Welcome to Microsoft Q&A, Thank you for your question.

Based on the error message, the deployment is failing because the total size of the Azure Container App configuration has reached the current allowed limit. Azure reports that the existing configuration is using 10,128 bytes, and adding the new setting would exceed the allowed 10,240-byte limit.

The output from:

az containerapp show -n analytics-api -g rg-analytics-staging -o json | wc -c

showing approximately 6,854 bytes represents the size of the JSON returned by the Azure CLI and is not the same value used by Azure when validating Container App configuration settings. The validation limit applies to the combined size of environment variables, secrets, and application configuration settings associated with the Container App.

To resolve the issue, review the Container App configuration and reduce the overall size of environment variables and secrets by:

Removing unused or duplicate settings.

Reducing the size of large configuration values.

Moving large secrets or configuration values to Azure Key Vault and referencing them from the Container App instead of storing the full values directly in the application configuration.

After reducing the total configuration size, redeploy the Terraform configuration and the deployment should complete successfully.

Thank you!
Mohammad Altaf 190 Reputation points Microsoft External Staff Moderator

2026-07-27T09:31:39.57+00:00

Hello,

I wanted to follow up and check whether you had a chance to review the suggested guidance regarding the Container App configuration size limit.

Were you able to identify any large or duplicate environment variables, secrets, or configuration values and test the deployment again after reducing the overall configuration size?

If you are still experiencing the issue, please let us know and we will be happy to continue assisting.

Thank you.

2 answers

Your answer

Mohammad Altaf 190 Reputation points Microsoft External Staff Moderator

2026-07-24T15:04:10.3666667+00:00

Hello @Kirill Egorov

Welcome to Microsoft Q&A, Thank you for your question.

Based on the error message, the deployment is failing because the total size of the Azure Container App configuration has reached the current allowed limit. Azure reports that the existing configuration is using 10,128 bytes, and adding the new setting would exceed the allowed 10,240-byte limit.

The output from:

az containerapp show -n analytics-api -g rg-analytics-staging -o json | wc -c

showing approximately 6,854 bytes represents the size of the JSON returned by the Azure CLI and is not the same value used by Azure when validating Container App configuration settings. The validation limit applies to the combined size of environment variables, secrets, and application configuration settings associated with the Container App.

To resolve the issue, review the Container App configuration and reduce the overall size of environment variables and secrets by:

Removing unused or duplicate settings.

Reducing the size of large configuration values.

Moving large secrets or configuration values to Azure Key Vault and referencing them from the Container App instead of storing the full values directly in the application configuration.

After reducing the total configuration size, redeploy the Terraform configuration and the deployment should complete successfully.

Thank you!
Mohammad Altaf 190 Reputation points Microsoft External Staff Moderator

2026-07-27T09:31:39.57+00:00

Hello,

I wanted to follow up and check whether you had a chance to review the suggested guidance regarding the Container App configuration size limit.

Were you able to identify any large or duplicate environment variables, secrets, or configuration values and test the deployment again after reducing the overall configuration size?

If you are still experiencing the issue, please let us know and we will be happy to continue assisting.

Thank you.

Answer 1

SUNOJ KUMAR YELURU 18,416 MVP Volunteer Moderator

Hello @Kirill Egorov,

Thanks for using Q & A forum.

Instead of storing large payloads directly in Container App settings:

Move secrets to Azure Key Vault
Store configuration files in:
- Azure Blob Storage
- Azure App Configuration
- Cosmos DB / SQL / Storage Tables (depending on use case)
Reference Key Vault secrets rather than embedding large values directly

If this answers your query, do click Accept Answer and Up-Vote for the same. And, if you have any further query do let us know.

Sreetheja Adusumilli 965 Reputation points Microsoft External Staff Moderator

2026-08-03T03:17:59.4733333+00:00

Hello @Kirill Egorov ,

We sincerely apologize to hear that the issue has not yet been resolved. Your satisfaction is important to us, and we are committed to working with you toward a resolution. Please share your email ID, feasible time to connect in Private Message.

Answer 2

The error is deterministic: the generated Container Apps configuration is already 10,128 bytes, and the requested setting takes it beyond the 10,240-byte limit reported by the service. Recreating the resource group will not change that payload size. Inspect the Terraform plan and the final environment-variable and secret arrays for duplicated keys, stale values, or large embedded certificates and JSON documents. Remove unused entries and avoid copying the same value into several variables. Put sensitive values in Key Vault and reference them from Container Apps secrets, or move larger non-secret configuration into an external configuration store or mounted file. Then apply the smallest change to one app and verify the new revision. Microsoft’s public documentation does not describe a quota-increase path for this validation limit, so the safe resolution is to reduce or split the application-level settings rather than retry the deployment unchanged.