Azure Storage Account: Types, Setup and What Drives Cost

Introduction

An Azure storage account is the starting point for Blob Storage, Azure Files, Queue Storage, and Table Storage. But the account kind, redundancy level, access pattern, and data movement decide whether it fits your workload and what you pay.

Teams commonly trip over the same things. They confuse storage services with account types, pick a legacy or needlessly expensive configuration, or forget that transactions, retrieval, replication, and transfer all show up on the bill.

Cloud-wide, Flexera's 2026 survey of 753 cloud decision-makers reports 29% wasted cloud spend. That's a general figure, not a storage-specific one, but it frames the stakes.

This guide covers account types, setup, cost drivers, and an optimization checklist.

Key Takeaways

  • A storage account is a namespace and management boundary, not a storage service itself.
  • Standard GPv2 is the usual starting point; premium kinds suit specific performance needs.
  • Cost covers transactions, tiers, retrieval, redundancy, transfer, and optional features, not just capacity.
  • Validate with the Pricing Calculator, Cost Management, and lifecycle policies before committing.

What Is an Azure Storage Account? Types, Services, and Redundancy

Azure storage accounts vs. Azure storage services

A storage account is a unique namespace. The account name becomes part of every object URL, and settings such as access controls, networking, and redundancy are managed at this level.

Services are what you store data in:

  • Blob Storage (including Data Lake Storage): unstructured objects
  • Azure Files: managed file shares
  • Queue Storage: messaging between components
  • Table Storage: NoSQL key-value data

Managed disks are administered separately from this model, so don't assume an account setting governs them.

Main Azure storage account types

Account kind Best for Redundancy
Standard GPv2 Blob, Files, Queue, Table; Microsoft recommends it for most scenarios LRS, ZRS, GRS, RA-GRS, GZRS, RA-GZRS (region dependent)
Premium Block Blob High transaction rates, smaller objects, consistently low latency LRS or ZRS
Premium File Shares Azure Files only LRS or ZRS
Premium Page Blobs Page blobs only LRS or ZRS

GPv2 supports Hot, Cool, Cold, and Archive blob tiers. Premium kinds are listed separately, so don't assume the same tier matrix applies.

GPv1 and legacy Blob Storage accounts are retiring. Microsoft disables new GPv1 creation in September 2026 and retires it in October 2026, with remaining accounts migrated to GPv2. Check what kind your accounts are and plan the upgrade before those cutoffs.

The GPv1 upgrade is in-place with no downtime or data copy, but it is permanent. Microsoft's migration guidance warns bills can rise for read-, write-, and list-heavy workloads, and recommends setting a default Hot or Cool tier.

Choosing redundancy and performance settings

Option Placement Durability
LRS One datacenter in the primary region; lowest cost 11 nines
ZRS Three or more availability zones in the primary region 12 nines
GRS / RA-GRS LRS in primary, async copy to secondary region 16 nines
GZRS / RA-GZRS ZRS in primary, async copy to secondary region 16 nines

The RA variants add read access to the secondary region, even when the primary is unavailable. Plain GRS and GZRS secondaries are not directly readable.

Support varies. Azure Files supports LRS, ZRS, GRS, and GZRS but not the RA variants. ZRS and GZRS need supported availability-zone regions. Check Microsoft's redundancy page for current availability figures.

Azure storage redundancy options showing placement and durability levels

How to Set Up an Azure Storage Account

Decide the account design before creating it

Settle these before you click Create:

  • Subscription and resource group
  • Globally unique name (3-24 characters, lowercase letters and numbers only)
  • US region
  • Account kind and performance tier
  • Default access tier and redundancy
  • Whether you need hierarchical namespace (for Data Lake Storage workloads)

Then match the account to the workload. Shared application data, rarely accessed objects, file shares, analytics data, and latency-sensitive storage don't all belong in the same configuration.

A GPv2 account with Cool tiering suits infrequently read objects. A Premium File Shares account suits performance-sensitive shares. No single kind fits everything.

Create the account through the Azure Portal

  1. Open Storage accounts and select Create.
  2. Choose the subscription and resource group.
  3. Enter the account name and region.
  4. Select performance and redundancy.
  5. Configure the Advanced, Networking, and Data protection tabs.
  6. Review the validation result and create.

Review these settings before deploying:

  • Secure transfer: required by default; keep it.
  • Minimum TLS: 1.2 is the default and the recommendation.
  • Public network access: accounts are internet-reachable by default. Disable it where possible, or use a deny-by-default firewall or private endpoints.
  • Anonymous blob access: disable it. It's separate from network access.
  • Authorization: Shared Key is on by default. Prefer Microsoft Entra ID and disable keys when feasible.
  • Recovery: soft delete is optional; Microsoft recommends at least 7 days of retention.

Automate and validate the deployment

Scripted deployment keeps development, staging, and production consistent. Microsoft's documented Azure CLI example:

az storage account create --name <account-name> --resource-group storage-resource-group --location eastus --sku Standard_RAGRS --kind StorageV2 --min-tls-version TLS1_2 --allow-blob-public-access false

After deployment:

  • Confirm endpoints and permissions, and test application connectivity.
  • Verify redundancy and lifecycle policies.
  • Turn on relevant metrics and logs.
  • Apply tags for application, owner, and environment.
  • Create a budget with cost alerts.

Azure storage account deployment validation checklist workflow

What Drives Azure Storage Account Cost?

