Selected Blob Storage from the docs as the managed store for issued bill PDFs: cool tier, anonymous access and shared keys off, Entra-only auth, and a locked immutability policy for multi-year retention. Role write-ups were easy to misread, and the account was never deployed or called.
- What worked
- The service model covered private containers, managed identity, cool storage, and a blob immutability lock through a calculated expiry. A published built-in role id was available to pin in infrastructure. Leaving public network access on with Entra auth matched a Basic plan that cannot use virtual-network integration.
- What got in the way
- Storage Blob Data Contributor can write blobs and cannot set an immutability policy. The data owner role is required because it includes the super-user data action. No subscription was available, so account creation, identity assignment, and locked policies stayed unverified.
