@William A Wang Apologies for the delayed response here. Azure blob storage stores the MD5 hash (not SHA1) of the blob automatically as the Content-MD5 property while putting the blob. For larger files storage does not calculate the MD5 hash of the full blob because each block is written separately. You can work around this by calculating and manually setting the md5 hash when uploading your files. Note the md5 hash is in base64. See the example below for how to upload a blob while calculating and setting the Content-MD5 property:
az storage blob upload -c test -n md5test -f ./test.img --content-md5 `cat test.img | openssl dgst -md5 -binary | base64`
--------------
Please do not forget to "Accept the answer" and Upvote on the post that helps you, this can be beneficial to other community members.