
The choice affects application compatibility, latency, throughput, supported services, and your Azure bill. Microsoft's schedule disables new GPv1 account creation in September 2026, with full retirement and automatic GPv2 migration in October 2026. GPv1 is now a migration topic.
This guide gives you a decision framework. Pricing, limits, and feature support vary by region and change often, so confirm current numbers in Microsoft's Azure documentation before committing.
Key Takeaways
- GPv2 is the right starting point for most new, mixed-service, cost-sensitive deployments.
- Premium is a family of specialized accounts, not a universal GPv2 upgrade.
- GPv1 is legacy; keep it only with a verified constraint and a migration plan.
- Choose by workload behavior, services, access patterns, redundancy, and total cost, not capacity alone.
GPv2 vs Premium vs GPv1: Quick Comparison
Account scope and supported services
| Account type | Supported services | Redundancy |
|---|---|---|
| Standard GPv2 | Blob (including Data Lake Storage), Files, Queues, Tables | LRS, ZRS, GRS, RA-GRS, GZRS, RA-GZRS |
| Premium block blobs | Blob, including Data Lake Storage | LRS, ZRS |
| Premium file shares | Azure Files (SMB and NFS) | LRS, ZRS |
| Premium page blobs | Page blobs only | LRS (ZRS support is documented inconsistently) |
| Standard GPv1 (legacy) | Blob, Files, Queues, Tables | LRS, GRS, RA-GRS |
Premium variants cover far less ground than GPv2. Verify feature support for your exact configuration in Microsoft's account overview.
Performance and latency
Premium accounts are SSD-backed. Premium block blobs target low latency and high IOPS for small objects. Premium Files states single-digit millisecond latency for most I/O operations, which is not a guarantee for your application.
Published scale targets differ widely:
- Standard GPv2 (East US): 5 PiB default capacity, 40,000 requests/sec, 60 Gbps ingress, 200 Gbps egress
- Premium Files (SSD provisioned v2): 256 TiB, 102,400 IOPS, 10,340 MiB/sec per account
- Premium page blob accounts: 35 TB provisioned disk capacity, up to 50 Gbps for LRS
Premium makes sense when you see predictable-latency needs, high transaction rates, or heavy random reads and writes. Microsoft flags workloads above roughly 35-40 transactions/sec per TB as candidates. Ordinary app data and backups rarely need it.

Don't confuse Premium page blob accounts with managed disks. Managed disks are Azure-managed block volumes for VMs: you pick a type and size, and Azure handles provisioning. Microsoft recommends managed disks when unmanaged-disk account targets are exceeded.
Cost and billing
A per-GB price alone misleads. Compare:
- Stored capacity and transaction charges
- Data retrieval and early-deletion penalties
- Transfer and egress
- Redundancy
- Real utilization
Premium block costs more per GB but less per transaction, so write-heavy, transaction-heavy workloads can come out cheaper. Premium Files v2 bills provisioned storage, IOPS, and throughput, with the first 3,000 IOPS and 100 MiB/sec included.
GPv2 offers flexibility through access tiers and lifecycle management. Model your workload in the official pricing pages and calculator, using your own region, redundancy, and tier.
Access tiers, lifecycle, and redundancy
| Tier | Behavior | Minimum duration |
|---|---|---|
| Hot | Online, frequent access | None listed |
| Cool | Online, infrequent access | 30 days |
| Cold | Online, rare access | 90 days |
| Archive | Offline; rehydration up to 15 hours | 180 days |
GPv2 supports these tiers for block blobs. Premium block data cannot be tiered to Hot, Cool, Cold, or Archive, so it is a poor fit for archive-oriented data. Lifecycle management works on both GPv2 and Premium block accounts, but Premium supports deletion actions only.

Redundancy is a separate decision. Every service in an account shares one redundancy setting, and Archive only supports LRS, GRS, and RA-GRS.
Recommended position
- GPv2: default for new general-purpose work, after workload testing and a regional check
- Premium: targeted choice for validated performance needs
- GPv1: legacy; needs a documented reason and modernization plan
What Are GPv2, Premium, and GPv1 Storage Accounts?
Four terms get mixed up constantly:
- Account kind: GPv2, GPv1, or a Premium variant
- Services: Blob, Files, Queue, Table
- Performance and tier: Standard vs Premium, and Hot/Cool/Cold/Archive
- Redundancy: LRS, ZRS, GRS, and so on
They are independent dials. Changing one does not change the others.
GPv2: The Modern General-Purpose Default
Microsoft recommends GPv2 for most scenarios. It incorporates GPv1 functionality and adds tiering flexibility, and it covers Blob, Files, Queues, and Tables in one account.
It fits web applications, application data, logs, backups, analytics staging, and mixed-service environments where flexibility beats specialized latency. Verify limitations for the specific feature you plan to use.
From a FinOps angle, GPv2 gives you the levers that matter:
- Access tiers and lifecycle policies to match cost to access frequency
- Redundancy choices sized to the data's value
- Pay-for-usage billing, so you don't buy performance you don't need
Watch retrieval charges. Moving Cool data back to Hot incurs read-operation and per-GB retrieval fees, and early deletion or tier moves can trigger penalties.
Premium: Specialized Performance Account Variants
The three variants
- Premium block blobs: low-latency object access, interactive applications, IoT and streaming analytics, AI/ML, small objects. Available only in selected regions.
- Premium file shares: enterprise and high-performance SMB or NFS shares. SSD file shares with ZRS are listed for East US, East US 2, Central US, South Central US, West US 2, and West US 3; LRS is broader.
- Premium page blobs: frequent random reads and writes, and sparse or index-based structures, including legacy unmanaged-disk scenarios.
Trade-offs
You get SSD performance and predictable latency. The trade-off is higher capacity cost and a narrower service scope. Premium also lacks Archive-style tiering.
Premium account or Premium managed disk?
If you need a block volume for a VM, you almost always want a managed disk, provisioned as its own resource. Choose a Premium storage account when you need object, file-share, or page-blob access patterns specifically.
GPv1: The Legacy General-Purpose Account
GPv1 supports Blob, Files, Queues, and Tables, but lacks blob-level Hot/Cool/Cold/Archive tiering and newer features. Its published scale targets are also lower, with 10 Gbps ingress compared to 60 Gbps for GPv2 in East US.
Old accounts persist for practical reasons: legacy deployment templates, application compatibility worries, migration risk, and inertia.
Upgrading to GPv2
Microsoft's upgrade guide describes the path:
- Free, with no downtime or data-loss risk
- Available through the portal, PowerShell, or CLI
- Irreversible: no downgrade to GPv1
- Unspecified account tier defaults to Hot
- Legacy GPv1 ZRS accounts have a separate procedure with an October 13, 2026 deadline; manual migration requires downtime

