If you are unable to access blob data despite having anonymous access enabled, it might be due to incorrectly targeting the container URL instead of the blob URL. Additionally, the blob could be in an archived state. Ensure you are pointing directly to the blob URL and rehydrate any archived blobs before attempting access. By default, anonymous access is not permitted unless explicitly configured. When enabled, it allows clients to read data without authorization, which can pose a security risk. Ensure anonymous access is only enabled if absolutely necessary.
To rehydrate an archived blob:
- Navigate to your Azure Storage account in the Azure portal.
- Find the archived blob you want to rehydrate.
- Change the access tier of the blob from "Archive" to "Hot" or "Cool".
For checking which storage accounts and containers have anonymous access enabled, you can refer to the following resources: - Configure anonymous read access for containers and blobs - Identify classic storage accounts and migrate them to ARM
Hope this helps. If you have any follow-up questions, please let me know. I would be happy to help.
Please do not forget to "Accept the answer" and "up-vote" wherever the information provided helps you, as this can be beneficial to other community members.