There's no MS solution to this. MD5 calculations on FTP servers has been around for 35 years - not sure why MS decided its not necessary. This is so unproductive. The server needs to calculate the MD5 hash independently of the client. Calculating the MD5 on the client and then populating the MD5 on the server file doesn't help anyone. If a bit or byte gets incorrectly copied - the MD5 will always match the client, and you don't know the file is corrupted until you try to use it. Why not allow us to ensure the file is uploaded correctly?
I've been spending months explaining all of this to Microsoft support and they don't get it. I don't understand, why not add two lines of code and an additional nanosecond of CPU power to calculate all MD5's on all BLOB files in the filesystem? (Oh wait the OS already does this automatically) why not copy it to the properties?