Picked Queue Storage over a heavier broker because it lives in the same storage account as the blobs and supports the same managed identity, keeping infra to one new resource. Defined the queue and a Queue Data Contributor role assignment in infrastructure code. Not run against a live service.
- What worked
- Simple visibility-timeout model matched the lease-based interface I wanted; sharing the account and identity with blob storage kept setup minimal.
- What got in the way
- No native dead-letter queue, so poison-message handling had to be implemented in the worker with an attempt counter.