Merge pull request #108334 from b-juche/patch-10

Clarify delegated subnects for vol creation

Author: PRMerger6

articles/azure-netapp-files/azure-netapp-files-delegate-subnet.md

@@ -13,7 +13,7 @@ ms.workload: storage
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: conceptual
-ms.date: 03/25/2019
+ms.date: 03/19/2020
 ms.author: b-juche
 ---
 # Delegate a subnet to Azure NetApp Files 
@@ -22,7 +22,8 @@ You must delegate a subnet to Azure NetApp Files.   When you create a volume, yo
 
 ## Considerations
 * The wizard for creating a new subnet defaults to a /24 network mask, which provides for 251 available IP addresses. Using a /28 network mask, which provides for 16 usable IP addresses, is sufficient for the service.
-* In each Azure Virtual Network (Vnet), only one subnet can be delegated to Azure NetApp Files.
+* In each Azure Virtual Network (VNet), only one subnet can be delegated to Azure NetApp Files.   
+   Azure enables you to create multiple delegated subnets in a VNet.  However, any attempts to create a new volume will fail if you use more than one delegated subnet.
 * You cannot designate a network security group or service endpoint in the delegated subnet. Doing so causes the subnet delegation to fail.
 * Access to a volume from a globally peered virtual network is not currently supported.
 * Creating [user-defined custom routes](https://docs.microsoft.com/azure/virtual-network/virtual-networks-udr-overview#custom-routes) on VM subnets with address prefix (destination) to a subnet delegated to Azure NetApp Files is unsupported. Doing so will impact VM connectivity.