The retirement of General-Purpose v1 (GPv1) storage accounts and Legacy Blob storage accounts (Blob Only) is October 13, 2026

Hi Haghunandan H (Az Admin),

Thanks for reaching out in Microsoft Q&A forum,

Based on Microsoft's official documentation, here are clear answers to your questions about upgrading your storage accounts.

Will there be any data loss or inconsistency by upgrading GPv2 storage accounts ?

No. The upgrade is safe and won't delete or move your data unexpectedly. All blobs, containers, and metadata remain intact during the process.

Will the cost remain same after the upgrade to GPv2, or will it reduce the cost or increase the cost ?

It may change. GPv2 offers the lowest per-gigabyte capacity prices in Azure, but transaction costs may vary:

• Storage costs: Potentially lower (GPv2 has the best capacity pricing)
• Transaction costs: Could increase if your Commvault backups involve high read/write operations
• New features: Lifecycle management can help optimize costs for varied-size storage

Right now blob storages are configured with cool tier. During the upgrade can we change access tier from Cool to cold ?

Yes. You can specify Cool tier during upgrade. However, Cold tier is available at the blob level (per-blob tiering) in GPv2 after upgrade, not as a default account tier during the upgrade itself. You can transition individual blobs to Cold later using lifecycle management policies.

Will there be any data loss or inconsistency by changing from Cool to Cold during the upgrade ?

No data loss. Moving blobs between tiers is non-disruptive and doesn't delete your data.

Will there be any charges for changing from Cool to Cold during the upgrade ?

Yes. You'll incur:

• Write operation charges at the Cold tier's rate when moving blobs there
• Early deletion fees if you move data out of Cold before 90 days (minimum retention period)
• Cold tier has lower storage costs but higher retrieval costs compared to Cool

During the upgrade in case if we face any issues, How do get support from Microsoft?

Create a support ticket via the Azure Support Portal:

• Service type: Storage Account Management
• Resource: Your storage account
• Problem type: Upgrade or change account type, tier or replication

Problem subtype: Upgrade to general purpose v2 storage account

Is there any precautions need to be taken (Like taking backup/snapshot) before the upgrade to GPv2

1. Verify your current storage account type in Azure Portal
2. Document data size, transaction volume, and redundancy type for each of your 9 accounts
3. Test first: Upgrade one smaller account before the 670 TB one
4. Review Azure Monitor metrics for access patterns (Ingress/Egress)
5. Check for any unsupported features (validation step will report these)

While backups aren't strictly required (upgrade is safe), for critical data like Commvault backups, some organizations create backup storage accounts as an extra precaution.

Is there any way we can revert it back to blob storage if there is any issue after the upgrade ?

No. Once you upgrade to GPv2, you cannot downgrade back to legacy blob storage. The migration is permanent.

However, since the upgrade is non-disruptive with no data loss, you typically won't need to revert.

Will there be any downtime of the storage resource during the upgrade ?

No downtime. The upgrade is non-disruptive:

• You can access data continuously with no loss of durability or availability
• Azure Storage SLA is maintained during migration
• Service endpoints, access keys, and SAS tokens remain unchanged
• Most applications continue working without changes

Official Microsoft Documentation

• Legacy Blob Storage account retirement FAQ – https://learn.microsoft.com/en-us/azure/storage/common/legacy-blob-storage-account-migration-frequently-asked-questions
• Upgrade to a general-purpose v2 storage account – https://learn.microsoft.com/en-us/azure/storage/common/storage-account-upgrade
• Overview of legacy blob storage account retirement – https://learn.microsoft.com/en-us/azure/storage/common/legacy-blob-storage-account-migration-overview
• Azure Storage documentation hub – https://learn.microsoft.com/en-us/azure/storage/

Kindly let us know if the above helps or you need further assistance on this issue.

Please do not forget to and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.