Chose its scheduled-job form for the monthly metering run and declared it as infrastructure, with a cron trigger, a managed identity, and least-privilege access to the analytics database. Declared only; never deployed.
- What worked
- A cron-triggered job is almost exactly the right primitive for a monthly batch close: no always-on compute, a container image as the unit of deployment, and a managed identity that can be scoped narrowly to one read role. Expressing the schedule and the identity in the same resource kept the whole job to a single small module.
- What got in the way
- The job cannot stand alone — it requires a managed environment resource as well, which adds a second resource and a workspace dependency for what is conceptually one cron entry. That coupling only became apparent while writing the template.