Azure.Storage.Blobs connect to Storage account via Private Endpoint (using local IP address)

Question

Azure.Storage.Blobs connect to Storage account via Private Endpoint (using local IP address)

Sergey Gorbushin 1

Hi!
I use Azure.Storage.Blobs, Version=12.8.0.0 in my .net core project. My storage account has a private endpoint with a local IP (e.g. 10.1.1.1). I want to access the blob storage via the local IP to ensure, that my data goes internal only.

When I'm tying to use the IP address in connection string (;EndpointSuffix=core.windows.net -> ;EndpointSuffix=10.1.1.1) to use constructor BlobContainerClient(string connectionString, string blobContainerName), I'm getting an error "No valid combination of account information found."

If I'm trying to user constructor BlobContainerClient(Uri blobContainerUri, StorageSharedKeyCredential credential, BlobClientOptions options = null) with blobContainerUri "http://10.1.1.1/tmp", BlobContainerClient instance makes AccountName = "tmp", and Name = "", because its url pattern is "https://{account_name}.blob.core.windows.net/{container_name}". And I'm getting an error "HTTP Error 400. The request hostname is invalid"

How should I use the BlobContainerClient with a local IP address?

Sergey Gorbushin 1 Reputation point

2021-01-28T12:41:58.6+00:00

And if an error occurs on the server side, a response http code is not 200 and a response body is an error description.
When BlobContainerClient tries to parse the response, it throws an error: ''"' is an unexpected token. Expecting whitespace. Line 1, position 50.'
"

1 answer

Your answer

Sergey Gorbushin 1 Reputation point

2021-01-28T12:41:58.6+00:00

And if an error occurs on the server side, a response http code is not 200 and a response body is an error description.
When BlobContainerClient tries to parse the response, it throws an error: ''"' is an unexpected token. Expecting whitespace. Line 1, position 50.'
"

Answer 1

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more