How to fix File Share deployment failure "The resource namespace 'Microsoft.FileShares' is invalid"

Bill W 0

Trying to create a file share I am getting a deployment failure with the error "The resource namespace 'Microsoft.FileShares' is invalid."

Keshavulu Dasari 1,830 Reputation points Microsoft Vendor

2024-11-11T22:24:26.6666667+00:00
Hi Bill W,
Welcome to Microsoft Q&A Forum. Thanks for posting you query here!
The issue with the resource provider registration in Azure. The error “The resource namespace ‘Microsoft.FileShares’ is invalid” typically indicates that the resource provider for file shares isn’t registered in your subscription.
to resolve this issue:

Check Resource Provider Registration:

Go to the Azure portal.

Navigate to your subscription.

Under Settings, select Resource providers.

Search for Microsoft.Storage and ensure it is registered. If it is not, click on Register.

Register via Azure CLI:

Open Azure Cloud Shell or your local terminal with Azure CLI installed.

Run the following command to register the resource provider
az provider register --namespace Microsoft.Storage
Verify Registration:

After registering, you can verify the status with:
az provider show --namespace Microsoft.Storage
If the issue persists after following these steps, it might be helpful to check for any specific deployment errors or additional details in the Azure Activity Log
https://learn.microsoft.com/en-us/azure/azure-resource-manager/troubleshooting/common-deployment-errors

If you have any other questions or are still running into more issues, let me know in the "comments" and I would be happy to help you
Bill W 0 Reputation points

2024-11-11T22:57:13.32+00:00

Thanks you for answering. Your suggestion did not work, but I am trying to create this File Share in a Resource Group, rather than in a Storage Account. Could it be that is not allowed? My real goal here is to create a file share with a quota of less that 100 TiB. It seems it can't do that because my storage account is created as a "premium" storage account and I cannot find any way to recreate it as a "standard" storage account. Can you help me with that?
Keshavulu Dasari 1,830 Reputation points Microsoft Vendor

2024-11-11T23:13:18.45+00:00

Hi Bill W,
If you have any other questions or are still running into more issues, let me know in the "comments" and I would be happy to help you
Bill W 0 Reputation points

2024-11-11T23:32:36.4533333+00:00

Thank you, but that does not solve the problem. Even though I created a Standard Storage Account, Large File Shares are enabled by default and it cannot be disabled. Please see attached screenshot. Any other possibilities?
Keshavulu Dasari 1,830 Reputation points Microsoft Vendor

2024-11-12T01:51:20.4933333+00:00
@Bill W,
Creating a File Share in a Resource Group: Azure File Shares must be created within a Storage Account, not directly in a Resource Group
https://learn.microsoft.com/en-us/azure/storage/files/storage-how-to-create-file-share?tabs=azure-portal

This is likely why you're seeing the error "The resource namespace 'Microsoft.FileShares' is invalid."

Quota of Less Than 100 TiB: As your screenshot indicates, large file shares are enabled by default on all storage accounts and cannot be disabled. This means that even if you create a Standard Storage Account, it will still support large file shares by default.

Solutions:

Create a New Storage Account with Standard Performance: Ensure that you select the correct performance tier when creating the storage account. You can choose between Standard and Premium performance tiers. For a quota of less than 100 TiB, you should select the Standard performance tier.

Use Azure CLI or PowerShell: Sometimes, using the Azure CLI or PowerShell can give you more control over the creation process. Here’s a quick example of how you can create a Standard Storage Account using Azure CLI:

az storage account create --name mystorageaccount --resource-group myResourceGroup --location eastus --sku Standard_LRS

Check Storage Account Settings: Double-check the settings of your existing storage account to ensure it is set to the Standard performance tier. If it is already set to Premium, you might need to create a new storage account with the Standard tier.

For more information, please refer the below link it might be help:
https://learn.microsoft.com/en-us/answers/questions/1659730/how-to-expand-azure-file-share-max-quota-size
Keshavulu Dasari 1,830 Reputation points Microsoft Vendor

2024-11-12T17:51:09.5733333+00:00

Hi Bill W,
If you have any other questions or are still running into more issues, let me know in the "comments" and I would be happy to help you
Bill W 0 Reputation points

2024-11-12T19:35:33.31+00:00

Thank you Keshavula. I have tried your suggestion, but as the screenshot indicates, large file shares are enabled by default on all storage accounts and cannot be disabled. This means that even with a standard storage account, I cannot create a file share with a quota less than 100Tib. It is unusual that this restriction is not explained better in the documentation.
Keshavulu Dasari 1,830 Reputation points Microsoft Vendor

2024-11-12T20:07:06.94+00:00
Hi Bill W,
The default enabling of large file shares can indeed be limiting in certain scenarios. Few additional options you might consider:
Use General Purpose v1 Storage Accounts:

General Purpose v1 (GPv1) storage accounts do not support large file shares by default. You can create a GPv1 storage account and then create a file share with a smaller quota.

you can create a GPv1 storage account using Azure CLI:

az storage account create \ --name <your_storage_account_name> \ --resource-group <your_resource_group_name> \ --location <your_location> \ --sku Standard_LRS \ --kind Storage

Depending on your use case, you might explore other Azure storage options like Blob Storage, which can be configured with different tiers and quotas, providing feedback directly to Microsoft through the Azure portal can help improve the documentation and potentially influence future updates to the service.

If you have any other questions or are still running into more issues, let me know in the "comments" and I would be happy to help you
Keshavulu Dasari 1,830 Reputation points Microsoft Vendor

2024-11-14T17:57:14.56+00:00

Hi Bill W,
If you have any other questions or are still running into more issues, let me know in the "comments" and I would be happy to help you
Bill W 0 Reputation points

2024-11-14T21:31:28.8533333+00:00

Thanks for your help, but it is impossible to create a smaller file share with any kind of storage account, and my ISP is blocking access to port 445 with no way around that, so I am giving up on the file share idea and trying Azure SQL Server next.

1 answer

Keshavulu Dasari 1,830 Reputation points Microsoft Vendor

2024-11-15T00:00:07.56+00:00

Hi Bill W,
Moving to Azure SQL Server is a great alternative for managing your data,You can manage your database directly from the Azure portal or using SQL queries through your preferred SQL client.

For information, you can refer to the Microsoft Learn documentation

If you have any other questions or are still running into more issues, let me know in the "comments" and I would be happy to help you
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

How to fix File Share deployment failure "The resource namespace 'Microsoft.FileShares' is invalid"

1 answer

Your answer