There is no flat "account fee." Charges depend on the services, data, capacity, and operations used inside the account. Prices vary by region and agreement, so pull current numbers from Microsoft's pricing pages.

Storage capacity, provisioned resources, and account performance

Bills reflect data stored, account kind, performance tier, how long data stays, and, for some services, provisioned capacity. Azure Files shows the difference clearly. Provisioned v2 bills storage, IOPS, and throughput separately. Pay-as-you-go applies to HDD classic shares and bills used storage, transactions, and transfer.

Access tiers, data retrieval, and retention rules

Hot, Cool, and Cold are online. Archive is offline and needs rehydration, which can take up to 15 hours.

  • Minimum retention: Cool 30 days, Cold 90 days, Archive 180 days; Hot has none.
  • Early deletion: deleting, overwriting, or moving data sooner incurs prorated charges.
  • Archive limits: only LRS, GRS, and RA-GRS support it, not ZRS or GZRS.

Lifecycle management is free and can tier or delete data automatically. But a last-access-time update bills as an "other" transaction, and badly designed rules can trigger retrieval or early-deletion charges.

Transactions and data operations

Operations are billed per transaction: reads, writes, lists, deletes, and more, depending on the tier. Table Storage bills batch write, scan, and list classes; Queue Storage bills Class 1 and 2 operations.

Model these workloads separately:

  • Many small objects that multiply transaction counts
  • Frequent polling or repeated metadata calls
  • High request rates relative to stored capacity

A 100 TB archive of large, rarely read files and a 2 TB container hit by millions of small reads can cost very differently.

Azure storage workload cost comparison by capacity and transaction volume

Redundancy and replication

Each step up replicates more data and changes the recovery model. LRS is the lowest-cost option; geo-redundant accounts add a geo-replication transfer meter. Weigh that against your recovery point objective, recovery time objective, regional resilience needs, and whether applications must read from the secondary.

Data transfer and network access

Azure storage charges and networking charges are separate line items. Data into Azure is free, and the first 100 GB per month of egress is free according to Azure's bandwidth pricing. Beyond that, data leaving a region can incur charges. Private endpoints add endpoint-hour and data-processing meters.

Consider a backup job writing to a second region while an app in a third region reads the data. That's cross-region replication plus egress, on top of storage.

Optional features, protection, and observability

Protection and monitoring aren't free add-ons.

  • With versioning enabled, each overwrite creates a new version; snapshots bill for the capacity they hold.
  • Soft-deleted data stays billable until retention expires.
  • Change feed, blob index tags, and inventory have their own meters.
  • Storage Analytics logs accumulate in the account.
  • Log Analytics bills ingestion, retention, and export; standard platform metrics are free.

Azure storage optional features and billable protection monitoring components

Price these into the design from the start.

How to Optimize and Monitor Azure Storage Costs

Build controls into the storage lifecycle

  • Right-size the account and performance tier.
  • Apply lifecycle rules based on measured access patterns.
  • Delete stale data and unnecessary copies.
  • Choose the cheapest redundancy that meets business requirements.

Run a recurring review for:

  • Orphaned resources, unused containers, and file shares
  • Abandoned snapshots and versions
  • Excessive logging
  • Data kept past its compliance need

Blob inventory reports (daily or weekly CSV or Parquet) list age, size, and tier to support that audit. Inventory scans are billable too. Azure Advisor can flag high transaction-per-TB workloads as premium candidates and suggest reserved capacity.

Use native Azure cost and observability tools

  • Pricing Calculator: model region, redundancy, tier, and usage. It's an estimate, not a quote.
  • Cost Management: allocate spend by tag and resource group.
  • Budgets: alert on actual or forecast cost. They don't stop usage.
  • Storage Insights: account- and subscription-level views of capacity, transactions, latency, and failures.

Extend visibility across multi-cloud block storage

For enterprises running Azure alongside AWS or Google Cloud, Lucidity provides an intelligence layer for cloud block storage. It delivers visibility into volumes across all three clouds and autonomous optimization. It covers block storage, not storage-account services. Azure-native tools remain the source for storage-account billing and service-level pricing.

Conclusion

The right storage account comes from workload behavior, service requirements, resilience goals, security controls, and total cost, not capacity alone.

Model the design in the Azure Pricing Calculator, test with real traffic, and monitor actual usage. Then revisit tiers, redundancy, retention, and data movement as requirements change.

Frequently Asked Questions

How much does an Azure storage account cost?

There's no flat account fee. Cost depends on what you use inside it: capacity, performance, transactions, access tier, redundancy, retrieval, and transfer. Use Microsoft's pricing pages and the Azure Pricing Calculator.

What are the different types of Azure storage accounts?

The current types are Standard GPv2 and the premium kinds: Block Blob, File Shares, and Page Blobs. GPv1 and legacy Blob Storage accounts are being retired, so check Microsoft's guidance for migration status.

What are LRS, GRS, and ZRS in Azure storage accounts?

LRS keeps data in one datacenter, ZRS spreads it across three or more zones in a region, and GRS adds asynchronous replication to a secondary region. Each has a different resilience model and cost.

What are the differences between Azure storage account v1 and v2?

GPv1 is legacy and lacks the access tiers and redundancy options GPv2 offers. Upgrading is in-place and permanent, but transaction costs can change, so review read, write, and list volumes first.

What is an Azure storage account?

It's the namespace and configuration boundary for Azure storage services. It controls endpoints, access, performance, networking, and redundancy settings.