Overview of general purpose (GPv1) with zone redundant storage (ZRS) redundancy retirement

Azure Storage is retiring the general purpose v1 (GPv1) with ZRS redundancy storage account configuration. This article explains what the change means for workloads using general purpose v1 (GPv1) with ZRS redundancy and how to prepare for a smooth transition to general-purpose v2 (GPv2) with modern ZRS.

About GPv1 with ZRS redundancy

General purpose v1 (GPv1) with ZRS redundancy refers to legacy Standard_ZRS replication used with GPv1 accounts (account kind Storage, not StorageV2). Unlike modern ZRS on GPv2, which replicates synchronously across three availability zones in the same region, GPv1 with ZRS redundancy does not provide that within region, three zone synchronous design and can rely on different replication topology that may require a platform initiated failover to access secondary copies.

For a refresher on modern redundancy options and characteristics (LRS, ZRS, GRS, GZRS, and read access variants), see storage redundancy options

Why GPv1 with ZRS redundancy is being retired

Azure is standardizing on GPv2 to deliver consistent resiliency, feature breadth, and management across all storage accounts. GPv2:

• Provides modern ZRS (synchronous replication across three availability zones) for higher availability in region.
• Enables per blob access tiers (hot/cool/archive) and lifecycle management for cost optimization.
• Supports ADLS Gen2, immutable storage, object replication, and broad ecosystem integrations.
• Uses the Azure Resource Manager (ARM) control plane with Azure AD RBAC, tags, and policies for consistent governance.

Retiring GPv1 with ZRS redundancy simplifies the platform and ensures customers benefit from modern capabilities and consistent pricing.

Benefits of migrating to GPv2

The table below summarizes the key differences most customers care about:

Retirement timeline and key milestones

Preparing for migration

To minimize risk and ensure a smooth migration:

1. Inventory your general purpose v1 (GPv1) with ZRS redundancy accounts: Use Azure Resource Graph, CLI, Azure Inventory, or the Portal to identify all general purpose v1 (GPv1) with ZRS redundancy storage accounts.
2. Evaluate workloads: To ensure compatibility with GPv2 (most general purpose v1 (GPv1) with ZRS redundancy workloads require no code changes).
3. Plan for pricing changes: Understand the new GPv2 pricing model, which includes per-blob tiering and transaction costs. Use the Azure pricing calculator to estimate costs based on your usage patterns.
4. Migrate to GPv2: Use the Azure portal, CLI, or automation tools to upgrade from GPv1 to GPv2. Learn more about the upgrade process.
5. Validate workloads: Post-migration to ensure functionality and billing accuracy.
6. Monitor usage: After migration, keep an eye on your storage account metrics to identify any unexpected changes in usage patterns or costs.

Identify GPv1 with ZRS accounts using Azure Resource Graph

Azure Resource Graph is a powerful tool for exploring and querying your Azure resources at scale. You can use it to identify all General Purpose v1 (GPv1) and legacy Blob storage accounts in your environment and assess their configurations. This helps you plan your migration to GPv2 more effectively.

Here's an example Azure Resource Graph query to identify all General Purpose v1 (GPv1) storage accounts (kind Storage) and legacy Blob storage accounts (kind BlobStorage) within your subscription that are impacted by the retirement:

Resources
| where type == "microsoft.storage/storageaccounts"
| where sku.name in~ ("Standard_LRS", "Standard_GRS", "Standard_ZRS", "Standard_RAGRS", "Standard_RAGZRS")
| where kind != "StorageV2"
| extend Version = tostring(properties.siteProperties.propertiesid)
| project name, type, tenantId, kind, location, resourceGroup, subscriptionId, managedBy, sku, plan, properties, tags, identity, zones, extendedLocation, Version

[!NOTE] This query identifies both GPv1 accounts (kind Storage) and legacy blob storage accounts (kind BlobStorage) regardless of redundancy. Since both account types are being retired, be sure to review and include all affected accounts in your migration plan.

What happens if you don't migrate by the deadline

After August 31, 2026, you'll no longer be able to manage general purpose v1 (GPv1) with ZRS redundancy accounts. After September 2026, if you don't migrate your GPv1 with ZRS redundancy storage account to general-purpose v2, all existing GPv1 with ZRS redundancy accounts are auto migrated over to a general-purpose v2 account, which may result in higher billing costs. Your decision not to migrate an existing GPv1 with ZRS redundancy account will be construed as consent for Microsoft to migrate the account on your behalf.

Where to get help and support

If you have questions, get answers from community experts in Microsoft Q&A.

If your organization or company has partnered with Microsoft or works with Microsoft representatives, such as cloud solution architects (CSAs) or customer success account managers (CSAMs), contact them for additional resources for migration.

If you have a support plan and you need technical help, create a support request in the Azure portal:

• Search for Help + support in the Azure portal.

Need help?

Learn more about related features and how to migrate:

• Upgrade a storage account to GPv2
• Storage account overview
• Azure Storage pricing