Merge pull request #307347 from khdownie/kendownie102425

add storage explorer support

Author: prmerger-automator[bot]

articles/storage/files/files-nfs-protocol.md

@@ -4,7 +4,7 @@ description: Learn about file shares hosted in Azure Files using the Network Fil
 author: khdownie
 ms.service: azure-file-storage
 ms.topic: concept-article
-ms.date: 07/11/2025
+ms.date: 10/24/2025
 ms.author: kendownie
 ms.custom: references_regions
 # Customer intent: "As a DevOps engineer, I want to deploy and manage NFS file shares in Azure Files, so that I can support Linux-based applications and workloads that require POSIX compliance and efficient data access."
@@ -45,10 +45,10 @@ NFS file shares are often used in the following scenarios:
 
 ## Features
 
-- Fully POSIX-compliant file system.
-- Hard link support.
-- Symbolic link support.
-- NFS file shares currently only support most features from the [4.1 protocol specification](https://tools.ietf.org/html/rfc5661). Some features such as delegations and callback of all kinds, Kerberos authentication, and ACLs aren't supported.
+- Fully POSIX-compliant file system
+- Hard link support
+- Symbolic link support
+- NFS Azure file shares currently support most features from the [4.1 protocol specification](https://tools.ietf.org/html/rfc5661). Some features such as delegations and callback of all kinds, Kerberos authentication, and ACLs aren't supported.
 
 > [!NOTE]
 > Creating a hard link from an existing symbolic link isn't currently supported.
@@ -57,7 +57,7 @@ NFS file shares are often used in the following scenarios:
 
 All data stored in Azure Files is encrypted at rest using Azure storage service encryption (SSE). Storage service encryption works similarly to BitLocker on Windows: data is encrypted beneath the file system level. Because data is encrypted beneath the Azure file share's file system, as it's encoded to disk, you don't have to have access to the underlying key on the client to read or write to the Azure file share. Encryption at rest applies to both the SMB and NFS protocols.
 
-For [encryption in transit](encryption-in-transit-for-nfs-shares.md), Azure Files NFS v4.1 volumes enhance network security by enabling secure TLS connections between the server and the client, protecting data in transit from interception. 
+For [encryption in transit](encryption-in-transit-for-nfs-shares.md), Azure Files NFSv4.1 volumes enhance network security by enabling secure TLS connections between the server and the client, protecting data in transit from interception. 
 Azure provides a layer of encryption for all data in transit between Azure datacenters using [MACSec](https://en.wikipedia.org/wiki/IEEE_802.1AE). Through this, encryption exists when data is transferred between Azure data centers.
 
 Unlike Azure Files using the SMB protocol, file shares using the NFS protocol don't offer user-based authentication. Authentication for NFS shares is based on the configured network security rules. Due to this, to ensure only secure connections are established to your NFS share, you must set up either a private endpoint or a service endpoint for your storage account.
@@ -79,7 +79,7 @@ For more details on the available networking options, see [Azure Files networkin
 
 ## Support for Azure Storage features
 
-The following table shows the current level of support for Azure Storage features in accounts that have the NFS 4.1 feature enabled.
+The following table shows the current level of feature support for NFS Azure file shares.
 
 The status of items that appear in this table might change over time as support continues to expand.
 
@@ -108,8 +108,8 @@ The status of items that appear in this table might change over time as support
 | [Azure file share snapshots](storage-snapshots-files.md)|  ✔️ |
 | [GRS or GZRS redundancy types](storage-files-planning.md#redundancy)| ⛔ |
 | [AzCopy](../common/storage-use-azcopy-v10.md?toc=/azure/storage/files/toc.json)| ✔️ |
-| Azure Storage Explorer| ⛔ |
-| Azure Storage Explorer on Azure portal| ⛔ |
+| Azure Storage Explorer| ✔️ |
+| Azure Storage Browser on Azure portal| ⛔ |
 | Support for more than 16 groups| ⛔ |
 
 ## Regional availability
@@ -118,7 +118,7 @@ NFS Azure file shares are supported in all regions that support SSD file shares.
 
 ## Performance
 
-NFS Azure file shares are only offered on SSD file shares, which store data on solid-state drives (SSD). In provisioned v2 model, you get to customize on provisioned capactiy, IOPS, and throughput independently. See the [provisioned v2 model](understanding-billing.md#provisioned-v2-model) section of the **Understanding billing** article to understand more. In provisioned v1 model, the IOPS and throughput of NFS shares scale with the provisioned capacity. See the [provisioned v1 model](understanding-billing.md#provisioned-v1-model) section of the **Understanding billing** article to understand the formulas for IOPS, IO bursting, and throughput. The average IO latencies are low-single-digit-millisecond for small IO size, while average metadata latencies are high-single-digit-millisecond. Metadata heavy operations such as untar and workloads like WordPress might face additional latencies due to the high number of open and close operations.
+NFS Azure file shares are only offered on SSD file shares, which store data on solid-state drives (SSD). In the provisioned v2 model, you get to customize on provisioned capactiy, IOPS, and throughput independently. See the [provisioned v2 model](understanding-billing.md#provisioned-v2-model) to understand more. In the provisioned v1 model, the IOPS and throughput of NFS shares scale with the provisioned capacity. See the [provisioned v1 model](understanding-billing.md#provisioned-v1-model) to understand the formulas for IOPS, IO bursting, and throughput. The average IO latencies are low-single-digit-millisecond for small IO size, while average metadata latencies are high-single-digit-millisecond. Metadata heavy operations such as untar and workloads like WordPress might face additional latencies due to the high number of open and close operations.
 
 > [!NOTE]
 > You can use the `nconnect` Linux mount option to improve performance for NFS Azure file shares at scale. For more information, see [Improve NFS Azure file share performance](nfs-performance.md).
@@ -132,5 +132,5 @@ NFS has been validated to work well with workloads such as SAP application layer
 
 ## Next steps
 
-- [Create an NFS file share](create-classic-file-share.md)
+- [Create a classic file share](create-classic-file-share.md)
 - [Compare access to Azure Files, Blob Storage, and Azure NetApp Files with NFS](../common/nfs-comparison.md?toc=/azure/storage/files/toc.json)