Azure Container Apps: Environments, Revisions, KEDA Scaling, and Managed Ingress
A production-focused guide to Azure Container Apps architecture, revisions, jobs, networking, identity, observability, scaling, and platform limits.
Azure Container Apps is a serverless platform for containerized applications and jobs. It exposes selected Kubernetes-era capabilities—revisions, event-driven scaling, service discovery, ingress, and optional Dapr integration—without giving customers a general Kubernetes API to operate.
Environments, apps, and revisions
Container apps live inside an environment that establishes a networking and observability boundary. A template change creates a revision. Single-revision mode replaces the active revision; multiple-revision mode enables traffic splitting and side-by-side validation. Jobs are separate resources for manual, scheduled, or event-driven work that terminates.
Scaling with KEDA
HTTP demand, CPU or memory, and supported KEDA-based triggers can change replica count. Many workloads can scale to zero, but CPU- or memory-only rules cannot do so because no running replica remains to produce those metrics. Define minimum and maximum replicas deliberately, then protect queues and databases against a sudden burst of parallel consumers.
Security and networking
Managed identities avoid embedding Azure credentials. Secrets can be stored by the platform or referenced through supported integrations; application logs must never print them. Ingress may be external or internal, and environments can integrate with a virtual network. Confirm subnet sizing, DNS, private endpoints, and egress requirements before treating an environment as a drop-in replacement for AKS networking.
Operations and cost
Azure Monitor and Log Analytics provide platform logs and metrics; application-level tracing still requires instrumentation. Revisions simplify rollback, but schema migrations and message consumers must remain compatible during overlap. Consumption and dedicated workload profiles have different cost and isolation characteristics. Container Apps fits teams wanting managed HTTP, event, and job execution; AKS remains appropriate when the Kubernetes API, custom controllers, privileged workloads, or deeper node control are requirements.
Sources: Azure Container Apps overview, Azure Container Apps architecture guidance