Skip to content

Commit b557f46

Browse files
committed
issue #107240
1 parent f7d98c7 commit b557f46

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

articles/azure-netapp-files/azure-netapp-files-network-topologies.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.service: azure-netapp-files
1212
ms.workload: storage
1313
ms.tgt_pltfrm: na
1414
ms.topic: conceptual
15-
ms.date: 2/17/2022
15+
ms.date: 3/30/2023
1616
ms.author: ramakk
1717
ms.custom: references_regions
1818
---
@@ -137,6 +137,8 @@ If you use a new VNet, you can create a subnet and delegate the subnet to Azure
137137

138138
If the VNet is peered with another VNet, you can't expand the VNet address space. For that reason, the new delegated subnet needs to be created within the VNet address space. If you need to extend the address space, you must delete the VNet peering before expanding the address space.
139139

140+
The address space size of the Azure NetApp Files VNet should be larger than its delegated subnet. If it is not, SMB volume creation will fail.
141+
140142
### UDRs and NSGs
141143

142144
If the subnet has a combination of volumes with the Standard and Basic network features, user-defined routes (UDRs) and network security groups (NSGs) applied on the delegated subnets will only apply to the volumes with the Standard network features.

0 commit comments

Comments
 (0)