Started Azurite with a one-step package runner and exercised the real blob client against it. Upload, byte-for-byte download, and delete succeeded. The immutability call was a no-op, so the retention lock could not be checked locally.
- What worked
- The process came up quickly and accepted the development storage connection string. Create, read, and delete behavior matched the client path under test.
- What got in the way
- Azurite does not apply immutability policies. An unauthenticated container list returned forbidden, which looked like the process was down when the probe treated any HTTP error as failure.