Microsoft Azure Learning Journey

Run Containers Without Managing Kubernetes: Azure Container Apps

Deploy containerized APIs, workers, and jobs while Azure manages the orchestration platform.

5 min read · 981 words
Microsoft AzureAzure ComputeContainersCloud ArchitectureDevOps
Run Containers Without Managing Kubernetes: Azure Container Apps cover image

Your team packages an API in a container, then discovers that a container image is not a hosting platform. You still need ingress, scaling, image pulls, revisions, secrets, and observability. Azure Container Apps supplies those platform capabilities without requiring you to operate a Kubernetes cluster.

What you’ll learn

Where this fits

Module 16 and Phase 4, Part 3. Next: Do You Need AKS?.

Prerequisites

A managed application platform for containers

An environment provides a shared boundary for Container Apps and related networking, logging, and service discovery. A container app runs one or more containers and defines ingress, identity, scaling, and configuration. A revision is an immutable snapshot of an app’s revision-scoped configuration and template. A job runs a finite workload on demand, on a schedule, or in response to events.

Client -> ingress -> Container App revision(s)
                          | managed identity -> Azure services / ACR
                          | scale rules -> replicas (possibly zero)
                          + logs and metrics -> monitoring

Container Apps supports HTTP or TCP ingress, internal service discovery, multiple revisions, traffic splitting, jobs, and event-driven scaling through supported scalers. It can reduce platform work, but you still own the container image, application health, data, identity permissions, and deployment design.

Images and Azure Container Registry

ACR stores private container images. Build from a trusted base, pin versions or digests, scan dependencies, and avoid embedding credentials in layers. Container Apps can use a managed identity to authenticate pulls. Assign only the required image-pull role at the registry or repository scope supported by its authorization mode. Do not enable the registry admin user as a shortcut.

Revisions, traffic, and scaling

In single-revision mode, the platform moves traffic to a new revision after it becomes ready. In multiple-revision mode, you can divide traffic for canary or blue/green deployments and shift it back if validation fails. A revision is immutable; configuration changes may create a new revision.

Scaling can use HTTP concurrency, CPU/memory, or event sources. Many consumption applications can scale to zero, but zero replicas introduces startup latency and is not appropriate for every workload. Set minimum and maximum replica counts intentionally; scale-out can increase cost and downstream load.

When to choose something else

Hands-on: inspect existing apps

RESOURCE_GROUP="<EXISTING_RESOURCE_GROUP>"
az containerapp list --resource-group "$RESOURCE_GROUP" \
  --query "[].{name:name, location:location, environment:managedEnvironmentId}" \
  --output table

This is a read operation. Use only a resource group you are authorized to inspect.

✅ Checkpoint: Identify the app and environment. The list does not prove that the revision is healthy, its ingress is safe, or its identity has minimal permissions.

Security, cost, and production

Use managed identity for Azure access and ACR pulls. Store application secrets in an approved secret store and restrict environment ingress. An environment’s networking mode and region are architectural choices that may be difficult or costly to change later.

Consumption, dedicated workload profiles, logging ingestion, registry storage, networking, and outbound transfer have different cost models. Verify current plan behavior, supported scale-to-zero features, regional availability, and pricing. Production designs need revision rollback, health endpoints, resource limits, diagnostic logs, and tested identity permissions.

Troubleshooting

Five-pillar readiness checklist

Cleanup

No Azure resources were created. No cleanup is needed.

Key takeaways

Next: Do You Need AKS? Kubernetes on Azure Explained.

Series navigation: Previous: VM Scale Sets · Current: Phase 4, Part 3 · Next: AKS

References

Share this article

LinkedIn post draft