You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/storage/files/create-file-share.md
+21-20Lines changed: 21 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,22 +5,22 @@ author: khdownie
5
5
ms.service: azure-file-storage
6
6
ms.custom: linux-related-content
7
7
ms.topic: how-to
8
-
ms.date: 09/18/2025
8
+
ms.date: 10/08/2025
9
9
ms.author: kendownie
10
10
# Customer intent: "As an IT admin, I want to learn how to deploy an NFS file share with Microsoft.FileShares resource provider (preview)."
11
11
---
12
12
13
13
# Create an Azure file share with Microsoft.FileShares (preview)
14
14
15
-
Before you create an Azure file share with the new Microsoft.FileShares resource provider, you need to answer two questions about how you want to use it:
15
+
The new Microsoft.FileShares resource provider (preview) and management model allows you to deploy file shares without creating an Azure storage account. Before you create an Azure file share with the Microsoft.FileShares resource provider, review the following to decide if it's the right fit for your needs. If you need all the features that Azure Files offers, or you need to use the SMB protocol, or want HDD (standard) performance, use a [classic file share](create-classic-file-share.md) instead.
16
16
17
-
-**Is file share (Microsoft.FileShares) the right fit for me?**
18
-
**Microsoft.FileShares is currently in preview.** The new resource provider and management model is current only available for 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. Using the Microsoft.FileShares resource provider allows you to deploy file shares without creating an Azure storage account. The preview only supports the provisioned v2 billing 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, we provide a recommendation for how many IOPS and how much throughput you need based on the amount of provisioned storage you specify. Depending on your requirements, you might find that you require more or less IOPS or throughput, and you can optionally override these recommendations with your own values. To learn more, see [Understanding the provisioned v2 billing model](understanding-billing.md#provisioned-v2-model). If you need all the features that Azure Files offers, or you need to use the SMB protocol, or want HDD (standard) performance, use a [classic file share](create-classic-file-share.md) instead.
17
+
- The Microsoft.FileShares resource provider and management model is current only available for 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.
19
18
20
-
-**What are the redundancy requirements for file share (Microsoft.FileShares)?**
21
-
The Microsoft.FileShares preview only supports locally-redundant storage (LRS) and zone-redundant storage (ZRS). See [Azure Files redundancy](./files-redundancy.md) for more information.
19
+
- The preview 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, we provide a recommendation for how many IOPS and how much throughput you need based on the amount of provisioned storage you specify. Depending on your requirements, you can choose to override these recommendations with your own values.
22
20
23
-
For more information on Azure Files management concepts, see [Planning for an Azure Files deployment](storage-files-planning.md#management-concepts).
21
+
- The Microsoft.FileShares preview only supports locally-redundant storage (LRS) and zone-redundant storage (ZRS). See [Azure Files redundancy](./files-redundancy.md) for more information.
22
+
23
+
For more information on Azure Files management concepts, see [Plan for an Azure Files deployment](storage-files-planning.md#management-concepts).
24
24
25
25
## Applies to
26
26
@@ -43,13 +43,13 @@ For more information on Azure Files management concepts, see [Planning for an Az
43
43
44
44
This article assumes that you have an Azure subscription. If you don't have an Azure subscription, then create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
45
45
46
-
Please make sure both "Microsoft.FileShares" and "Microsoft.Storage" resource providers are registered for the subscription.
47
-
To register a resource provider:
46
+
Make sure both "Microsoft.FileShares" and "Microsoft.Storage" resource providers are registered for the subscription. To register a resource provider, follow these steps.
47
+
48
48
1. Sign in to Azure portal.
49
-
2. In the search box, enter subscriptions.
50
-
3. Select the subscription you want to use to register a resource provider.
51
-
4. To see the list of resource providers, under Settings select Resource providers.
52
-
5. To register a resource provider, select the resource provider you intend to add and then select Register.
49
+
1. In the search box, enter *subscriptions*.
50
+
1. Select the subscription you want to use to register a resource provider.
51
+
1. To see the list of resource providers, under **Settings**, select **Resource providers**.
52
+
1. Select the resource provider you intend to add and then select **Register**.
53
53
54
54
## Create a file share (Microsoft.FileShares)
55
55
@@ -83,20 +83,21 @@ The first tab to complete creating a file share is labeled **Basics**, which con
83
83
| Region | Drop-down list |*Available Azure regions*| The region for the file share to be deployed into. This can be the region associated with the resource group, or any other available region. |
84
84
| Provisioned capacity (GiB) | Text box | Integer | Provisioned capacity for the file share, ranging from 32 GiB to 262144 GiB. |
85
85
| Redundancy | Drop-down list | - Locally redundant storage (LRS) <br> - Geo-redundant storage (GRS) | The redundancy choice for the file share. See [Azure Files redundancy](files-redundancy.md) for more information. |
86
-
| Provisioned IOPS and throughput| Radio button group | - Recommended provisioning <br> - Manually specify IOPS and throughput: <br> - Provisioned IOPS <br> - Provisioned throughput (MiB/sec) | The Microsoft.FileShares preview only uses the provisioned v2 SSD billing model. See [Understanding billing](understanding-billing.md#provisioned-v2-model). |
87
-
86
+
| Provisioned IOPS and throughput| Radio button group | - Recommended provisioning <br> - Manually specify IOPS and throughput: <br> - Provisioned IOPS <br> - Provisioned throughput (MiB/sec) | The Microsoft.FileShares preview only uses the [provisioned v2 billing model](understanding-billing.md#provisioned-v2-model). |
88
87
89
88
### Advanced
90
89
91
-
The **Advanced** tab is optional, but provides more granular settings for the file share. Currently you can choose to set up root squash options or specify a mount name for the file share. See [nfs root squash options](./nfs-root-squash.md) to learn more. 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) to learn more.
90
+
The **Advanced** tab is optional and provides more granular settings. You can choose to set up [root squash options](nfs-root-squash.md) 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).
92
91
93
92
94
93
95
94
### Networking
96
95
97
-
Using the NFS protocol for a file share requires network-level security configurations. Currently there are two options for establishing networking-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. See [What is a private endpoint](../../private-link/private-endpoint-overview.md) to learn more. Currently, you can set up a private endpoint after you create the file share, for region support on private endpoint, see [Plan to deploy Azure Files](./storage-files-planning.md#file-shares-microsoftfileshares).
96
+
Using the NFS protocol for a file share requires network-level security configurations. There are two options for establishing networking-level security configurations: [Private endpoint](../../private-link/private-endpoint-overview.md) and [service endpoint](../../virtual-network/virtual-network-service-endpoints-overview.md).
97
+
98
+
A 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. You can set up a private endpoint after you create the file share. For region support on private endpoints for Microsoft.Fileshares, see [Plan to deploy Azure Files](./storage-files-planning.md#file-shares-microsoftfileshares).
98
99
99
-
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 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. See [Azure virtual network service endpoints](../../virtual-network/virtual-network-service-endpoints-overview.md) to learn more. You can create or choose an existing virtual network for service endpoint purpose in the networking tab during the create flow.
100
+
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 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. You can create or choose an existing virtual network for service endpoint purpose in the networking tab during the create flow.
100
101
101
102
### Tags
102
103
@@ -106,9 +107,9 @@ Tags are name/value pairs that enable you to categorize resources and view conso
106
107
107
108
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.
108
109
109
-
### Set up a private endpoint
110
+
### Set up a private endpoint
110
111
111
-
1. After the file share is created, search private endpoint in the search bar, and then click on create button.
112
+
1. After the file share is created, search for private endpoint in the search bar, and then click on create button.
112
113
1. Leave **Subscription** and **Resource group** the same. Under **Instance**, provide a name and select a region for the new private endpoint. Your private endpoint must be in the same region as your virtual network, so use the same region as you specified when creating the VM. When all the fields are complete, select **Next: Resource**.
113
114
114
115
![prmerger-automator[bot]](https://avatars.githubusercontent.com/u/22479449?v=4&size=40){kind=avatar}
0 commit comments