Merge pull request #91554 from b-juche/live-update-10-12-NFSv41

NFSv41 UI and considerations

Author: ShannonLeavitt

articles/azure-netapp-files/azure-netapp-files-create-volumes-smb.md

@@ -13,7 +13,7 @@ ms.workload: storage
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: conceptual
-ms.date: 10/02/2019
+ms.date: 10/12/2019
 ms.author: b-juche
 ---
 # Create an SMB volume for Azure NetApp Files
@@ -107,6 +107,9 @@ A subnet must be delegated to Azure NetApp Files.
 
     ![Active Directory Connections](../media/azure-netapp-files/azure-netapp-files-active-directory-connections-created.png)
 
+> [!NOTE] 
+> You can edit the username and password fields after saving the Active Directory connection. No other values can be edited after saving the connection. If you need to change any other values, you must first delete any deployed SMB volumes, then delete and re-create the Active Directory connection.
+
 ## Add an SMB volume
 
 1. Click the **Volumes** blade from the Capacity Pools blade. 

articles/azure-netapp-files/azure-netapp-files-create-volumes.md

@@ -13,19 +13,41 @@ ms.workload: storage
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: conceptual
-ms.date: 7/9/2019
+ms.date: 10/12/2019
 ms.author: b-juche
 ---
 # Create an NFS volume for Azure NetApp Files
 
-Azure NetApp Files supports NFS and SMBv3 volumes. A volume's capacity consumption counts against its pool's provisioned capacity. This article shows you how to create an NFS volume. If you want to create an SMB volume, see [Create an SMB volume for Azure NetApp Files](azure-netapp-files-create-volumes-smb.md). 
+Azure NetApp Files supports NFS (NFSv3 and NFSv4.1) and SMBv3 volumes. A volume's capacity consumption counts against its pool's provisioned capacity. This article shows you how to create an NFS volume. If you want to create an SMB volume, see [Create an SMB volume for Azure NetApp Files](azure-netapp-files-create-volumes-smb.md). 
 
 ## Before you begin 
 You must have already set up a capacity pool.   
 [Set up a capacity pool](azure-netapp-files-set-up-capacity-pool.md)   
 A subnet must be delegated to Azure NetApp Files.  
 [Delegate a subnet to Azure NetApp Files](azure-netapp-files-delegate-subnet.md)
 
