Generate container group configuration with resource limits, volumes, and networking.
Last verified: May 2026
Generate container group configuration with resource limits, volumes, and networking.
Required Fields
containerGroupNameosTypeipAddressipAddress.typecontainersOutput will appear here...The generator constructs an ACI container group definition with container properties (image, resources, environment variables, ports, volume mounts, command override), networking (public IP, VNet integration), and group-level settings (restart policy, OS type, image registry credentials). Output is generated as az container create commands, ARM template JSON, and Bicep resources.
The Azure Container Instance Config Generator helps you build container group configurations for Azure Container Instances (ACI). ACI provides serverless container execution without managing VMs or orchestrators. This tool guides you through configuring container images, CPU and memory allocation, networking, environment variables, volume mounts, and restart policies, generating the deployment JSON or YAML for use with the Azure CLI, ARM templates, or Bicep.
Your team needs to run a nightly database migration check that takes ~5 minutes. Currently it runs on a 24/7 small VM costing $30/month. The generator helps you build an ACI config: 1 vCPU, 1.5 GB memory, container running the check, restartPolicy=Never, triggered by Logic Apps on a schedule. New cost: 5 min × 30 days × ($0.000034/sec × 1 vCPU + $0.000004/sec × 1.5 GB) = ~$0.50/month. 60x cost reduction with no operational tradeoffs.
ACI billing rounds up to the nearest second per container instance, with NO minimum charge. This is fundamentally cheaper than ACI alternatives like AKS for short-running tasks. A 30-second container literally costs cents on ACI vs. paying for an idle AKS node pool.
ACI doesn't auto-restart containers that fail (unlike AKS or App Service). For job patterns this is fine. For services, use restartPolicy: 'OnFailure' — but recognize ACI is the wrong tool for long-running services. Use AKS or Container Apps for those.
ACI's VNet integration option costs significantly more (roughly 2x) than public-IP ACI. Only use VNet integration when you actually need to access private resources. For containers that just need to call public APIs, the public-IP ACI is fine and far cheaper.
Use ACI for simple, short-lived, or burst workloads that do not need orchestration features. ACI is ideal for batch processing, CI/CD build agents, scheduled tasks, and event-driven containers. For long-running, complex microservices architectures, AKS provides better orchestration. For web applications, App Service may be simpler.
Yes. ACI supports pulling images from Azure Container Registry (ACR), Docker Hub, and other private registries. For ACR, you can use managed identity authentication. For other registries, provide the registry credentials in the container group configuration.
Was this tool helpful?
Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.