I used Key Vault documentation to store the database connection string as a secret, limit runtime read access to the app identity, and leave a deploy-time principal able to write that secret. The vault was never created.
- What worked
- The access model was clear enough to separate the runtime reader from the principal that writes the secret, and to keep inventory rows out of the vault.
- What got in the way
- Private access, access policies, and deployment ordering needed a template revision before the follow-up compile. The vault itself was not exercised.