100% Free Forever
AI-Powered Learning
Industry Expert Content
Certificates & Badges
Learn At Your Own Pace
Azure

Azure Storage Account Types

A guide to choosing between general-purpose and premium Azure storage account kinds, and how performance and redundancy tiers interact.

StorageBeginner9 min readJul 10, 2026
Analogies

Overview of Storage Account Types

An Azure storage account is the top-level namespace that groups together your blob containers, file shares, queues, and tables under a single globally unique endpoint. The account type you choose determines which services and performance tiers are available. General-purpose v2 (GPv2) is the modern default supporting blobs, files, queues, and tables with access to all tiers, while legacy general-purpose v1 lacks Cool/Archive tiers and is rarely chosen for new deployments today.

🏏

Cricket analogy: A storage account is like a franchise's central headquarters (say Mumbai Indians) that houses the batting unit, bowling unit, and support staff (blobs, files, queues) all under one team umbrella, rather than each department operating independently.

General-Purpose v2 vs Specialized Accounts

Beyond GPv2, Azure offers specialized account kinds: BlockBlobStorage accounts use premium SSD-backed storage for high-transaction, low-latency block and append blob workloads, and FileStorage accounts provide premium Azure Files shares for latency-sensitive workloads like databases hosted on file shares. Choosing the right kind at creation time matters because you generally cannot convert a general-purpose account into these specialized premium kinds later without migrating data.

🏏

Cricket analogy: Choosing GPv2 versus BlockBlobStorage is like picking a general all-format player versus a T20 specialist power-hitter — the specialist (premium) excels in a narrow high-intensity role but isn't as flexible across formats.

bash
# General-purpose v2 account (default, supports all tiers)
az storage account create \
  --name gpv2demoacct \
  --resource-group rg-storage-demo \
  --location eastus \
  --sku Standard_LRS \
  --kind StorageV2

# Premium BlockBlobStorage account for high-throughput blob workloads
az storage account create \
  --name premiumblockacct \
  --resource-group rg-storage-demo \
  --location eastus \
  --sku Premium_LRS \
  --kind BlockBlobStorage

# Premium FileStorage account for low-latency Azure Files
az storage account create \
  --name premiumfileacct \
  --resource-group rg-storage-demo \
  --location eastus \
  --sku Premium_LRS \
  --kind FileStorage

Performance Tiers: Standard vs Premium

Standard performance accounts are backed by magnetic (HDD-class) storage hardware and are cost-effective for general workloads with moderate throughput needs. Premium performance accounts are backed by SSDs and deliver consistent low-latency, high-IOPS performance, but each premium account is dedicated to a single service type — for example a Premium FileStorage account only serves Azure Files, it cannot also hold blob containers.

🏏

Cricket analogy: Standard tier is like a domestic first-class match paced over four days — solid and economical; Premium tier is like a T10 blitz format demanding instant, high-intensity performance every single ball.

Premium performance storage accounts are single-purpose by design: BlockBlobStorage holds only block/append blobs, FileStorage holds only Azure Files shares. If you need both premium blobs and premium files, you must provision two separate premium storage accounts.

Replication Choices at Account Creation

Every storage account also specifies a redundancy option — such as LRS, ZRS, GRS, or GZRS — chosen at creation time, which determines how many copies of your data are kept and where. This choice directly affects your durability SLA and disaster-recovery posture, and while some redundancy conversions (like LRS to GRS) are supported after creation, others require planning, so it's worth deciding deliberately upfront rather than accepting the default.

🏏

Cricket analogy: It's like deciding before the toss whether your team will field a defensive setup (LRS, protecting locally) or a aggressive setup ready for any away conditions (geo-redundant) — the choice shapes your whole strategy, not something you casually flip mid-innings.

Not all account type and replication combinations are mutually compatible or freely changeable — for example, ZRS is unavailable in some regions and premium account kinds don't support every redundancy option. Confirm supported combinations for your target region before provisioning production workloads.

  • A storage account is the top-level container for blob, file, queue, and table services under one endpoint.
  • General-purpose v2 (GPv2) is the modern default account kind supporting all services and access tiers.
  • BlockBlobStorage and FileStorage are premium, single-purpose account kinds for high-throughput, low-latency workloads.
  • Standard accounts use HDD-class storage; Premium accounts use SSD-backed storage with higher, more consistent performance.
  • Premium accounts are dedicated to one service type — you cannot mix premium blobs and premium files in one account.
  • Redundancy (LRS/ZRS/GRS/GZRS) is chosen at account creation and shapes your durability and disaster-recovery posture.
  • Not every account kind supports every redundancy option or region, so validate combinations before provisioning.

Practice what you learned

Was this page helpful?

Topics covered

#Azure#AzureFundamentalsStudyNotes#CloudComputing#AzureStorageAccountTypes#Storage#Account#Types#General#StudyNotes#SkillVeris