Merge pull request #239369 from RenaShahMSFT/patch-42

Update storage-files-networking-endpoints.md

Author: prmerger-automator[bot]

articles/storage/files/storage-files-networking-endpoints.md

@@ -40,7 +40,8 @@ We recommend reading [Azure Files networking considerations](storage-files-netwo
 
 You can configure your endpoints to restrict network access to your storage account. There are two approaches to restricting access to a storage account to a virtual network:
 
-- [Create one or more private endpoints for the storage account](#create-a-private-endpoint)  and restrict all access to the public endpoint. This ensures that only traffic originating from within the desired virtual networks can access the Azure file shares within the storage account.
+- [Create one or more private endpoints for the storage account](#create-a-private-endpoint)  and restrict all access to the public endpoint. This ensures that only traffic originating from within the desired virtual networks can access the Azure file shares within the storage account. 
+*See [Private Link cost](https://azure.microsoft.com/pricing/details/private-link/).
 - [Restrict the public endpoint to one or more virtual networks](#restrict-public-endpoint-access). This works by using a capability of the virtual network called *service endpoints*. When you restrict the traffic to a storage account via a service endpoint, you are still accessing the storage account via the public IP address, but access is only possible from the locations you specify in your configuration.
 
 ### Create a private endpoint
@@ -178,4 +179,4 @@ When you restrict the storage account to specific virtual networks, you are allo
 
 - [Azure Files networking considerations](storage-files-networking-overview.md)
 - [Configuring DNS forwarding for Azure Files](storage-files-networking-dns.md)
-- [Configuring S2S VPN for Azure Files](storage-files-configure-s2s-vpn.md)
+- [Configuring S2S VPN for Azure Files](storage-files-configure-s2s-vpn.md)