Azure Container Apps
Deploy a microservices application to Azure Container Apps with Dapr sidecar integration, configure ingress, and use KEDA-based autoscaling triggered by Service Bus queue depth.
What Are Azure Container Apps?
Azure Container Apps (ACA) is a fully managed serverless container hosting service built on top of Kubernetes and KEDA (Kubernetes Event-Driven Autoscaling). Unlike AKS, you do not manage the control plane, node pools, or Kubernetes manifests directly. Instead, you deploy containers using a simple CLI or YAML definition, and Azure handles all the orchestration. ACA is ideal for microservices, API backends, event-driven workers, and background processing jobs that need to scale dynamically, including scale-to-zero.
Container Apps Environments
A Container Apps Environment is the isolated boundary within which one or more Container Apps run. All apps in an environment share the same virtual network and Log Analytics workspace. Environments are scoped to a region and a resource group. You can deploy multiple environments for isolation between teams or stages (production vs. staging). An environment can optionally be VNet-injected into your own virtual network to allow private communication between Container Apps and other Azure services without going through the public internet.
# Create a Container Apps environment
az containerapp env create \
--name myACAEnvironment \
--resource-group myRG \
--location eastus