What it does
Azure Container Instances provides on-demand container compute for workloads that do not need a full Kubernetes control plane. It can run Linux or Windows containers, including confidential and Spot options, as container instances or groups. Teams can deploy from the Azure portal, CLI, PowerShell, or infrastructure templates, and can use virtual nodes to burst from Azure Kubernetes Service. Billing is per second for the selected compute, making the service suited to short-lived jobs, event-driven processing, or additional capacity for a cluster.
Start with a container image and a small deployment definition
Azure Container Instances is designed for running containers directly, without first creating virtual machines or adopting a higher-level container service. The official documentation offers quickstarts for the CLI, portal, PowerShell, Bicep, ARM templates, and Terraform. A developer can provide a container image and the resources it needs, then launch a container instance. The service supports Linux and Windows containers, with regular, confidential, and Spot options documented in the overview.
That direct model is useful for a one-off data conversion, a job kicked off by an event, or a small service that needs isolated compute but not a cluster scheduler. For Kubernetes teams, Azure documents virtual nodes that let AKS place additional pods on Container Instances when traffic spikes. This makes ACI a burst-capacity option rather than a replacement for AKS's full orchestration and control-plane features.
The pricing page describes per-second billing with no upfront cost or termination fee, and lets customers adjust CPU and memory sizes. Actual charges depend on the region and configuration, so use the Azure calculator for a workload estimate. You still supply and maintain the container image and its application behavior; ACI takes away the virtual-machine management, not the need to build a deployable container. No container was launched for this listing.
Strengths
- Runs Linux or Windows containers without requiring users to provision virtual machines or adopt a full orchestration service.
- The documentation provides deployment paths for CLI, portal, PowerShell, Bicep, ARM templates, and Terraform.
- Virtual-node integration lets AKS use ACI capacity for burst workloads, and pricing is billed per second.
Watch out for
- ACI supplies direct container compute rather than a complete Kubernetes scheduler; orchestrated workloads may still need AKS.
- Customers must provide a suitable container image and select resource sizes; the final bill depends on region and configuration.
Best for
- Short-lived jobs or event-driven tasks that need container isolation without a VM fleet.
- Development teams deploying a small containerized workload through a CLI or infrastructure template.
- AKS users who need extra capacity for traffic bursts through virtual nodes.
Sources
- Azure Container Instances | Microsoft Azure (Oct 25, 2026)
- Serverless containers in Azure - Azure Container Instances | Microsoft Learn (Oct 25, 2026)
- Pricing - Container Instances | Microsoft Azure (Oct 25, 2026)