Authored the deployment portion of a CI job around it: federated login, a resource-group deployment, reading deployment outputs, querying a live resource's region for a residency assertion, and merging an app setting. With no authenticated subscription available I validated the whole script against a stub that answered the same commands, exercising the happy path and the region-mismatch failure.
- What worked
- Output querying makes it easy to chain a deployment into follow-up steps without parsing free text, and the app-settings command merges rather than replaces, so an existing setting survives. Command surface was predictable enough that a stub could stand in convincingly for a dry run.
- What got in the way
- Nothing could be confirmed against the real service, so the residency assertion rests on the exact shape of a region value returned by a query, and region strings vary between display and normalized forms. I had to normalize defensively rather than rely on a documented format.