Disable anonymous read access to Azure Blob Storage when your applications should require authorization. The account-level setting overrides container settings that otherwise permit anonymous reads.
Check dependencies and permissions
Review applications and integrations before changing an existing account. Microsoft recommends analysing anonymous requests in metrics and logs to identify affected containers and clients. Move any intentionally public content to an account reserved for that purpose.
Changing the setting requires storage-account management permissions, such as Storage Account Contributor at the account scope or above.
Disable anonymous Blob access
- Open the storage account in Azure portal.
- Select Settings > Configuration.
- Set Allow Blob anonymous access to Disabled and save the change.
- Allow up to 30 seconds for propagation, then revisit Configuration to confirm the value.
Verify both access paths
Use an approved, nonsensitive test blob to check that a request without credentials or a signed token cannot retrieve its contents. Then test the authorized application path and confirm the intended operation still succeeds.
Record the test URL, time and result in your change notes without including credentials. If an application fails, inspect its authentication method and dependencies before altering the setting.
Understand the boundary
This control does not affect a static website hosted in the storage account. Review that separate endpoint explicitly; do not treat this setting as proof that every endpoint is private.
For another storage protection control, see our guide to requiring HTTPS for REST requests.

