Merge pull request #95485 from MicrosoftDocs/master

Merge master to live Sunday 4:00 PM

Author: GitHubber17

articles/azure-netapp-files/TOC.yml

@@ -47,10 +47,12 @@
     href: azure-netapp-files-set-up-capacity-pool.md
   - name: Delegate a subnet to Azure NetApp Files
     href: azure-netapp-files-delegate-subnet.md
-  - name: Create an NFS volume for Azure NetApp Files
-    href: azure-netapp-files-create-volumes.md
   - name: Create an SMB volume for Azure NetApp Files
     href: azure-netapp-files-create-volumes-smb.md
+  - name: Create an NFS volume for Azure NetApp Files
+    href: azure-netapp-files-create-volumes.md
+  - name: Configure NFSv4.1 default domain for Azure NetApp Files
+    href: azure-netapp-files-configure-nfsv41-domain.md
   - name: Configure export policy for an NFS volume
     href: azure-netapp-files-configure-export-policy.md
   - name: Manage volumes

articles/azure-netapp-files/azure-netapp-files-configure-nfsv41-domain.md

@@ -0,0 +1,71 @@
+---
+title: Configure NFSv4.1 default domain for Azure NetApp Files | Microsoft Docs
+description: Describes how to configure the NFS client for using NFSv4.1 with Azure NetApp Files.
+documentationcenter: ''
+author: b-juche
+manager: ''
+editor: ''
+
+ms.assetid:
+ms.service: azure-netapp-files
+ms.workload: storage
+ms.tgt_pltfrm: na
+ms.devlang: na
+ms.topic: conceptual
+ms.date: 11/08/2019
+ms.author: b-juche
+---
+# Configure NFSv4.1 default domain for Azure NetApp Files
+
+NFSv4 introduces the concept of an authentication domain. Azure NetApp Files currently supports root-only user mapping from the service to the NFS client. To use the NFSv4.1 functionality with Azure NetApp Files, you need to update the NFS client.
+
+## Default behavior of user/group mapping
+
+Root mapping defaults to the `nobody` user because the NFSv4 domain is set to `localdomain`. When you mount an Azure NetApp Files NFSv4.1 volume as root, you will see file permissions as follows:  
+
+![Default behavior of user/group mapping for NFSv4.1](../media/azure-netapp-files/azure-netapp-files-nfsv41-default-behavior-user-group-mapping.png)
+
+As the above example shows, the user for `file1` should be `root`, but it maps to `nobody` by default.  This article shows you how to set the `file1` user to `root`.  
+
+## Steps 
+
+1. Edit the `/etc/idmapd.conf` file on the NFS client.   
+    Uncomment the line `#Domain` (that is, remove the `#` from the line), and change the value `localdomain` to `defaultv4iddomain.com`. 
+
+    Initial configuration: 
+    
+    ![Initial configuration for NFSv4.1](../media/azure-netapp-files/azure-netapp-files-nfsv41-initial-config.png)
+
+    Updated configuration:
+    
+    ![Updated configuration for NFSv4.1](../media/azure-netapp-files/azure-netapp-files-nfsv41-updated-config.png)
+
+2. Unmount any currently mounted NFS volumes.
+3. Update the `/etc/idmapd.conf` file.
+4. Restart the `rpcbind` service on your host (`service rpcbind restart`), or simply reboot the host.
+5. Mount the NFS volumes as required.   
+
+    See [Mount or unmount a volume for Windows or Linux virtual machines](azure-netapp-files-mount-unmount-volumes-for-virtual-machines.md). 
+
+The following example shows the resulting user/group change: 
+
+![Resulting configuration for NFSv4.1](../media/azure-netapp-files/azure-netapp-files-nfsv41-resulting-config.png)
+
+As the example shows, the user/group has now changed from `nobody` to `root`.
+
+## Behavior of other (non-root) users and groups
+
+Azure NetApp Files supports local users (users created locally on a host) who have permissions associated with files or folders in NFSv4.1 volumes. However, the service does not currently support mapping the users/groups across multiple nodes. Therefore, users created on one host do not map by default to users created on another host. 
+
+In the following example, `Host1` has three existing test user accounts (`testuser01`, `testuser02`, `testuser03`): 
+
+![Resulting configuration for NFSv4.1](../media/azure-netapp-files/azure-netapp-files-nfsv41-host1-users.png)
+
+On `Host2`, note that the test user accounts have not been created, but the same volume is mounted on both hosts:
+
+![Resulting configuration for NFSv4.1](../media/azure-netapp-files/azure-netapp-files-nfsv41-host2-users.png)
+
+## Next step 
+
+[Mount or unmount a volume for Windows or Linux virtual machines](azure-netapp-files-mount-unmount-volumes-for-virtual-machines.md)
+

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

