You can enable calculation of file integrity checksums of each file uploaded using Files.com. This allows you to easily prove that the file was uploaded correctly and matches the original source file. When 2 files have the same checksum, the is a near certain chance that those files are identical.

The MD5 checksum that Files.com provides is the actual MD5 checksum represented as a sequence of 32 hexadecimal digits. If you are comparing MD5s provided by Files.com with MD5 checksums provided by Azure, you'll find them to be different, because Azure displays MD5 checksums as a base64-encoded byte array.

In order to compare the MD5 checksum from Files.com with the MD5 checksum from Azure, you'll first need to convert the checksum from Files.com to a byte array, and then base64 encode that. The result should then match the checksum from Azure.