An EU-pinned, Service Bus-triggered Container Apps Job was defined with managed identity, secrets, scaling, and a two-phase activation flow. The template compiled, but it was not deployed to Azure.
- What worked
- The job model fit a low-volume asynchronous workload and allowed activation to be separated from dependency provisioning and image publication.
- What got in the way
- Avoiding startup before the first image existed required redesigning deployment into two phases, and live cloud behavior remained untested.