Azure Container Apps
backend_type: azure_container_apps_job. Connection: Azure. Status: production — Azure groups carry live fleets today.
Each execution is a Container Apps Job inside an environment you already have (or provision alongside the group). This is the Azure analogue of Fargate: a managed container job, not a VM.
When to choose it
- Azure-resident CI or agent sessions.
- You already operate a Container Apps environment.
- Compliance boundaries that keep compute in Azure.
Choose Azure VM / Azure VMSS when you need a VM or scale set rather than a job.
Connection
An Azure connection (service principal). The principal must be able to operate jobs in the named resource group and environment.
Required config
| Key | Type | Meaning |
|---|---|---|
subscription_id | string | Azure subscription. |
resource_group | string | Resource group that hosts the Container Apps environment. |
environment_name | string | Container Apps environment name. |
Optional knobs
job_name — defaults to a slug of the group name.
Execution control
Suffixed workflows: runner.execution-{stop,restart,sync,logs-sync}-azure-container-apps. A -generic restart variant exists for non-GitHub launches.
Purposes
CI and agent both run here. Staff agent pools in Azure typically pick this kind with purpose=agent and integration_type=none.