Merge pull request #297989 from craigshoemaker/aca/freshness/environment

[Container Apps] Update: Environment -> freshness

Author: JamesJBarnett

articles/container-apps/environment.md

@@ -5,7 +5,7 @@ services: container-apps
 author: craigshoemaker
 ms.service: azure-container-apps
 ms.topic:  conceptual
-ms.date: 08/29/2023
+ms.date: 04/10/2025
 ms.author: cshoe
 ms.custom: build-2023
 ---
@@ -19,13 +19,13 @@ Environments include the following features:
 | Feature | Description |
 |---|---|
 | Type | There are [two different types](#types) of Container Apps environments: Workload profiles environments and Consumption only environments. Workload profiles environments support both the Consumption and Dedicated [plans](plans.md) whereas Consumption only environments support only the Consumption [plan](plans.md). |
-| Virtual network | A virtual network supports each environment, which enforces the environment's secure boundaries. As you create an environment, a virtual network that has [limited network capabilities](networking.md) is created for you, or you can provide your own. Adding an [existing virtual network](vnet-custom.md) gives you fine-grained control over your network. |
+| 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](networking.md) is created for you, or you can provide your own. Adding an [existing virtual network](vnet-custom.md) 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](https://aka.ms/functionsonaca) and [Azure Spring Apps](https://aka.ms/asaonaca) to your Azure Container Apps environment. |
 
 :::image type="content" source="media/environments/azure-container-apps-environments.png" alt-text="Azure Container Apps environments.":::
 
-Depending on your needs, you may 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.
+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
 
@@ -34,8 +34,8 @@ 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
-- Have applications share the same Dapr configuration
-- Have applications share the same log destination
+- Share the same Dapr configuration among applications
+- Share the same log destination among applications
 
 ### Multiple environments
 
@@ -54,7 +54,18 @@ Use more than one environment when you want two or more applications to:
 
 ## Logs
 
-Settings relevant to the Azure Container Apps environment API resource.
+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`/`stderr` streams
+- 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 |
 |---|---|
@@ -65,11 +76,35 @@ Settings relevant to the Azure Container Apps environment API resource.
 
 Azure Container Apps environments are automatically deleted if one of the following conditions is detected for longer than 90 days:
 
-- In an idle state
+- 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
-- Blocks infrastructure updates 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](/azure/azure-resource-manager/management/azure-subscription-service-limits#container-apps-limits).
 
-## Next steps
+## Related content
 
-> [!div class="nextstepaction"]
-> [Containers](containers.md)
+- [Containers in Azure Container Apps](containers.md)
+- [Networking in Container Apps](networking.md)