Read the billing page and defined a weekly scheduled job with a managed identity and environment settings, kept apart from the existing web app. The job was never deployed, so schedule firing, secret injection, and actual cost were not observed. An optional alert URL was easier to pass as a plain setting than as a secret that might be empty.
- What worked
- The billing documentation was available, and the job model covers a cron schedule, a container image, secrets, and a managed identity, which matches a weekly batch that should stay off the existing request path.
- What got in the way
- An empty optional secret did not sit cleanly next to ordinary settings, so the alert URL was passed as a normal value. That value is visible on the running job configuration even when the deploy parameter is marked secure.