Azure Storage: ContainerNotFound / BlobNotFound — The specified container (or blob) does not exist
The container or blob path doesn’t exist in that storage account.
Seen on:
Azure
Meaning
Container names must be lowercase; blob names are case-sensitive and include the full virtual path. Using the wrong account (e.g. Azurite vs cloud) or forgetting to create the container first are common.
Common causes
- Container not created yet
- Case mismatch in blob path
- Wrong storage account/connection string (dev vs prod, Azurite)
- Blob deleted (soft delete)
⚡ Quick fix
- Create the container (CreateIfNotExists)
- Check the exact blob path and case
- Confirm the account in the connection string
Detailed fix by platform
Azure CLI
- bash
az storage container list --account-name stapp --auth-mode login --query "[].name" az storage blob list --account-name stapp -c data --prefix reports/ --auth-mode login --query "[].name"
How to diagnose
- Account — Which one?
- Container — Exists?
- Path — Exact blob name
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in Azure
Other ways to find it
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 7 Oct 2026