Setting the "defaultServiceVersion" makes no difference on requests without the "x-ms-version" headers set

Behzad 40

Hello,

I've used the following command to set the "defaultServiceVersion" unto our Storage Account:

az storage account blob-service-properties update --set defaultServiceVersion="2020-04-08" --account-name FOOBAR

So that when I interact with the Storage Account API (https://FOOBAR.blob.core.windows.net/), I wouldn't have to set it.

I can see that it is set and accepted by Azure when I do blob-service-properties show

User's image

However, when I use Postman to send a request to it, I still have to always set the x-ms-version so that it accepts Bearer FOOBAR . Otherwise:

Authentication scheme Bearer is not supported in this version.

I've tried it with the 2025-01-05 , no luck. The Storage Account is in West Europe.

Keshavulu Dasari 3,185 Reputation points Microsoft Vendor

2025-01-28T17:44:35.2666667+00:00
Hi Behzad,

Greetings & Welcome to Microsoft Q&A forum! Thanks for posting your query!

I Understand an issue where the defaultServiceVersion setting isn't being applied as expected when making requests to your Azure Storage Account. I Suggest few things you can check and try:

Ensure Correct Version Setting:

Verify that the defaultServiceVersion is correctly set by running:
az storage account blob-service-properties show --account-name FOOBAR
Ensure it returns the expected version (2020-04-08).

Check Request Headers:

When making requests via Postman, ensure that the x-ms-version header is included. Sometimes, the default version might not be applied automatically, and explicitly setting this header can help.

Bearer Token Authentication:

The error message "Authentication scheme Bearer is not supported in this version" suggests that the version you're using might not support Bearer token authentication. Make sure you're using a version that supports this authentication scheme. You might need to include the x-ms-version header explicitly in your requests to ensure compatibility.

Role Assignments & Network and Firewall Settings:

Ensure that the Azure AD app you're using to fetch the OAuth token has the necessary roles assigned, such as "Storage Blob Data Owner". Verify that there are no network security group (NSG) rules or firewall settings that might be restricting access to your storage account.

Above suggested don't resolve the issue, please check the Azure Storage account logs for more specific error messages or consider regenerating the authentication tokens or keys as necessary

If you have any other questions or are still running into more issues, let me know in the "comments" and I would be happy to help you.
Keshavulu Dasari 3,185 Reputation points Microsoft Vendor

2025-01-29T23:29:45.3733333+00:00

Hi Behzad,

Just checking in to see if the response helped. If you have any questions, let me know in the "comments" and I would be happy to help you.
Behzad 40 Reputation points

2025-01-30T12:36:18.08+00:00

The response helped somewhat, especially since you mentioned that explicitly setting the header might be required.

That comment pushed us to use the Azure Blob REST API directly, instead of using the @azure/storage-blob library. Since it was not easy to add such a header to the library.

But that's a conversation that belongs to GitHub.
Keshavulu Dasari 3,185 Reputation points Microsoft Vendor

2025-01-30T20:12:05.8533333+00:00

Hi Behzad,
I understand the challenge you are facing with the @azure/storage-blob library. Sometimes, working directly with the REST API can provide more control and flexibility, especially when specific headers need to be set.

Share via

Setting the "defaultServiceVersion" makes no difference on requests without the "x-ms-version" headers set

Your answer