Skip to content

Commit 6e80864

Browse files
committed
issue #107240
1 parent c37693f commit 6e80864

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
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: 3/30/2023
15+
ms.date: 04/12/2023
1616
ms.author: ramakk
1717
ms.custom: references_regions
1818
---
@@ -137,7 +137,7 @@ 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.
140+
Ensure that the address space size of the Azure NetApp Files delegated subnet is smaller than the address space of the virtual network to avoid unforeseen issues.
141141

142142
### UDRs and NSGs
143143

0 commit comments

Comments
 (0)