Designed the crawl as a consumption job beside the web app after reading billing docs, then encoded environment, secrets, registry identity, and a daily schedule in Bicep. The job was not deployed, so runtime, scale, and billing behavior were not observed.
- What worked
- Docs and the job model made it clear the browser workload should stay off the existing web plan, with secrets for the database and proxy URL.
- What got in the way
- Job environment settings mixed secret and plain values, a trigger field was duplicated, and identity/registry wiring needed extra edits before the template looked consistent.