Skip to content

Commit ae4a0de

Browse files
committed
Learn Editor: Update network-file-system-protocol-support.md
1 parent 1c51ee6 commit ae4a0de

1 file changed

Lines changed: 7 additions & 4 deletions

File tree

articles/storage/blobs/network-file-system-protocol-support.md

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -132,26 +132,29 @@ For step-by-step guidance, see [Mount Blob storage by using the Network File Sys
132132
Traffic must originate from a VNet. A VNet enables clients to securely connect to your storage account. The only way to secure the data in your account is by using a VNet and other network security settings. Any other tool used to secure data including account key authorization, Microsoft Entra security, and access control lists (ACLs) can't be used to authorize an NFS 3.0 request.
133133

134134
To learn more, see [Network security recommendations for Blob storage](security-recommendations.md#networking).
135+
> [!Note]
136+
> Public IP whitelisting is not supported.
135137
136138
### Supported network connections
137139

138-
A client can connect over a public or a [private endpoint](../common/storage-private-endpoints.md), and can connect from any of the following network locations:
140+
Clients can connect via a public or [private endpoint](../common/storage-private-endpoints.md), provided the connection originates from any of the following network locations:
139141

140142
- The VNet that you configure for your storage account.
141143

142144
In this article, we'll refer to that VNet as the *primary VNet*. To learn more, see [Grant access from a virtual network](../common/storage-network-security.md#grant-access-from-a-virtual-network).
143-
145+
144146
- A peered VNet that is in the same region as the primary VNet.
145147

146148
You'll have to configure your storage account to allow access to this peered VNet. To learn more, see [Grant access from a virtual network](../common/storage-network-security.md#grant-access-from-a-virtual-network).
147-
149+
148150
- An on-premises network that is connected to your primary VNet by using [VPN Gateway](../../vpn-gateway/vpn-gateway-about-vpngateways.md) or an [ExpressRoute gateway](../../expressroute/expressroute-howto-add-gateway-portal-resource-manager.md).
149151

150152
To learn more, see [Configuring access from on-premises networks](../common/storage-network-security.md#configuring-access-from-on-premises-networks).
151-
153+
152154
- An on-premises network that is connected to a peered network.
153155

154156
This can be done by using [VPN Gateway](../../vpn-gateway/vpn-gateway-about-vpngateways.md) or an [ExpressRoute gateway](../../expressroute/expressroute-howto-add-gateway-portal-resource-manager.md) along with [Gateway transit](/azure/architecture/reference-architectures/hybrid-networking/vnet-peering#gateway-transit).
157+
155158

156159
> [!IMPORTANT]
157160
> The NFS 3.0 protocol uses ports 111 and 2048. If you're connecting from an on-premises network, make sure that your client allows outgoing communication through those ports. If you have granted access to specific VNets, make sure that any network security groups associated with those VNets don't contain security rules that block incoming communication through those ports.

0 commit comments

Comments
 (0)