Proposed Pull Request Change

📄 Document Links

View on GitHub View on Microsoft Learn

--- title: Create a File Share (Microsoft.FileShares) description: Learn to use the Azure portal to deploy an NFS file share with Microsoft.FileShares resource provider. author: khdownie ms.service: azure-file-storage ms.custom: linux-related-content ms.topic: how-to ms.date: 07/14/2026 ms.author: kendownie # Customer intent: "As an IT admin, I want to learn how to deploy an NFS file share with Microsoft.FileShares resource provider." --- # Create an Azure file share with Microsoft.FileShares :heavy_check_mark: **Applies to:** File shares created with the Microsoft.FileShares resource provider :heavy_multiplication_x: **Doesn't apply to:** Classic file shares created with the Microsoft.Storage resource provider The new Microsoft.FileShares resource provider and management model enables you to deploy file shares without creating an Azure storage account. Before you create an Azure file share by using the Microsoft.FileShares resource provider, review the following information to decide if it fits your needs. If you need all the features that Azure Files offers, or you need to use the SMB protocol, or you want HDD (standard) performance, use a [classic file share](create-classic-file-share.md) instead. ## Supported features The Microsoft.FileShares resource provider and management model currently supports only NFS file shares, which require SSD (premium) storage. SSD media provides consistent high performance and low latency, within single-digit milliseconds for most IO operations. The Microsoft.FileShares resource provider only supports the [provisioned v2 billing model](understanding-billing.md#provisioned-v2-model), which allows you to specify how much storage, IOPS, and throughput your file share needs. The amount that you provision determines your total bill. When you create a new file share using the provisioned v2 model, Azure provides a recommendation for how many IOPS and how much throughput you need based on the amount of provisioned storage you specify. You can choose to override these recommendations with your own values. The Microsoft.FileShares resource provider only supports locally redundant storage (LRS) and zone-redundant storage (ZRS). It doesn't support geo-redundant storage. See [Azure Files redundancy](./files-redundancy.md) for more information. To see which features are missing from the Microsoft.FileShares resource provider, see the [comparison chart](files-management-concepts.md#comparing-resource-providers-microsoftstorage-versus-microsoftfileshares). For more information on Azure Files management concepts, see [Azure Files management concepts](files-management-concepts.md). ## Prerequisites This article assumes that you have an Azure subscription. If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn) before you begin. Make sure both Microsoft.FileShares and Microsoft.Storage resource providers are registered for the subscription. The Microsoft.FileShares resource provider is required to create NFS file shares by using the new management model described in this article. To register a resource provider, follow these steps: 1. Sign in to the Azure portal. 1. In the search box, enter *subscriptions*. 1. Select the subscription you want to use to register a resource provider. 1. Under **Settings**, select **Resource providers** to see the list of resource providers. 1. Select the resource provider you want to add and then select **Register**. ## Create a file share (Microsoft.FileShares) You can create a file share with Microsoft.FileShares by using the Azure portal, Azure PowerShell, Azure CLI, or Azure MCP Server. To learn more about using Azure MCP Server, see [Azure Files tools for the Azure MCP Server overview](/azure/developer/azure-mcp-server/tools/azure-file-shares). # [Portal](#tab/azure-portal) To create a file share by using the Azure portal, use the search box at the top of the Azure portal to search for **file share** and select the matching result.  Select **+ Create** to create a new file share.  ### Basics The first tab to complete when creating a file share is labeled **Basics**. It contains the required fields to create a file share.  | Field name | Input type | Values | Meaning | |-|-|-|-| | Subscription | Drop-down list | *Available Azure subscriptions* | The selected subscription in which to deploy the file share. | | Resource group | Drop-down list | *Available resource groups in selected subscription* | The resource group in which to deploy the file share. A resource group is a logical container for organizing Azure resources, including file shares. | | File share name | Text box | -- | The name of the file share must be unique across all existing file share names in Azure. It must be 3 to 63 characters long and can contain only lowercase letters, numbers, and hyphens. The name must start and end with a letter or number. | | Tier | N/A | -- | The media tier for the file share. The Microsoft.FileShares resource provider only supports the SSD media tier. | | Protocol | N/A | -- | File shares support a multitude of access protocols. If you need the SMB protocol, deploy your file share within a storage account. Currently, Microsoft.FileShares supports only the NFS protocol. | | Region | Drop-down list | *Available Azure regions* | The region for the file share to be deployed into. This region can be the region associated with the resource group, or any other available region. | | Provisioned capacity (GiB) | Text box | Integer | Provisioned capacity for the file share, ranging from 32 GiB to 262,144 GiB. | | Redundancy | Drop-down list | <ul><li>Locally redundant storage (LRS)</li><li>Zone-redundant storage (ZRS)</li></ul> | The redundancy choice for the file share. See [Azure Files redundancy](files-redundancy.md) for more information. | | Provisioned IOPS and throughput | Radio button group | <ul><li>Recommended provisioning</li><li>Manually specify IOPS and throughput:<ul><li>Provisioned IOPS</li><li>Provisioned throughput (MiB/sec)</li></ul></li></ul> | The Microsoft.FileShares resource provider only uses the [provisioned v2 billing model](understanding-billing.md#provisioned-v2-model). | ### Advanced The **Advanced** tab is optional and provides more granular settings. You can choose to set up [root squash options](nfs-root-squash.md), require this specific file share to use the encryption in transit setting, or specify a mount name for the file share. Mount name allows you to choose a different name to use to mount the file share. By default, it's the same as the file share name. Customize it if you want a unique mount name. The same rules still apply to the naming policy. See [Naming rules and restrictions for Azure resources](../../azure-resource-manager/management/resource-name-rules.md).  ### Networking NFS file shares require network-level security configurations to control access. Currently, two options are available for establishing network-level security configurations: private endpoint and service endpoint. Private endpoint gives your file share a private, static IP address within your virtual network, preventing connectivity interruptions from dynamic IP address changes. Traffic to your file share stays within peered virtual networks, including those in other regions and on-premises. To learn more, see [What is a private endpoint](../../private-link/private-endpoint-overview.md). If you don't require a static IP address, you can enable a service endpoint for Azure Files within the virtual network. A service endpoint configures the file share to allow access only from specific subnets. The allowed subnets can belong to a virtual network in the same subscription or a different subscription, including those that belong to a different Microsoft Entra tenant. There's no extra charge for using service endpoints. To learn more, see [Azure virtual network service endpoints](../../virtual-network/virtual-network-service-endpoints-overview.md). The **Networking** tab is optional, and allows you to set up both service and private endpoint. A virtual network is required if you intend to set up private endpoint while creating the file share. You can also set up networking configurations after you create the file share. With public endpoints access enabled, and public endpoint access scope enabled from selected virtual networks, you can create or choose an existing virtual network for the service endpoint connection to this file share. If you disable public endpoint access, the service endpoint is disabled for this file share. If you choose public endpoint access scope as enable (no network restrictions), you need to set up the virtual network after you create the file share.  For private endpoint configurations, each file share has its own private endpoint. To get started, follow these steps: 1. Select **+ Create private endpoint**. Leave **Subscription** and **Resource group** the same. Choose the same location as the virtual network and desired name for the private endpoint. Choose FileShare for target sub-resource. 1. Choose the desired virtual network and subnet setting. Make sure you select the **Enable Private DNS Integration** checkbox. 1. Select **Add**.  ### Tags Tags are name/value pairs that you use to categorize resources and view consolidated billing by applying the same tag to multiple resources and resource groups. These tags are optional, and you can apply them after you create the file share. ### Review + create The final step to create the file share is to select the **Create** button on the **Review + create** tab. This button isn't available until you complete all the required fields. # [PowerShell](#tab/powershell) To create a file share by using PowerShell, run the following commands. Replace the variables with your values. ```powershell # To learn more about the Az.FileShare module, see https://www.powershellgallery.com/packages/Az.FileShare/1.0.0 Install-Module -Name Az.FileShare -Repository PSGallery -RequiredVersion 1.0.0 # To learn more about the parameters for New-AzFileShare, use command # Get-Help New-AzFileShare $shareName = "<your-file-share-name>" $resourceGroup = "<your-resource-group-name>" $region = "<intended-region-for-deployment>" # The provisioned storage size of the share in GiB. Valid range is 32 to 262,144. $provisionedStorageGib = 1024 # If you don't specify -ProvisionedThroughputMiBPerSec and -ProvisionedIoPerSec, the deployment uses the recommended provisioning. $provisionedIops = 3500 $provisionedThroughput = 200 New-AzFileShare ` -ResourceName $shareName ` -ResourceGroupName $resourceGroup ` -Location $region ` -Protocol NFS ` -ProvisionedStorageGiB $provisionedStorageGib # -ProvisionedIoPerSec $provisionedIops ` # -ProvisionedThroughputMiBPerSec $provisionedThroughput ``` # [Azure CLI](#tab/azure-cli) To create a file share by using Azure CLI, run the following commands. Replace the variables with your values. ```bash # If you previously installed the preview extension, remove it first: # az extension remove --name fileshares # Install the fileshare extension az extension add --name fileshare # Specify your values shareName="<your-file-share-name>" resourceGroup="<your-resource-group-name>" region="<intended-region-for-deployment>" # The provisioned storage size of the share in GiB. Valid range is 32 to 262,144. provisionedStorageGiB=1024 # If you don't specify provisioned IOPS and throughput, the deployment uses the recommended provisioning. # provisionedIops=3000 # provisionedThroughput=125 # Create the file share. Redundancy supports "Local" and "Zone". az fileshare create \ --name $shareName \ --resource-group $resourceGroup \ --location $region \ --provisioned-storage-gib $provisionedStorageGiB \ --protocol NFS \ --redundancy Local # --provisioned-iops $provisionedIops \ # --provisioned-throughput-mib $provisionedThroughput ``` --- ## See also - [Create a Linux virtual machine](/azure/virtual-machines/linux/quick-create-portal?tabs=ubuntu) - [Mount an NFS file share on Linux](storage-files-how-to-mount-nfs-shares.md) - [Modify a file share](modify-file-share.md)