Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
A Container Apps environment is a secure boundary around one or more container apps and jobs. The Container Apps runtime manages each environment by handling OS upgrades, scale operations, failover procedures, and resource balancing.
Environments include the following features:
| Feature | Description |
|---|---|
| Type | There are two different types of Container Apps environments: Workload profiles environments and Consumption only environments. Workload profiles environments support both the Consumption and Dedicated plans whereas Consumption only environments support only the Consumption plan. |
| Virtual network | A virtual network supports each environment, which enforces the environment's secure boundaries. As you create an environment, a virtual network with limited network capabilities is created for you, or you can provide your own. Adding an existing virtual network gives you fine-grained control over your network. |
| Multiple container apps | When multiple container apps are in the same environment, they share the same virtual network and write logs to the same logging destination. |
| Multi-service integration | You can add Azure Functions and Azure Spring Apps to your Azure Container Apps environment. |
Depending on your needs, you might want to use one or more Container Apps environments. Use the following criteria to help you decide if you should use a single or multiple environments.
Single environment
Use a single environment when you want to:
- Manage related services
- Deploy different applications to the same virtual network
- Instrument Dapr applications that communicate via the Dapr service invocation API
- Share the same Dapr configuration among applications
- Share the same log destination among applications
Multiple environments
Use more than one environment when you want two or more applications to:
- Never share the same compute resources
- Not communicate via the Dapr service invocation API
- Be isolated due to team or environment usage (for example, test vs. production)
Types
| Type | Description | Plan | Billing considerations |
|---|---|---|---|
| Workload profile | Run serverless apps with support for scale-to-zero and pay only for resources your apps use with the consumption profile. You can also run apps with customized hardware and increased cost predictability using dedicated workload profiles. | Consumption and Dedicated | You can choose to run apps under either or both plans using separate workload profiles. The Dedicated plan has a fixed cost for the entire environment regardless of how many workload profiles you're using. |
| Consumption only | Run serverless apps with support for scale-to-zero and pay only for resources your apps use. | Consumption only | Billed only for individual container apps and their resource usage. There's no cost associated with the Container Apps environment. |
Logs
Logging is an essential part of monitoring and troubleshooting container apps running in your environment. Azure Container Apps environments provide centralized logging capabilities through integration with Azure Monitor and Application Insights.
By default, all container apps within an environment send logs to a common Log Analytics workspace, making it easier to query and analyze logs across multiple apps. These logs include:
- Container
stdout/stderrstreams - Container app scaling events
- Dapr sidecar logs (if Dapr is enabled)
- System-level metrics and events
Log configuration properties
You can configure the following properties at the environment level through the API:
| Property | Description |
|---|---|
properties.appLogsConfiguration |
Used for configuring the Log Analytics workspace where logs for all apps in the environment are published. |
properties.containerAppsConfiguration.daprAIInstrumentationKey |
App Insights instrumentation key provided to Dapr for tracing |
Policies
Azure Container Apps environments are automatically deleted if one of the following conditions is detected for longer than 90 days:
- In an idle state (no active container apps or jobs running in the environment)
- In a failed state due to VNet or Azure Policy configuration
- Is blocking infrastructure updates due to VNet or Azure Policy configuration
These policies help ensure efficient resource use and maintain service quality. To prevent automatic deletion:
- Keep at least one active container app or job running in your environment
- Ensure your VNet and Azure Policy configurations are correctly set up
- Respond to any notifications about your environment being in a problematic state
You can monitor the status of your environments through Azure Monitor alerts or by regularly checking the environment status in the Azure portal or via Azure CLI.
Limits and quotas
Understanding the limits and quotas for Container Apps environments helps you plan your application architecture effectively.
| Resource | Limit | Notes |
|---|---|---|
| Container apps per environment | 200 | Maximum number of container apps in a single environment |
| Container app revisions per environment | 1000 | Total revisions across all apps in an environment |
| Environments per region per subscription | 20 | Can be increased via support request |
| Maximum CPU per container | 4 vCPU (Consumption), Varies by workload profile | Depends on the environment type and selected workload profile |
| Maximum memory per container | 16 GB (Consumption), Varies by workload profile | Depends on the environment type and selected workload profile |
| Maximum replicas per container app | 300 | Maximum scale-out limit for a single container app |
| Maximum ingress request timeout | 240 seconds | For HTTP requests through ingress |
For the most up-to-date limits and quotas, refer to the Azure Container Apps service limits.