One caution: GPv2 uses more granular transaction pricing, which can raise bills for read/write-heavy workloads despite lower storage costs. Inventory your dependencies and test before you move.
GPv2 vs Premium vs GPv1: What Is Better?
There is no universal winner. The answer depends on the data service, access pattern, performance goal, compatibility needs, and full cost model.
Choose GPv2 when
- You need broad service support or mixed services
- Tiers and lifecycle policies would cut cost
- The workload is a new application, backups, logs, or general object storage
Choose Premium when
Testing shows standard performance can't meet latency, throughput, I/O, or concurrency needs. Pick the variant by service:
- Block blobs for objects
- File shares for SMB/NFS
- Page blobs for random-access page data
Retain GPv1 only when
A current dependency justifies it. Plan a migration when you hit any of these:
- Unsupported features
- Rising operational cost
- Modernization work or a need for newer capabilities
With retirement scheduled, the calendar is effectively the trigger.
A decision sequence
- Identify the storage service you need.
- Measure read/write and access patterns.
- Define latency and availability targets.
- Model storage and operation costs.
- Validate regional availability.
- Run a representative workload test.
For testing, Microsoft warns that short Azure Files tests can measure burst credits, not provisioned performance. Also, Blob targets that are approached or exceeded cause throttling and higher latency.
Operations after the decision
A correct choice can still become an over-provisioned one. Review these on a schedule:
- Utilization and idle resources
- Transaction patterns
- Tier placement
- Redundancy and egress
Real-World Examples
Premium Files: a GlusterFS migration
In a Microsoft Azure Storage blog post from June 2025, an enterprise customer working with TCS moved application shares to Premium Files. The old share was limited to about 1,500 IOPS, and SQL Server workloads needed more.
The Premium configuration gave 3,000 IOPS and 200 MB/sec base performance per share. The customer reported SQL performance gains and met 15-minute RTO/RPO requirements. These are case-specific results, not Premium guarantees. GPv2 standard performance wasn't the fit because the requirement was provisioned file performance.
A GPv2 example
Public case studies rarely name GPv2 as the account kind explicitly. Most generic Azure Blob deployments run on it, so confirm the account kind in your own subscription.
When the real problem is block storage
If your review shows the bigger issue is visibility, over-provisioning, or manual tuning of Azure block storage (disks, not Blob account kinds), that's where Lucidity helps. It provides real-time visibility into block-storage volumes and autonomously optimizes eligible multi-cloud environments, with no infrastructure changes. Try the free storage assessment to see where you stand.
Conclusion
For most new general-purpose storage, choose in this order:
- Start with GPv2 as the default account kind
- Select a Premium variant only for a validated performance requirement
- Treat GPv1 as legacy that needs clear justification and a modernization plan
Account kind is only one piece of the architecture. Also weigh:
- Access tiers and redundancy
- Security and lifecycle policies
- Egress, utilization, and ongoing cost visibility
Frequently Asked Questions
What are the differences between an Azure Storage account v1 and v2?
GPv1 is the legacy general-purpose kind; GPv2 is the modern one. GPv2 adds blob-level tiering, more redundancy options, and higher scale targets. See Microsoft's upgrade guidance for migration.
What are the key differences between Azure ADLS Gen1 and Gen2?
ADLS Gen1 was a separate product, retired February 29, 2024. Gen2 is a set of Blob Storage capabilities, with hierarchical namespace providing directory and file-system semantics. GPv1 and GPv2 are account kinds, a different concept.
Is GPv2 better than GPv1?
For new deployments, yes. GPv2 supports newer capabilities and flexible cost controls. GPv1 may remain briefly for compatibility, but it is being retired.
When should I choose a Premium Azure storage account?
Choose Premium when low-latency, high-throughput, or high-I/O needs exceed standard performance. Match the Premium variant to your Blob, Azure Files, or page-blob workload.
Can I upgrade an Azure Storage account from GPv1 to GPv2?
Generally yes. Upgrades are free and without downtime, but they cannot be reversed. Check eligibility, dependencies, and testing needs first. Legacy GPv1 ZRS accounts follow a separate process.
How do Azure storage account type and access tier affect cost?
Account kind sets available services and performance model. Access tier shifts storage, transaction, and retrieval economics. Model the full workload cost, not capacity alone.