I’ve bumped into a funny Windows Azure Storage API feature lately.
I was trying to read / write the meta data of a blob-container using a Shared Access Signature (SAS) and got a 404 Resource Not Found.
Well, after flipping my algorithm upside down quite a few times I considered that was by designed.
It is confirmed, it is by design!
You cannot use a Shared Access Signature to create or delete a container, or to read or write container properties or metadata.
Thanks to Neil Mackenzie for providing the reference!
Of course, this means that if you really need to do this, you have to use your Primary or Secondary Key and no SAS. Sad…