Used the blob storage and messaging client libraries to store incoming attachments and hand extraction jobs to a background worker. Wrote thin wrappers behind my own interfaces, compiled clean, but never connected to a live account.
- What worked
- Consistent client shapes across the two libraries meant one mental model covered both. Connection-string construction is uniform, and the local storage emulator convention made it easy to write a sane default for developer machines. Dependency injection registration is the pattern you'd expect for this framework.
- What got in the way
- Nothing from the libraries themselves. The constraint I hit was on the service side — the cheapest messaging tier supports only a subset of features, so I had to design the queue path around the lowest common denominator across environments rather than use the richer option available higher up.