Merge pull request #253196 from b-hchen/patch-127

Subnet consideration: Update for GitHub issue 115243

Author: prmerger-automator[bot]

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

@@ -12,7 +12,7 @@ ms.service: azure-netapp-files
 ms.workload: storage
 ms.tgt_pltfrm: na
 ms.topic: how-to
-ms.date: 09/07/2023
+ms.date: 09/28/2023
 ms.author: anfdocs
 ---
 # Delegate a subnet to Azure NetApp Files 
@@ -21,12 +21,12 @@ You must delegate a subnet to Azure NetApp Files. When you create a volume, you
 
 ## Considerations
 
-* The wizard for creating a new subnet defaults to a /24 network mask, which provides for 251 available IP addresses. You should consider a larger subnet (for example, /23 network mask) in scenarios such as SAP HANA where many volumes and storage endpoints are anticipated. You can also stay with the default network mask /24 as proposed by the wizard if you don't need to reserve many client or VM IP addresses in your Azure Virtual Network (VNet). Note that the network mask of the delegated network cannot be changed after the initial creation. 
+* When creating the delegated subnet for Azure NetApp Files, the size of the subnet matters. A subnet with a /28 network mask provides (only) 11 usable IP addresses, which might be insufficient for certain use cases. In that case, you should plan for a larger delegated subnet. For instance, a subnet with a /26 network mask provides 59 and a /24 network mask provides 251 available IP addresses respectively. You should consider even larger subnets (for example, /23 network mask) in scenarios where application volume group for SAP HANA is used and where many volumes and storage endpoints are anticipated. The network mask of the delegated network can't be changed after the initial creation. Make sure to plan your VNet and delegated subnet sizes consciously. 
 * In each 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.  
+   Azure enables you to create multiple delegated subnets in a VNet.  However, any attempts to create a new volume would fail if you use more than one delegated subnet.  
    You can have only a single delegated subnet in a VNet. A NetApp account can deploy volumes into multiple VNets, each having its own 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 using Basic networks features. Global VNet peering is supported with Standard network features. See [Supported network topologies](azure-netapp-files-network-topologies.md#supported-network-topologies) for more information.
+* You can't 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 isn't currently supported using Basic networks features. Global VNet peering is supported with Standard network features. For more information, see [Supported network topologies](azure-netapp-files-network-topologies.md#supported-network-topologies).
 * For Azure NetApp Files support of [User-defined routes](../virtual-network/virtual-networks-udr-overview.md#custom-routes) (UDRs) and Network security groups (NSGs), see [Constraints in Guidelines for Azure NetApp Files network planning](azure-netapp-files-network-topologies.md#constraints).   
    To establish routing or access control ***to*** the Azure NetApp Files delegated subnet, you can apply UDRs and NSGs to other subnets, even within the same VNet as the subnet delegated to Azure NetApp Files.