Edtis3

Author: lootle1

articles/container-apps/sessions.md

@@ -5,7 +5,7 @@ services: container-apps
 author: craigshoemaker
 ms.service: azure-container-apps
 ms.topic: concept-article
-ms.date: 04/07/2025
+ms.date: 04/01/2026
 ms.author: cshoe
 ms.custom: references_regions, ignite-2024
 ---
@@ -14,29 +14,30 @@ ms.custom: references_regions, ignite-2024
 
 Azure Container Apps dynamic sessions provide fast access to secure sandboxed environments that are ideal for running code or applications that require strong isolation from other workloads.
 
-Dynamic sessions offer prewarmed environments through a [session pools](./session-pool.md) that starts the container in milliseconds, scales on demand, and maintains strong isolation. This makes them ideal for interactive workloads, running LLM generated scripts, and secure execution of custom code.
-
+Dynamic sessions offer prewarmed environments through [session pools](./session-pool.md) that start the container in milliseconds, scale on demand, and maintain strong isolation. This makes them ideal for interactive workloads, running LLM generated scripts, and secure execution of custom code.
 
 ## Benefits
+
 With sessions, you get:
 
 - **Secure isolation**: Hyper-V isolation and optional network controls protect your environment. Sessions are isolated from each other and from the host environment, providing enterprise-grade security and isolation.  
 - **Sandboxed environments**: Each session runs in its own isolated environment, ensuring that workloads don't interfere with each other.
 - **Instant Startup**: Prewarmed pools enable subsecond launch times for interactive workloads. New sessions are allocated in milliseconds thanks to pools of ready but unallocated sessions.  
-- **Scalable by Design**: Handle hundreds or thousands of concurrent sessions without manual intervention. 
-- **Managed lifecycle**: Sessions are automatically deprovisioned after use or after a configurable cooldown period, ensuring efficient resource usage. 
-
+- **Scalable by Design**: Handle hundreds or thousands of concurrent sessions without manual intervention.
+- **Managed lifecycle**: Sessions are automatically deprovisioned after use or after a configurable cooldown period, ensuring efficient resource usage.
 
 ## Common Scenarios
+
 Dynamic sessions are useful in a variety of situations, including:
+
 - **AI/LLM Workflows**: Safely execute AI-generated code in isolated environments without risking your production systems.
 - **Interactive Development**: Provide developers with fast, disposable environments for testing scripts or prototypes without provisioning full apps.
 - **Secure Code Execution**: Run untrusted or user-submitted code in a sandboxed environment with strong isolation.
 - **Custom Compute Tasks**: Execute short-lived jobs that require custom dependencies or runtime environments without long startup times.
 - **Burst Workloads**: Handle unpredictable spikes in demand by scaling sessions up and down automatically.
 
-
 ## Key Concepts
+
 - **Session Pool**: A session pool is the foundation for dynamic sessions. It contains a set of prewarmed, ready-to-use sessions that enable near instant startup. When a request comes in, the system allocates a session from the pool instead of creating one from scratch, which dramatically reduces latency.  
 
 - **Session**: A session is the actual execution environment where your code or container runs. Sessions are ephemeral and isolated, designed for short-lived tasks. When you create a session, it's allocated from the session pool, ensuring fast startup. After the task completes or the cooldown period expires, the session is destroyed and resources are cleaned up.  
@@ -49,8 +50,7 @@ Dynamic sessions are useful in a variety of situations, including:
   - **Code interpreter session pools**: These use platform built-in containers that provide preconfigured environments for running code, including AI-generated scripts. Ideal for scenarios like LLM-driven workflows or secure code execution.
   - **Custom container session pools**: Bring-your-own-container for custom workloads that require specific dependencies or runtime environments.
 
-
-#### Session pool types comparison
+### Session pool types comparison
 
 | | **Code interpreter session pool** | **Custom container session pool** |
 |---------------|------------------------------|------------------------------|
@@ -59,11 +59,10 @@ Dynamic sessions are useful in a variety of situations, including:
 | **When to choose** | Choose this for simplicity, fastest startup, and minimal setup. | Choose this when you need full control over the execution environment or rely on custom dependencies. |
 | **Ideal use cases** | LLM workflows, code interpretation, educational/sandbox scenarios, safe execution of user code. | Custom compute tasks, proprietary interpreters, specialized environments, or workloads with specific OS/library requirements. |
 | **Language and protocol** | Limited to the built-in runtimes and the REST API surface provided by the code interpreter. | Any language or stack supported by your container, with any TCP protocol you choose to expose. |
-| **Image requirement** | None—uses platform built‑in interpreter environments. | Required—supply your own container image URI. |
+| **Image requirement** | None, uses platform built‑in interpreter environments. | Required, supply your own container image URI. |
 
 For more information, see [Usage](./sessions-usage.md).
 
-
 ## Supported regions
 
 Dynamic sessions are available in the following regions. Both code interpreter and custom container sessions are supported in all listed regions.
@@ -89,14 +88,14 @@ Dynamic sessions are available in the following regions. Both code interpreter a
 > Regional availability may change. To verify current availability, check the **Location** dropdown when creating a session pool in the Azure portal.
 
 ## Security
-Dynamic sessions are designed to run untrusted code in isolated environments. For information about securing your sessions, see [Security](./sessions-usage.md#security).
 
+Dynamic sessions are designed to run untrusted code in isolated environments. For information about securing your sessions, see [Security](./sessions-usage.md#security).
 
 ## Billing
-Custom container sessions are billed based on the resources consumed by the session pool. For more information, see [Azure Container Apps billing](./billing.md#dynamic-sessions).
 
+Custom container sessions are billed based on the resources consumed by the session pool. For more information, see [Azure Container Apps billing](./billing.md#dynamic-sessions).
 
 ## Next steps
-- Learn how to configure [session pools](./session-pool.md) 
-- Learn how to use [dynamic sessions](./sessions-usage.md), including security and best practices
 
+- Learn how to configure [session pools](./session-pool.md)
+- Learn how to use [dynamic sessions](./sessions-usage.md), including security and best practices