Azure Storage account allows public blob access
Azure Storage can serve blobs anonymously when the account allows public access and a container is set to 'Blob' or 'Container' access level. That data is then readable by anyone with the URL.
Why it matters
Public storage accounts are a common source of leaked backups, logs and customer files — the same class of incident as an open S3 bucket.
Access can be turned on per container, so one container set public slips past an otherwise private account.
How to check for it
- Portal → Storage account → Configuration: check 'Allow Blob anonymous access'. Then review each container's Public access level.
- az storage account show -n <name> --query allowBlobPublicAccess, then az storage container list for any publicAccess != null.
How to fix it
- Set 'Allow Blob anonymous access' to Disabled at the account level; this overrides any container that tries to be public.
- az storage account update -n <name> --allow-blob-public-access false. Serve genuinely public content through a CDN with a private origin instead.
SkyShield checks this automatically
Connect your AWS, Cloudflare, GitHub, GitLab, Hetzner or DigitalOcean account read-only and SkyShield flags this across every account and region, with the fix in plain words — alongside the agent that watches your servers. Start free.
FAQ
- How do I share one file without making the container public?
- Use a time-limited SAS token or a stored access policy — the link expires and no container has to be anonymous.