We received a notice to upgrade our Azure Storage and Blob accounts from GPv1 to GPv2 before the October 13 automatic migration deadline. The portal presents this as a simple in-place upgrade with no downtime or data loss, but GPv2 changes the billing model: storage can be cheaper while transaction charges may be significantly higher.
For anyone who has completed the migration, did you simply upgrade the accounts, or did you review Azure Monitor metrics and transaction volumes first? If you analyzed usage, what transaction levels made you reconsider a workload or estimate costs more carefully?
I'm also interested in potential surprises involving Hot versus Cool access tiers, lifecycle policies, redundancy options such as ZRS, or workloads like queues and disaster-recovery replication. Did the migration change your bill noticeably, or was it mostly cost-neutral? I'm trying to decide whether a detailed transaction audit is worthwhile before the automatic migration.
5 Answers
We scripted an analysis of the previous 30 days of transaction metrics, split by transaction type, and estimated the GPv1 and GPv2 cost for each storage account. Most accounts were close to their existing cost, so we upgraded them without redesigning anything. That approach gave us enough confidence without manually inspecting every transaction.
At minimum, check current transaction activity before upgrading. The portal action is simple, but the pricing change is the part that matters. Pay particular attention to high-volume transactions, queue-style workloads, and any account used for replication rather than assuming the migration will have the same cost everywhere.
For many accounts, the upgrade itself really is just selecting the option and saving it. GPv2 also adds useful features such as lifecycle management and, depending on the redundancy configuration, smart tiering. That said, transaction-heavy workloads—especially queue-based ones—can become much more expensive, so I wouldn’t treat every account as risk-free.
We mostly upgraded accounts directly because the remaining GPv1 accounts were old and several could simply be deleted. Many were only generating tiny incidental charges from legacy resources. Checking whether an account is still needed may be more valuable than deeply analyzing every low-usage account.
Our migration was mostly cost-neutral or slightly cheaper. The notable exception was storage used for Azure Site Recovery, where the GPv2 pricing made it more expensive. I’d specifically identify replication and disaster-recovery accounts before making a blanket change.
Queue-heavy usage is the big warning sign. In some cases the transaction bill can be several times higher, so those accounts deserve a closer look before upgrading.