What an Azure Storage Account Actually Is (and When You Need One)
One account, four different services, and a name you'll never remember.
By Shehryar Hassan, Microsoft 365 & Azure Consultant
If you've ever clicked "Create a resource" in the Azure portal and typed "storage" into the search box, you've probably seen half a dozen options that all sound the same. Storage account. Blob storage. File share. Disk. It's confusing the first time, and honestly it stays a little confusing after that too.
What it actually contains
A storage account isn't one service. It's a container for up to four different services that happen to share the same billing, the same access keys, and the same name:
- Blob storage, for unstructured files like PDFs, images, videos, or app data. This is the one most people mean when they say "Azure storage."
- File shares, which work like a network drive you can mount with a drive letter on Windows.
- Queues, used by developers to pass messages between parts of an application.
- Tables, a simple key-value store that's been around since before Cosmos DB existed.
You don't have to use all four. Most small setups only ever touch blob storage or file shares, and never look at the other two.
When you'd actually need one
You need a storage account any time something needs a place to put files that isn't a virtual machine's own disk. Some common real cases:
- A web app needs somewhere to store uploaded images or documents.
- You want a shared network drive for a small office without running your own file server, using Azure File Sync or a mapped file share.
- A backup job needs a destination outside your local network.
- You're storing logs or telemetry that a script writes to on a schedule.
The naming rules trip people up the first time too. Storage account names have to be globally unique across all of Azure, lowercase letters and numbers only, no hyphens allowed. So don't be surprised if the obvious name is already taken, even though you can't see anyone using it.
One thing worth deciding before you turn one on: pick your redundancy option (locally redundant, zone redundant, or geo redundant) at creation time. Changing it later usually means moving the data rather than flipping a setting. If you're not sure which to pick, locally redundant storage is fine for anything that isn't mission critical, and it's the cheapest option by a wide margin.
Get new posts by email
One note when there is something worth reading. No spam, unsubscribe anytime.
Related articles
Azure Traffic Manager, What It Does and How It's Different From Load Balancer
Traffic Manager and Load Balancer sound like they do the same thing. They don't. One works at the DNS level across regions, the other spreads traffic inside one region. Here's what each is actually for.
Azure Front Door, What It Does and When You'd Actually Use One
Azure Front Door routes visitors to the closest healthy copy of your site and can add a free SSL certificate along the way. Here's when it actually earns its keep.
What an Azure Managed Identity Actually Does (and Why You Want One)
Azure managed identities let an App Service, Function App, or VM authenticate to other Azure resources without you ever having to store or rotate a secret.