@@ -13,7 +13,7 @@ ms.workload: storage
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: conceptual
-ms.date: 10/12/2019
+ms.date: 11/08/2019
 ms.author: b-juche
 ---
 # Create an NFS volume for Azure NetApp Files
@@ -38,7 +38,7 @@ A subnet must be delegated to Azure NetApp Files.
   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. 
+  Currently, NFSv4.1 supports root access to volumes only. See [Configure NFSv4.1 default domain for Azure NetApp Files](azure-netapp-files-configure-nfsv41-domain.md). 
 
 ## Best practice
 
@@ -110,6 +110,7 @@ A subnet must be delegated to Azure NetApp Files.
 
 ## Next steps  
 
+* [Configure NFSv4.1 default domain for Azure NetApp Files](azure-netapp-files-configure-nfsv41-domain.md)
 * [Mount or unmount a volume for Windows or Linux virtual machines](azure-netapp-files-mount-unmount-volumes-for-virtual-machines.md)
 * [Configure export policy for an NFS volume](azure-netapp-files-configure-export-policy.md)
 * [Resource limits for Azure NetApp Files](azure-netapp-files-resource-limits.md)

articles/azure-netapp-files/azure-netapp-files-mount-unmount-volumes-for-virtual-machines.md

@@ -13,7 +13,7 @@ ms.workload: storage
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: conceptual
-ms.date: 03/07/2019
+ms.date: 11/08/2019
 ms.author: b-juche
 ---
 # Mount or unmount a volume for Windows or Linux virtual machines 
@@ -27,5 +27,8 @@ You can mount or unmount a volume for Windows or Linux virtual machines as neces
 
     ![Mount instructions SMB](../media/azure-netapp-files/azure-netapp-files-mount-instructions-smb.png)
 
-If you are using NFSv4.1, use the following command to mount your file system: 
-`sudo mount -t nfs -o rw,hard,rsize=65536,wsize=65536,vers=4.1,tcp,sec=sys $MOUNTTARGETIPADDRESS:/$VOLUMENAME $MOUNTPOINT`
+If you are using NFSv4.1, use the following command to mount your file system:  
+
+`sudo mount -t nfs -o rw,hard,rsize=65536,wsize=65536,vers=4.1,tcp,sec=sys $MOUNTTARGETIPADDRESS:/$VOLUMENAME $MOUNTPOINT`  
+
+See [Configure NFSv4.1 default domain for Azure NetApp Files](azure-netapp-files-configure-nfsv41-domain.md).

articles/azure-netapp-files/azure-netapp-files-solution-architectures.md

@@ -13,7 +13,7 @@ ms.workload: storage
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: conceptual
-ms.date: 08/26/2019
+ms.date: 11/08/2019
 ms.author: b-juche
 ---
 # Solution architectures using Azure NetApp Files
@@ -34,6 +34,7 @@ This article provides references to best practices that can help you understand
 * [High availability for SAP NetWeaver on Azure VMs on SUSE Linux Enterprise Server with Azure NetApp Files for SAP applications](https://docs.microsoft.com/azure/virtual-machines/workloads/sap/high-availability-guide-suse-netapp-files)
 * [Azure Virtual Machines high availability for SAP NetWeaver on Red Hat Enterprise Linux with Azure NetApp Files for SAP applications](https://docs.microsoft.com/azure/virtual-machines/workloads/sap/high-availability-guide-rhel-netapp-files)
 * [SAP HANA scale-out with standby node on Azure VMs with Azure NetApp Files on SUSE Linux Enterprise Server](https://docs.microsoft.com/azure/virtual-machines/workloads/sap/sap-hana-scale-out-standby-netapp-files-suse)
+* [SAP HANA Azure virtual machine storage configurations](https://docs.microsoft.com/azure/virtual-machines/workloads/sap/hana-vm-operations-storage)
 
 ## Talon solutions