+## Considerations 
+
+* Deciding which NFS version to use  
+  NFSv3 can handle a wide variety of use cases and is commonly deployed in most enterprise applications. You should validate what version (NFSv3 or NFSv4.1) your application requires and create your volume using the appropriate version. For example, if you use [Apache ActiveMQ](https://activemq.apache.org/shared-file-system-master-slave), file locking with NFSv4.1 is recommended over NFSv3. 
+
+> [!IMPORTANT] 
+> Access to the NFSv4.1 feature requires whitelisting.  To request whitelisting, submit a request to <[email protected]>. 
+
+* Security  
+  Support for UNIX mode bits (read, write, and execute) is available for NFSv3 and NFSv4.1. Root-level access is required on the NFS client to mount NFS volumes.
+
+* Local user/group and LDAP support for NFSv4.1  
+  Currently, NFSv4.1 supports root access to volumes only. 
+
+## Best practice
+
+* You should ensure that you’re using the proper mount instructions for the volume.  See [Mount or unmount a volume for Windows or Linux virtual machines](azure-netapp-files-mount-unmount-volumes-for-virtual-machines.md).
+
+* The NFS client should be in the same VNet or peered VNet as the Azure NetApp Files volume. Connecting from outside the VNet is supported; however, it will introduce additional latency and decrease overall performance.
+
+* You should ensure that the NFS client is up-to-date and running the latest updates for the operating system.
+
 ## Create an NFS volume
 
 1.	Click the **Volumes** blade from the Capacity Pools blade. 
@@ -66,14 +88,16 @@ A subnet must be delegated to Azure NetApp Files.
 
         ![Create subnet](../media/azure-netapp-files/azure-netapp-files-create-subnet.png)
 
-4. Click **Protocol**, then select **NFS** as the protocol type for the volume.   
+4. Click **Protocol**, and then complete the following actions:  
+    * Select **NFS** as the protocol type for the volume.   
     * Specify the **file path** that will be used to create the export path for the new volume. The export path is used to mount and access the volume.
 
         The file path name can contain letters, numbers, and hyphens ("-") only. It must be between 16 and 40 characters in length. 
 
         The file path must be unique within each subscription and each region. 
 
-    * Optionally, [configure export policy for the NFS volume](azure-netapp-files-configure-export-policy.md)
+    * Select the NFS version (**NFSv3** or **NFSv4.1**) for the volume.  
+    * Optionally, [configure export policy for the NFS volume](azure-netapp-files-configure-export-policy.md).
 
     ![Specify NFS protocol](../media/azure-netapp-files/azure-netapp-files-protocol-nfs.png)
 

articles/azure-netapp-files/azure-netapp-files-faqs.md

@@ -13,7 +13,7 @@ ms.workload: storage
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: conceptual
-ms.date: 09/25/2019
+ms.date: 10/12/2019
 ms.author: b-juche
 ---
 # FAQs About Azure NetApp Files
@@ -45,7 +45,7 @@ Yes, you can, if you create the required DNS entries. Azure NetApp Files supplie
 
 ### Can the network traffic between the Azure VM and the storage be encrypted?
 
-Data traffic (traffic from the NFSv3 or SMBv3 client to Azure NetApp Files volumes) is not encrypted. However, the traffic from an Azure VM (running an NFS or SMB client) to Azure NetApp Files is as secure as any other Azure-VM-to-VM traffic. This traffic is local to the Azure data-center network. 
+Data traffic (traffic from the NFSv3, NFSv4.1, or SMBv3 client to Azure NetApp Files volumes) is not encrypted. However, the traffic from an Azure VM (running an NFS or SMB client) to Azure NetApp Files is as secure as any other Azure-VM-to-VM traffic. This traffic is local to the Azure data-center network. 
 
 ### Can the storage be encrypted at rest?
 
@@ -116,7 +116,11 @@ The volume size reported in DF is the maximum size the Azure NetApp Files volume
 
 ### What NFS version does Azure NetApp Files support?
 
-Azure NetApp Files currently supports NFSv3.
+Azure NetApp Files supports NFSv3 and NFSv4.1. You can create a volume using either NFS version. 
+
+> [!IMPORTANT] 
+> Access to the NFSv4.1 feature requires whitelisting.  To request whitelisting, submit a request to <[email protected]>. 
+
 
 ### How do I enable root squashing?
 

articles/azure-netapp-files/azure-netapp-files-quickstart-set-up-account-create-volumes.md

@@ -13,7 +13,7 @@ ms.workload: storage
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: quickstart 
-ms.date: 9/11/2019
+ms.date: 10/12/2019
 ms.author: b-juche
 #Customer intent: As an IT admin new to Azure NetApp Files, I want to quickly set up Azure NetApp Files and create a volume.
 ---
@@ -238,7 +238,7 @@ This how-to article requires the Azure PowerShell module Az version 2.6.0 or lat
        * Enter **myvnet1** as the Vnet name.
        * Specify an address space for your setting, for example, 10.7.0.0/16
        * Enter **myANFsubnet** as the subnet name.
-       * Specify the subnet address range, for example, 10.7.0.0/24. Note that you cannot share the dedicated subnet with other resources.
+       * Specify the subnet address range, for example, 10.7.0.0/24. You cannot share the dedicated subnet with other resources.
        * Select **Microsoft.NetApp/volumes** for subnet delegation.
        * Click **OK** to create the Vnet.
    5. In subnet, select the newly created Vnet (**myvnet1**) as the delegate subnet.
@@ -247,9 +247,12 @@ This how-to article requires the Azure PowerShell module Az version 2.6.0 or lat
 
       ![Create virtual network window](../media/azure-netapp-files/azure-netapp-files-create-virtual-network-window.png)  
 
-4. Click **Protocol**, then select **NFS** as the protocol type for the volume.   
-
-    Enter **myfilepath1** as the file path that will be used to create the export path for the volume. 
+4. Click **Protocol**, and then complete the following actions: 
+    * Select **NFS** as the protocol type for the volume.  
+    * Enter **myfilepath1** as the file path that will be used to create the export path for the volume.  
+    * Select the NFS version (**NFSv3** or **NFSv4.1**) for the volume.  
+> [!IMPORTANT] 
+> Access to the NFSv4.1 feature requires whitelisting.  To request whitelisting, submit a request to <[email protected]>. 
 
     ![Specify NFS protocol for quickstart](../media/azure-netapp-files/azure-netapp-files-quickstart-protocol-nfs.png)