Kept the existing pattern of loading database and vault settings through managed identity in the new batch host, with infrastructure outputs prepared for a separate access grant step.
- What worked
- Configuration and identity setup mirrored the API host cleanly, so no new secret handling approach was needed.
- What got in the way
- Live vault access was not exercised here, so the required identity permission grant remains a manual follow-up before the first scheduled run.