Why is Azure Functions creating V1 Storage Accounts?

Question

We're usually using Azure Functions + SPA (e.g. Angular) for a lot of different projects. That means technically we can host the Functions and the web frontend inside the same Azure Storage Account, as long as it is v2 to support static website hosting.

However, whenever I create an Azure Function App and let it auto-create the storage account it creates a v1 account. Is there any reason why v1 would be better for Functions than v2?

From Microsofts docs:

General-purpose v2 accounts: Basic storage account type for blobs, files, queues, and tables. Recommended for most scenarios using Azure Storage.

General-purpose v1 accounts: Legacy account type for blobs, files, queues, and tables. Use general-purpose v2 accounts instead when possible.

I haven't seen any issues running Azure Functions in a v2 Storage Account so I'm wondering why v1 is still the default option?

question from:https://stackoverflow.com/questions/65881860/why-is-azure-functions-creating-v1-storage-accounts

Answer 1

As far as I know, the General-purpose v1 storage account is the legacy version of Azure storage account and can basically meet most of the needs, so it was the best choice for setting it with Azure Function by default.

As we can see from the official docs:

1. General-purpose v2 storage accounts incorporate all of the functionality of general-purpose v1 and Blob storage accounts.
2. Upgrading a general-purpose v1 or Blob storage account to general-purpose v2 is permanent and cannot be undone.

For better user experience, I think it's not a problem to set GPv1 storage account by default. If you need more functionality about Storage, you could consider upgrade to GPv2.