storage upgrade from GPv1 to GPv2 - Sku invalid

Question

Hi there,

Getting this error: Failed to upgrade storage account '....storage....'. Error: Values for request parameters are invalid: sku.

Tried the diagnostic tool and said it had these errors:

"Account Kind Storage is not supported."

"Account Kind BlobOnly is not supported."

No idea why .. all my other storage accounts migrated just fine.

E

Answer 1

Hello Eric Klimuk

It appears you’re encountering the “invalid sku” error because Azure is now blocking the legacy GPv1 (“Storage”) and Blob-Only (“BlobOnly”) account types due to their upcoming retirement. This is why the diagnostic marks your account type as “not supported.”

However, you can still perform an in-place upgrade from GPv1 or BlobStorage to GPv2 (StorageV2) without any disruption. Here’s how to proceed and some important considerations:

Please try to upgrade GPv2 first, please check the commands to upgrade:

az storage account update -g <resource-group> -n <storage-account> --set kind=StorageV2 --access-tier=<Hot/Cool>

Set-AzStorageAccount -ResourceGroupName <resource-group> -Name <storage-account> -UpgradeToStorageV2 -AccessTier <Hot/Cool>

Check the reference document: Upgrade to a general-purpose v2 storage account

• If your GPv1 account uses ZRS and your region doesn’t support the new ZRSv2, you’ll get flagged as “ineligible to upgrade.” In that case, switch replication to LRS or GRS first. See “Regions without ZRSv2 support.”
• Make sure there are no active operations or management locks on the account (check Activity Log and Settings → Locks).
• If you’re using hierarchical namespace (Data Lake Gen2) or encryption scopes, disable those unsupported features, save, then re-enable after the upgrade if needed.

Check the below documents for more understanding:
https://learn.microsoft.com/en-us/azure/storage/common/general-purpose-version-1-zone-redundant-storage-migration-overview#regions-without-zrs-support

https://learn.microsoft.com/en-us/rest/api/storagerp/srp_error_codes_update_storage_account

---

I hope the above answer helps you! Please let us know if you have any further questions.

Please don't forget to "upvote" where the information provided will help you, this can be beneficial to other members of the community.

Answer 2

Hi Eric Klimuk,

Thanks for reaching out in Microsoft Q&A forum,

"Account Kind Storage is not supported."

"Account Kind BlobOnly is not supported."

Your storage account cannot be upgraded due to its legacy "Storage" (GPv1) or "BlobOnly" (BlobStorage) kind, which blocks SKU changes as noted in the diagnostics.

Unlike your other accounts (likely already StorageV2), these older kinds lack direct upgrade paths for certain SKUs like Premium or specific redundancies.

Run this CLI command to confirm:

az storage account show --name <account-name> --resource-group <rg> --query "{kind:kind, sku:sku.name}" 

Expected output for your issue: {"kind": "Storage"} or {"kind": "BlobOnly"}.

Upgrade to GPv2 first via CLI (safe, in-place):

az storage account update --name <account-name> --resource-group <rg> --set kind=StorageV2 

Then retry SKU change:

az storage account update --name <account-name> --resource-group <rg> --sku <new-sku>

(e.g., Standard_GRS).

Fix for BlobStorage (BlobOnly)

No direct upgrade recreates:

1. Back up data: azcopy copy 'https://<old>.blob.core.windows.net/<container>?<SAS>' 'https://<new>.blob.core.windows.net/<container>?<SAS>' --recursive
2. Create new: az storage account create -g <rg> -n <newname> --kind StorageV2 --sku <desired-sku> --location <region>
3. Update apps to point to new account.

Why It Fails:
Legacy kinds enforce rigid SKU rules; GPv2 offers full flexibility. Recreation ensures compatibility without data loss. Share the CLI output for tailored steps.

Reference:

• Upgrade to a general-purpose v2 storage account - Azure Storage | Microsoft Learn
• Error Codes for Update Storage Account (Azure Storage) | Microsoft Learn

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.