An error is on when create an account for Azure blobs storage

Hello Eric Miyahara

We understand you’re experiencing issues creating an Azure Blob Storage account, even though all required details appear correct. This problem is not caused by your local machine or system.

Check in the activity logs and verify the error message while failing the operation time.

Usually, this is due to configuration or permission settings at the Azure subscription level. Possible reasons include missing or insufficient permissions, locks on the subscription or resource group, Azure policy restrictions, or the Microsoft.Storage resource provider not being registered. Sometimes, browser cache or portal issues can also result in misleading validation messages.

To address this, please check your subscription permissions, ensure there are no locks or policy constraints, and confirm the Microsoft.Storage resource provider is registered.

Please check the below document to create account with CLI and PowerShell commands:

https://dotnet.territoriali.olinfo.it/en-us/azure/storage/common/storage-account-create?tabs=azure-cli

And also check the below reference document:

https://dotnet.territoriali.olinfo.it/en-us/azure/role-based-access-control/deny-assignments?tabs=azure-portal

https://dotnet.territoriali.olinfo.it/en-us/azure/azure-resource-manager/management/lock-resources?tabs=json#configure-locks

https://dotnet.territoriali.olinfo.it/en-us/answers/questions/957643/unable-to-create-storage-account-error-loading-the

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.

Hi @ Eric Miyahara,

Welcome to Microsoft Q&A Platform.

It sounds like you’re running into a generic “unable to create storage account” error when you try to provision an Azure Blob Storage account. That usually comes down to one of a few common issues, name conflicts, subscription or resource-group locks, missing permissions or policies, or even the Microsoft.Storage provider not being registered.

Here’s a quick rundown of what you can try:

Run the built-in diagnostic

• In the Azure portal, go to Create a resource > Storage account and click Diagnose and solve problems.
• Let the “We are running a quick check on the storage account” insight complete and see if it flags anything.

Check for name conflicts:

• Storage account names must be globally unique. If the name is taken, you’ll get a StorageAccountAlreadyTaken error.
• Try a different name or use the name-conflict checker.

Verify resource locks:

• Make sure there are no Delete or Read-only locks on your subscription or resource group that might block new resource creation.
• Remove any locks via the resource locks documentation.

Confirm you have the right permissions

• Ensure your user or service principal has at least Contributor on the target subscription or resource group.
• Check for any deny assignments that could be blocking creation: https://dotnet.territoriali.olinfo.it/azure/role-based-access-control/deny-assignments-portal

Register the Microsoft. Storage provider

• If the Storage resource provider isn’t registered, you can’t create any storage accounts.
• In PowerShell or Azure CLI: az provider register --namespace Microsoft.Storage More details: https://dotnet.territoriali.olinfo.it/azure/azure-resource-manager/management/azure-services-resource-providers

Try CLI or PowerShell:

• Sometimes the portal masks the underlying error. create using the Azure CLI: https://dotnet.territoriali.olinfo.it/azure/storage/common/storage-account-create?tabs=azure-cli

Pleaseand “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

The error is not caused by the local machine. Creating an Azure Storage account for Blob Storage is controlled entirely by the Azure subscription, tenant, and the values entered in the create form.

Use the Azure portal creation flow and verify the required fields step by step:

1. Sign in to the Azure portal and go to Storage accounts → Create.
2. On the Basics tab, make sure:
   • Subscription: A valid, active subscription is selected.
   • Resource group: Either select an existing one or create a new one.
   • Storage account name: 3–24 characters, only lowercase letters and numbers, globally unique.
   • Region: Choose a valid region; some SKUs are not supported in all locations.
   • Performance and Redundancy: Choose a supported combination (for example, Standard + Standard_LRS for a general-purpose v2 account).
3. If using advanced options (encryption with customer-managed keys, special redundancy, or access tiers), ensure they are valid for the chosen account type and region. Invalid combinations can cause BadRequest (400) errors such as:
   • AccountTypeNotSupportedInLocation – SKU not supported in that region.
   • InvalidAccessTier – access tier not allowed for that account kind.
   • InvalidAccountType – invalid SKU.
   • Key Vault–related errors if a customer-managed key is misconfigured.
4. Go to Review + create and check the validation message. If validation fails, the portal will indicate which setting is invalid; adjust that field and retry.

If the storage account name was used previously in another subscription/tenant and recently deleted, creation can be blocked for security reasons. In that case, open an Azure Support Request and choose:

• Problem type: Create new storage account
• Problem subtype: Failure(s) during new account creation Include the storage account name and approximate failure time.

If the portal still reports that the environment cannot create an account even with valid values, the subscription or tenant may be blocked or inactive. That must be resolved by Azure Support via a support request from the portal.

References:

• Create an Azure storage account
• Error Codes for Create Storage Account
• Resolve errors for storage account names