Skip to content

Commit 58bb892

Browse files
committed
acrolinx
1 parent 5c77ea4 commit 58bb892

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

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

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: azure-netapp-files
55
author: b-hchen
66
ms.service: azure-netapp-files
77
ms.topic: how-to
8-
ms.date: 09/28/2023
8+
ms.date: 10/09/2024
99
ms.author: anfdocs
1010
---
1111
# Delegate a subnet to Azure NetApp Files
@@ -14,20 +14,20 @@ You must delegate a subnet to Azure NetApp Files. When you create a volume, you
1414

1515
## Considerations
1616

17-
* 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.
17+
* 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 virtual network (VNet) and delegated subnet sizes consciously.
1818
* In each VNet, only one subnet can be delegated to Azure NetApp Files.
1919
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.
2020
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.
21-
* You can't designate a network security group or service endpoint in the delegated subnet. Doing so causes the subnet delegation to fail.
21+
* If you're using Basic network features, you can't designate a network security group (NSG) or service endpoint in the delegated subnet. Doing so causes the subnet delegation to fail. To designate an NSG or service endpoint, [upgrade to Standard network features](configure-network-features.md).
2222
* 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).
2323
* 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).
2424
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.
2525

2626
## Steps
2727

28-
1. Go to the **Virtual networks** blade in the Azure portal and select the virtual network that you want to use for Azure NetApp Files.
28+
1. Navigate to **Virtual networks** in the Azure portal. Select the virtual network that you want to use for Azure NetApp Files.
2929

30-
1. Select **Subnets** from the Virtual network blade and click the **+Subnet** button.
30+
1. From Virtual network, select **Subnets** then the **+Subnet** button.
3131

3232
1. Create a new subnet to use for Azure NetApp Files by completing the following required fields in the Add Subnet page:
3333
* **Name**: Specify the subnet name.

0 commit comments

Comments
 (0)