Could sharepoint server verify azure blob by StorageCrc64HashAlgorithm to replace the MD5

[EmiyaKiritsuguZz]

What type of issue is this?

Question

What SharePoint development model, framework, SDK or API is this about?

SharePoint CSOM

Target SharePoint environment

SharePoint Online

What browser(s) / client(s) have you tested

• 💥 Internet Explorer
• 💥 Microsoft Edge
• 💥 Google Chrome
• 💥 FireFox
• 💥 Safari
• mobile (iOS/iPadOS)
• mobile (Android)
• not applicable
• other (enter in the "Additional environment details" area below)

Additional environment details

• browser version
• SPFx version
• Node.js version
• etc

Issue description

I am using the public SProvisionedMigrationContainersInfo ProvisionMigrationContainers() to get the Azure storage for the Sharepoint site collection.
When I upload files to Azure storage, I need to set the MD5 hash of the content to ContentHash in order to generate blob files, but the production environment needs to be FIPS enabled.
Can we support replacing the hash with StorageCrc64HashAlgorithm?

[Ashlesha-MSFT]

Hello @EmiyaKiritsuguZz,
Thank you for bringing this issue to our attention. We will look into it and get back to you shortly.

[Amey-MSFT]

Hello @EmiyaKiritsuguZz ,
If you're using the Azure SDK, check whether the ProvisionMigrationContainers() method allows specifying a hashing algorithm other than MD5. The Azure Storage Blob API typically supports various hash algorithms depending on the scenario. Refer to the official Azure documentation or SDK to confirm if StorageCrc64HashAlgorithm or other FIPS-compliant algorithms like SHA-256 are supported for your use case.

You can access the Azure SDK documentation via the following link:
https://learn.microsoft.com/en-us/azure/developer/

For information specifically related to Azure Storage, you can check:
https://learn.microsoft.com/en-us/azure/storage/blobs/

Let me know if this approach works or further help is required on the same.
Thanks!!

[EmiyaKiritsuguZz]

Thanks for your comment

Yes, I can upload the files to the Azure Storage of the SharePoint Online site collection via StorageCrc64HashAlgorithm.
However, when I get message from the service bus queue (from public ClientResult<ProvisionedMigrationQueueInfo> ProvisionMigrationQueue() Microsoft.SharePoint.Client), I would get the error message.

{"Event":"JobError","JobId":"cbcf1ca3-de3c-4fcf-9bb2-9328611e083b","Time":"03/12/2025 00:37:26.674","TotalRetryCount":"0","MigrationType":"None","MigrationDirection":"Import","Message":"Unable to download ExportSettings.xml with exception \u0027Missing MD5 property in Manifest and Azure Blob.\u0027","CorrelationId":"5c9f89a1-d022-0000-8a7c-7e2eccd90212"}

{"Event":"JobFatalError","JobId":"cbcf1ca3-de3c-4fcf-9bb2-9328611e083b","Time":"03/12/2025 00:37:26.704","TotalRetryCount":"0","MigrationType":"None","MigrationDirection":"Import","ErrorCode":"-2147213157","ErrorType":"Microsoft.SharePoint.SPException","Message":"Missing Export Settings file stream: ExportSettings.xml CallStack -- at Microsoft.SharePoint.Deployment.SPImport.DeserializeExportSettings()\r\n at Microsoft.SharePoint.Deployment.SPImport.Run()","CorrelationId":"5c9f89a1-d022-0000-8a7c-7e2eccd90212"}

[Amey-MSFT]

Hello @EmiyaKiritsuguZz ,
It appears that the migration process is expecting the MD5 hash to be present in the blob manifest for the ExportSettings.xml file, but since you're using StorageCrc64HashAlgorithm in place of MD5 for FIPS compliance, it's not being recognized.
Ensure that the blob manifest is updated to include the correct hash value (MD5 or StorageCrc64). If the migration tool expects MD5 but you're using StorageCrc64HashAlgorithm, the manifest might not be compatible with the service expecting MD5.

Additional Resources:

https://learn.microsoft.com/en-us/rest/api/storageservices/setting-and-retrieving-properties-and-metadata-for-blob-resources

https://powers-hell.com/2021/12/31/calculate-validate-md5-hashes-on-azure-blob-storage-files-with-powershell/

Let me know if this approach works or further help is required on the same.
Thanks!!