Brendan
Brendan
It doesn't work regardless of the auth method I've tried. What permissions do you want me to try, obviously I can't just guess at them. And yes it's being thrown...
Can you point me to the code that demonstrates copying from a BlockBlob to a FileShare?  Stack: ``` at Azure.Core.HttpPipelineExtensions.ProcessMessageAsync(HttpPipeline pipeline, HttpMessage message, RequestContext requestContext, CancellationToken cancellationToken) at Azure.Storage.Blobs.BlobRestClient.GetPropertiesAsync(String...
It does **not** throw an error and all the properties are returned as expected. ``` var props = await blockBlobClient.GetPropertiesAsync(); Console.WriteLine($"Blob URI: {blockBlobClient.Uri}"); Console.WriteLine($"Blob size: {props.Value.ContentLength}"); Blob URI: https://......blob.core.windows.net/....eve2/1.jpg Blob...
So passing the clients directly to the providers results in the same error, GetProperties on the source works, a file is created in the share but fails on copying the...
I also wanted to note that this managedIdentity is used throughout the existing application to w/out issue to manipulate all the file in both the share and blob containers using...
Very frustrating because I can get the source blob properties, the transfer begins and the file is created in the fileshare showing the correct size but then the implementation fails...
I'm seeing the same with the .Net SDK and don't really understand the intent of priorities as it seems required and necessarily unique which is odd.
This issue seems like a UNIX EOF setting in the scripts which I would assume only impacts Windows users.