Create an SMB volume for Azure NetApp Files
Azure NetApp Files supports creating volumes using NFS (NFSv3 or NFSv4.1), SMB3, or dual protocol (NFSv3 and SMB, or NFSv4.1 and SMB). A volume's capacity consumption counts against its pool's provisioned capacity.
Before you begin
- You must have already set up a capacity pool. See Create a capacity pool.
- A subnet must be delegated to Azure NetApp Files. See Delegate a subnet to Azure NetApp Files.
Configure Active Directory connections
Before creating an SMB volume, you need to create an Active Directory connection. If you haven't configured Active Directory connections for Azure NetApp files, follow instructions described in Create and manage Active Directory connections.
Add an SMB volume
Click the Volumes blade from the Capacity Pools blade.
Click + Add volume to create a volume.
The Create a Volume window appears.
In the Create a Volume window, click Create and provide information for the following fields under the Basics tab:
Specify the name for the volume that you are creating.
A volume name must be unique within each capacity pool. It must be at least three characters long. The name must begin with a letter. It can contain letters, numbers, underscores ('_'), and hyphens ('-') only.
You can't use
binas the volume name.
Specify the capacity pool where you want the volume to be created.
Specify the amount of logical storage that is allocated to the volume.
The Available quota field shows the amount of unused space in the chosen capacity pool that you can use towards creating a new volume. The size of the new volume must not exceed the available quota.
If the volume is created in a manual QoS capacity pool, specify the throughput you want for the volume.
If the volume is created in an auto QoS capacity pool, the value displayed in this field is (quota x service level throughput).
Specify the Azure virtual network (VNet) from which you want to access the volume.
The VNet you specify must have a subnet delegated to Azure NetApp Files. The Azure NetApp Files service can be accessed only from the same VNet or from a VNet that is in the same region as the volume through VNet peering. You can also access the volume from your on-premises network through Express Route.
Specify the subnet that you want to use for the volume.
The subnet you specify must be delegated to Azure NetApp Files.
If you haven't delegated a subnet, you can click Create new on the Create a Volume page. Then in the Create Subnet page, specify the subnet information, and select Microsoft.NetApp/volumes to delegate the subnet for Azure NetApp Files. In each VNet, only one subnet can be delegated to Azure NetApp Files.
In supported regions, you can specify whether you want to use Basic or Standard network features for the volume. See Configure network features for a volume and Guidelines for Azure NetApp Files network planning for details.
If you want to apply an existing snapshot policy to the volume, click Show advanced section to expand it, specify whether you want to hide the snapshot path, and select a snapshot policy in the pull-down menu.
For information about creating a snapshot policy, see Manage snapshot policies.
Click Protocol and complete the following information:
Select SMB as the protocol type for the volume.
Select your Active Directory connection from the drop-down list.
Specify a unique share name for the volume. This share name is used when you create mount targets. The requirements for the share name are as follows:
- It must be unique within each subnet in the region.
- It must start with an alphabetical character.
- It can contain only letters, numbers, or dashes (
- The length must not exceed 80 characters.
This feature enables encryption for in-flight SMB3 data. SMB clients not using SMB3 encryption will not be able to access this volume. Data at rest is encrypted regardless of this setting.
See SMB encryption for additional information.
The SMB Continuous Availability feature is currently in public preview. You need to submit a waitlist request for accessing the feature through the Azure NetApp Files SMB Continuous Availability Shares Public Preview waitlist submission page. Wait for an official confirmation email from the Azure NetApp Files team before using the Continuous Availability feature.
You should enable Continuous Availability only for SQL Server and FSLogix user profile containers. Using SMB Continuous Availability shares for workloads other than SQL Server and FSLogix user profile containers is not supported. This feature is currently supported on Windows SQL Server. Linux SQL Server is not currently supported. If you are using a non-administrator (domain) account to install SQL Server, ensure that the account has the required security privilege assigned. If the domain account does not have the required security privilege (
SeSecurityPrivilege), and the privilege cannot be set at the domain level, you can grant the privilege to the account by using the Security privilege users field of Active Directory connections. See Create an Active Directory connection.
Click Review + Create to review the volume details. Then click Create to create the SMB volume.
The volume you created appears in the Volumes page.
A volume inherits subscription, resource group, location attributes from its capacity pool. To monitor the volume deployment status, you can use the Notifications tab.
Control access to an SMB volume
Access to an SMB volume is managed through permissions.
NTFS file and folder permissions
You can set permissions for a file or folder by using the Security tab of the object's properties in the Windows SMB client.
- Mount a volume for Windows or Linux virtual machines
- Resource limits for Azure NetApp Files
- Configure ADDS LDAP over TLS for Azure NetApp Files
- Enable Continuous Availability on existing SMB volumes
- SMB encryption
- Troubleshoot volume errors for Azure NetApp Files
- Learn about virtual network integration for Azure services
- Install a new Active Directory forest using Azure CLI