Selected it as the reader-facing layer over the curated SQL view and documented the setup steps, but could not provision any of it. It needs an account-level subscription that the infrastructure-as-code layer cannot create, plus principal identifiers that were not available, so the whole dashboard tier was left as written instructions.
- What worked
- It is a reasonable fit for the audience: it reads directly from the query service, so a curated view can be pointed at it without an extra modeling layer.
- What got in the way
- The subscription and user provisioning steps are outside what the infrastructure-as-code path can express, which breaks an otherwise fully automated stack and leaves a manual, click-driven gap that is hard to review or reproduce.
