Uprade from storage account from v1 to v2

Tony Wetzler 40 Reputation points
2026-07-31T15:06:18.4433333+00:00

I have to upgrade a storage account from v1 to v2. What are the steps involved to migrate it

Azure Storage
Azure Storage

Globally unique resources that provide access to data management services and serve as the parent namespace for the services.

0 comments No comments

Answer accepted by question author
Jose Benjamin Solis Nolasco 12,201 Reputation points Volunteer Moderator
2026-07-31T18:57:39.3066667+00:00

Welcome to Microsoft Q&A

Hello @Tony Wetzler , I hope you are doing well.

If the storage account is General-purpose v1 (GPv1), you can upgrade it directly to General-purpose v2 (GPv2). The upgrade is performed in place, so you don't need to migrate the data to a new storage account.

Azure portal

Open the Storage account in the Azure portal.

Go to Settings > Configuration.

Under Account kind, select Upgrade.

Review the upgrade information.

Select the default blob access tier, Hot or Cool.

Enter the storage account name to confirm.

Select Upgrade.

The upgrade is permanent, so the account cannot be downgraded back to GPv1.

Azure CLI

You can also perform the upgrade with:

az storage account update \
  --resource-group <resource-group> \
  --name <storage-account> \
  --set kind=StorageV2 \
  --access-tier Hot

Replace Hot with Cool if that is the appropriate default access tier for your workload.

Microsoft has announced the retirement of GPv1, so it is recommended to complete the upgrade before the applicable retirement deadline.

Reference:

https://learn.microsoft.com/azure/storage/common/storage-account-upgrade

If my answer helped you, please consider marking it as accepted. This helps others in the community find similar solutions.

Was this answer helpful?

1 person found this answer helpful.

1 additional answer

Sort by: Newest
  1. AI answer

    2026-07-31T15:06:33.5566667+00:00

    To upgrade an Azure Storage account from general-purpose v1 (GPv1) or Blob storage to general-purpose v2 (GPv2):

    1. Review the impact before upgrading
      • The upgrade is in-place, non-disruptive, and has no downtime or data loss.
      • The upgrade is permanent. A GPv1 account cannot be downgraded back to GPv1, and a Blob storage account cannot be downgraded back to Blob storage.
      • GPv2 uses a different pricing model, so review expected billing impact before upgrading.
      • Choose the default blob access tier during upgrade: Hot or Cool. If not specified, the account is upgraded to Hot by default.
    2. Upgrade in the Azure portal
      • Sign in to the Azure portal.
      • Open the storage account.
      • Go to Settings > Configuration.
      • Under Account kind, select Upgrade.
      • In Confirm upgrade, enter the storage account name.
      • Select Upgrade.
    3. Upgrade with Azure PowerShell
      • Use the latest Az.Storage module.
      • Run:
         Set-AzStorageAccount -ResourceGroupName <resource-group> -Name <storage-account> -UpgradeToStorageV2 -AccessTier <Hot/Cool>
      
    4. Upgrade with Azure CLI
      • Use the latest Azure CLI.
      • Run:
         az storage account update -g <resource-group> -n <storage-account> --set kind=StorageV2 --access-tier=<Hot/Cool>
      
    5. Validate after upgrade
      • Confirm the account kind is now StorageV2.
      • Validate application behavior, especially anything that depends on account kind or pricing/tier behavior.
      • Test in a staging environment before upgrading production if the storage account is used by applications.

    Important notes:

    • Upgrading a v1 storage account to GPv2 is free.
    • Changing the access tier after the upgrade can affect billing, so setting the intended tier during the upgrade is recommended.
    • GPv1 accounts retire on October 13, 2026. Existing GPv1 accounts must be upgraded by then to avoid service disruption.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.