copyFromUrl() fails if blob is encrypted with customer key

Mircea Cristea 21 Reputation points

I am getting the next error when I try to use copyFromUrl() method on a blob that was deposited using encryption key provided by us:
Status code 409, \"<?xml version=\"1.0\" encoding=\"utf-8\"?><Error><Code>CannotVerifyCopySource</Code><Message>The blob is encrypted with customer specified encryption, but it was not provided in the request.

I want to mention that we had to generate a SAS token before we activated encryption as the method failed with:
Status code 409, \"<?xml version=\"1.0\" encoding=\"utf-8\"?><Error><Code>CannotVerifyCopySource</Code><Message>Public access is not permitted on this storage account.

Using the same keys used in copyFromUrl() method but simulating copy action by retrieving and then depositing the message works just fine, so there are no problem with the provided keys (as the error message erroneously suggests).

The Azure account is using shared key for authentication and library used is Azure Java SDK 12.8.0.

Any help is much appreciated!

Azure Blob Storage
Azure Blob Storage
An Azure service that stores unstructured data in the cloud as blobs.
2,415 questions
0 comments No comments
{count} votes

Accepted answer
  1. deherman-MSFT 33,141 Reputation points Microsoft Employee

    @Mircea Cristea
    Since you are able to perform this action outside of copyFromUrl() it sounds like this could be a bug. For the quickest response and fix from the developer team, I recommend creating an issue on the azure-sdk-for-java GitHub issues page.

    Please let me know if you are unable to create an issue or get a response and I will work internally to escalate the issue.


    Please don’t forget to "Accept the answer" and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Mircea Cristea 21 Reputation points

    Thank you @deherman-MSFT ,

    I have raised a bug to the development team.

    0 comments No comments