Azure Storage Account Types Explained Simply: Which One You Actually Need UK 2026

The storage account confusion nobody talks about

When you're moving from healthcare into cloud engineering, Azure storage accounts feel like one big thing. They're not. Azure actually gives you four distinct storage account types, each designed to solve a different problem. Pick the wrong one in a technical interview or on day one in your new role, and you'll flag yourself as someone who skipped the basics.

The good news: the differences are simpler than they sound. You don't need a PhD in cloud architecture to understand them. You just need to know what job each one does.

What is an Azure storage account anyway?

Think of an Azure storage account as a container where Azure stores data. It's where you put files, databases, queues, and other information that your applications need. Every storage account has a unique name, lives in a specific Azure region, and has its own security and performance settings.

The type of storage account you create determines what data it can hold and how fast it can move that data around. That's it. The type is the decision point.

The four Azure storage account types

General-purpose v2 (GPv2)

This is the default and the one you'll use 80 per cent of the time.

GPv2 supports Blob storage (files and documents), Table storage (structured data), Queue storage (messages between applications), and File shares (like network drives). It's the Swiss Army knife of Azure storage. If you're not sure which type you need, start here.

Typical use cases: storing application logs, backing up databases, hosting website content, storing user-uploaded documents.

General-purpose v1 (GPv1)

This is the older version. Azure still supports it, but they're slowly phasing it out. If you see it mentioned in legacy systems or training from 2020, that's why.

GPv1 does most of what GPv2 does, but it's slower, costs slightly more, and doesn't support some modern features. There's almost no reason to create a new GPv1 account in 2026. This will come up in certification questions, though, so remember it exists.

Blob storage

This type does one thing: stores blobs (big objects like videos, images, backups, and unstructured data). It's faster for blob-only workloads and cheaper if you don't need the other features GPv2 offers.

The trade-off: Blob storage accounts can't hold Tables, Queues, or File shares. You're locked into blobs. Use this if you're running a video streaming service or managing massive backup files and nothing else.

Typical use cases: media libraries, archive storage, backup repositories, machine learning datasets.

BlockBlobStorage

This is the premium version for blobs. It's designed for high-performance scenarios where speed matters more than cost. It processes data faster and handles very large files more efficiently.

You'll rarely need this in your first IT role, but large organisations working with real-time video processing or financial data analysis use it. It's more expensive, so it's reserved for workloads that genuinely justify the cost.

How to actually choose between them

Here's the decision tree your team will use:

Do you only need to store unstructured data (files, videos, images)? Go with Blob storage or GPv2.

Do you need both blobs and tables, queues, or file shares? GPv2 is your answer.

Is speed critical and cost is secondary? Consider BlockBlobStorage.

Are you looking at an old system built before 2018? You might find GPv1. Migrate it to GPv2.

In your first months as an IT professional, you'll mostly see GPv2. That's the industrial default. Getting comfortable with GPv2 first means you can pick up the others in an afternoon when you need them.

Real differences that matter in your first job

Cost: GPv2 and Blob have similar pricing. GPv1 is slightly more expensive. BlockBlobStorage is the premium option, roughly 2 to 3 times the cost.

Speed: BlockBlobStorage is fastest. GPv2 is standard. Blob is optimised for blob access specifically, so it's fast for blobs but doesn't handle mixed workloads. GPv1 is noticeably slower on modern operations.

What you can store: This is the hard constraint. Blob storage only takes blobs. GPv2 takes everything. BlockBlobStorage only takes blobs, but faster. GPv1 takes everything, but slower.

Support: GPv2 is the modern standard. Azure teams support it fully. GPv1 still works but it's legacy. Blob and BlockBlobStorage are fully supported.

Where you'll see these in real work

In healthcare-to-tech transitions, many NHS trusts and private health providers are moving patient records and research data to Azure. They use GPv2 accounts to store both structured data (patient demographics in tables) and unstructured data (medical scans in blobs).

Media companies and research institutions handling large datasets typically pick Blob storage to keep costs down on massive archives.

Financial services organisations running real-time analytics might justify BlockBlobStorage for the speed.

This is the kind of knowledge your interviewers will test. Not "what is storage," but "when would you use Blob instead of GPv2?" That's a question that separates people who studied the exam from people who've actually thought about the problem.

If you're preparing for Azure certification or your first cloud role, understanding storage account types is foundational. It's one of those topics that feels abstract until you've created one yourself. That's why many people find a structured, hands-on approach invaluable.

We run the Azure Administrator Programme (£1,000 over 3 months) which covers storage accounts in depth, including practical labs where you'll create and configure different types, see the trade-offs in real time, and answer the exact questions your technical interview will ask. The programme is currently on our waitlist, but you can register your interest at smoothops365.com/courses to get notified when the next cohort opens.

Frequently asked questions

What's the difference between Blob storage and GPv2?

Blob storage specialises in unstructured data only (blobs), while GPv2 handles blobs, tables, queues, and file shares. Choose Blob if you only need blobs and want a slightly simpler offering. Choose GPv2 if you need flexibility or mixed data types. In practice, most teams just use GPv2 because the cost difference is small and the flexibility is worth it.

Can I change storage account type after creation?

No. You create a storage account with a specific type and that's locked in. If you pick the wrong type, you create a new one and migrate your data over. This is why getting it right at the start matters. In your first role, your team lead or architect will usually specify the type before you create it, so you won't be making this call alone.

Is GPv1 completely obsolete?

Not yet, but it's deprecated. Azure still supports it and legacy systems still run on it, but Microsoft stopped recommending it in 2019. For any new project in 2026, use GPv2. You'll only see GPv1 in older systems or exam questions testing whether you know the historical context.

Do I need BlockBlobStorage for my career in IT?

Probably not in your first role. Most organisations use GPv2 or Blob storage. BlockBlobStorage is for specialist high-performance scenarios. Once you're established in cloud, you might encounter it, but don't stress learning it in depth until then.

How much does each storage account type cost?

Pricing varies by region and usage, but roughly: GPv2 and Blob storage are similar (around £0.01 to £0.03 per GB for stored data), GPv1 is slightly higher, and BlockBlobStorage is 2 to 3 times more expensive. Azure's pricing calculator gives exact figures for your region at azure.microsoft.com/pricing. In the real world, your finance or cloud team calculates this, not you, but it's good to understand why types differ.