[BUG] Storage clients don't parse escape sequence in connection strings

[sebastienros]

Library name and version

Azure.Storage.Blobs

Describe the bug

When creating a BlobServiceClient from a connection string, if a key/value uses " to enclose its values then the client throws an exception.

Example:

new BlobServiceClient("DefaultEndpointsProtocol=http;AccountName=devstoreaccount1;AccountKey=\"Eby8vdM02xNOcqFlqUwJPLlmEtlCDXJ1OUzFT50uSRZ6IFsuFq2UVErCz4I6tq/K1SZFPTOtr/KBHBeksoGMGw==\";BlobEndpoint=http://127.0.0.1:50606/devstoreaccount1;");

This is the case when using DbConnectionStringBuilder to build/remove elements from a connection string, it will see the AccountKey has special chars ('=') and encode the value.

Expected behavior

Escape the values by handling escape sequences and surrounding double quotes.

Actual behavior

Throws an exception with the generic message: "No valid combination of account information found."

Reproduction Steps

new BlobServiceClient("DefaultEndpointsProtocol=http;AccountName=devstoreaccount1;AccountKey=\"Eby8vdM02xNOcqFlqUwJPLlmEtlCDXJ1OUzFT50uSRZ6IFsuFq2UVErCz4I6tq/K1SZFPTOtr/KBHBeksoGMGw==\";BlobEndpoint=http://127.0.0.1:50606/devstoreaccount1;");

Environment

No response

[github-actions]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @amnguye @jalauzon-msft @jaschrep-msft @nickliu-msft @seanmcc-msft.

[github-actions]

Hi @sebastienros, I'm an AI Support assistant here to help with your issue. While the Azure SDK team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.

• The issue appears when connection string values (like AccountKey) are enclosed in escaped double quotes. The SDK expects the value without extra surrounding quotes.
• When building connection strings (for example, using DbConnectionStringBuilder), ensure that the key values are provided without leading/trailing quotes. This avoids triggering the parsing error.
• For connection string-based client construction, the recommended configuration format is documented. For example, see the sample configuration for BlobServiceClient in the Azure.Extensions.AspNetCore.DataProtection.Blobs changelog where key values are unquoted.
• Using configuration files (as shown in the JSON sample in the documentation) may help avoid inadvertent extra quotes around credential values.

The Azure SDK team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!

[amnguye]

Where Azure product are you using that generates a connection string that puts the account key in quotations?

I don't believe the emulator connection string is even documented in that format where the shared key value is in enclosed with quotations.
See https://learn.microsoft.com/en-us/azure/storage/common/storage-use-azurite?tabs=visual-studio%2Cblob-storage#http-connection-strings

[sebastienros]

Where Azure product are you using that generates a connection string that puts the account key in quotations?

As mentioned in the description of the issue, we are using DbConnectionStringBuilder in Aspire to build the connection string to prevent malformed values, or unexpected property injections (similarly to SQL injections if it's not obvious).

[amnguye]

Looks like DbConnectionStringBuilder is a .NET class, but doesn't look like it's an Azure Storage product.

Unfortunately, I cannot speak to what's presented in Aspire to build connection strings, or in this case specifically Azure Storage connection strings. It doesn't look like anything in the DbConnectionStringBuilder eludes to supporting building Azure Storage connection strings.

I can point you to our documentation on how to configure a connection string for an Azure Storage account.

https://learn.microsoft.com/en-us/azure/storage/common/storage-configure-connection-string#configure-a-connection-string-for-an-azure-storage-account

[sebastienros]

Looks like DbConnectionStringBuilder is a .NET class, but doesn't look like it's an Azure Storage product.

I mean the Azure SDK for .NET is built in dotnet, it could (but I really mean should) use this class to parse connection strings. Am I missing something? I will dig up to see how it's doing it right now.

[amnguye]

I might be making a leap here, but I believe the Db in the class name, DbConnectionStringBuilder stands for DataBase? Looking at the documentation, I don't see a note of it supporting constructing an Azure Storage Connection Strings. Though I can fully understand the terminology use here, since regularly DataBase and Storage gets used interchangeably.

In the documentation I linked above, it notes how to construct an Azure Storage Connection String and it doesn't include wrapping the shared key in quotations.