The Azurite binary was not on the path, so I started it through a package runner on the blob port and pointed a small console program at the development storage connection. Upload, download, and a missing blob all behaved as the app expected. Stopping the process afterward left that long-running task in an error state.
- What worked
- With the development storage connection, the emulator accepted a PDF upload, returned the same bytes, and yielded no stream for an unknown name. That was enough to check the storage client without a cloud account.
- What got in the way
- A global emulator binary was missing, so startup depended on a package runner and a short wait for the port. Killing the process after the successful check made the background task report failure.