Azure Storage account allows unencrypted (HTTP) transfer
Azure Storage has a 'Secure transfer required' setting. When it's off, the account accepts HTTP as well as HTTPS, so requests — including SAS tokens in the URL — can be sent in the clear.
Why it matters
Anyone on the network path can read or tamper with data sent over HTTP, and a SAS token observed in a plain request can be replayed.
It's a one-flag fix that modern baselines (CIS Azure) require, and leaving it off is an easy audit finding.
How to check for it
- Portal → Storage account → Configuration → 'Secure transfer required' should be Enabled.
- az storage account show -n <name> --query enableHttpsTrafficOnly — it should be true.
How to fix it
- Enable it: az storage account update -n <name> --https-only true.
- Also set the minimum TLS version to 1.2 on the account.
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
- Will enabling it break existing clients?
- Only clients that connect over plain HTTP, which should be none — every current SDK and tool uses HTTPS by default.