Open david-may-shift opened 6 months ago
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @xgithubtriage.
@jsquire Is there any update for this bug triage? Waiting for this bug fix.
@CallMeCJ: My involvement was only to triage to the owners of the package. I have no insight into the current state. We would need updates from the Storage team.
//cc: @amnguye, @seanmcc-msft
The encryption scope request header is not supported on the Copy Blob Service Side Sync REST API call. See https://learn.microsoft.com/en-us/rest/api/storageservices/copy-blob?tabs=microsoft-entra-id#request-headers
If you want to copy a blob with an encryption scope, use BlobBaseClient.SyncCopyFromUri or BlockBlobClient.SyncUplaodFromUri, where the header is supported.
Library name and version
Azure.Storage.Blobs 12.19.1
Describe the bug
We have 2 storage accounts and use BlobClient.StartCopyFromUriAsync within an AzureFunction to copy a blob from one to the other. We instantiate the blobClient and apply an encryption scope using WithEncryptionScope call
However, when the copy completes, the destination blob does not have the encryption scope applied.###
Expected behavior
The destination blob should have the encryption scope that was configured on the blobClient (using WithEncryptionScope call)
Actual behavior
The destination blob does not have an encryption scope applied
Reproduction Steps
Environment
Azure Function App configured with: OS: Linux ServicePlan: B1 RuntimeVersion: 4.28.4.4 FUNCTIONS_EXTENSION_VERSION: ~4 FUNCTIONS_WORKER_RUNTIME: dotnet-isolated