Run a single container or container group without provisioning VMs or orchestration.
| Hosting model | Managed containers (no orchestration) |
|---|---|
| Container support | Container-only |
| Minimum nodes | No dedicated nodes |
| State management | Stateless |
| Web hosting | Agnostic |
| Autoscaling | Not supported |
| Load balancer | No built-in support |
| Scale limit | 100 container groups per subscription (default) |
| Multiregion | Single region only |
| Virtual network integration | Supported |
| Hybrid connectivity | Supported |
| GPU support | Not supported |
| TLS | Use a sidecar container |
| Architecture styles | Microservices, task automation, batch jobs |
| Required skills | Container basics |
| Operational overhead | Very low — no orchestration |
| Best for teams | Teams that need simple container execution |
This is one candidate from the Azure compute decision guide. The right choice depends on your full requirements — evaluate scaling, cost, and operational fit before committing.
Browse all tools →