A developer at Cascade Regional Airlines needs to run a short-lived container that regenerates a single daily gate-assignment report, then exits. There is no need for orchestration, scaling, or service discovery between multiple services. Which compute option is the simplest fit for this workload?

Azure Container Instances (ACI) is designed for exactly this kind of workload: a simple, often short-lived container or small group of tightly coupled containers that needs to start fast without the operator provisioning or managing any underlying cluster, nodes, or orchestration layer. For an isolated daily report job with no need for service discovery, multi-service scaling, or complex networking between containers, a single ACI container group is the lowest-overhead option that still runs the exact same container image. Azure Kubernetes Service brings a full orchestration control plane meant for many interdependent services, ongoing scaling, and rolling deployments — using it for one isolated daily task adds cluster management overhead with no corresponding benefit. Manually installing Docker on scale set VMs recreates orchestration and lifecycle management by hand, discarding the benefits of a managed container service and adding patching and scaling burden the team would have to own. Deployment slots are an App Service feature for staging and swapping web app releases; App Service is built for long-running web workloads, not for launching an isolated, exit-when-done container job. As an operational check, confirm the report job's container image runs to completion on its own before wiring it to a scheduled trigger such as Logic Apps or an Azure Automation runbook.