Skip to content

Concepts

This section explains Azure Container Apps platform behavior in a language-agnostic way. Use these documents to understand architecture, scaling, and networking before diving into implementation.

Main Content

Documents

Document Description
Architecture: Resource Relationships Control plane vs data plane, environment and app resource hierarchy
Environments Regional boundary for apps, consumption vs workload profiles
Revisions Immutable snapshots, single vs multi-revision mode, traffic splitting
Scaling KEDA autoscaling, HTTP/event/custom scale rules, replica management
Networking Ingress, VNet integration, private endpoints, service discovery
Jobs Scheduled, event-driven, and manual job execution
Identity and Secrets Managed identity setup and RBAC patterns (see also Key Vault, Easy Auth, Security Operations pages)
Reliability Health probes, graceful shutdown, zone redundancy, recovery 
graph LR
    A[Architecture] --> B[Environments]
    B --> C[Revisions]
    C --> D[Scaling]
    D --> E[Networking]
    E --> F[Identity and Secrets]
    F --> G[Reliability]
    C --> H[Jobs]
  1. Start with architecture and resource relationships
  2. Understand environment boundaries and profile choices
  3. Learn revision lifecycle and traffic splitting
  4. Design scaling envelope with KEDA rules
  5. Finalize networking controls and ingress
  6. Validate identity, secrets, and reliability patterns

Read by decision sequence

If you are designing a new workload, treat this section as a dependency chain: architecture and environments first, then revisions/scaling, and finally networking plus identity controls.

Do not skip platform concepts

Jumping directly to language guides without understanding revision mode, ingress boundaries, and scaling behavior often leads to production misconfigurations.

Advanced Topics

  • Build architecture decision records (ADRs) per environment
  • Standardize profile and scaling baselines by workload class
  • Define SLO-driven scaling and networking review checkpoints

Platform docs are language-agnostic

Implementation snippets in language guides should follow the architectural boundaries defined here, not the other way around.

Language-Specific Details

For language-specific implementation details, see: - Python Guide

See Also

Sources