[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!