diff --git a/docs/t-sql/functions/openrowset-bulk-transact-sql.md b/docs/t-sql/functions/openrowset-bulk-transact-sql.md
index cd3b01b71d4..b6950c7f584 100644
--- a/docs/t-sql/functions/openrowset-bulk-transact-sql.md
+++ b/docs/t-sql/functions/openrowset-bulk-transact-sql.md
@@ -165,6 +165,12 @@ Beginning with [!INCLUDE [sssql17-md](../../includes/sssql17-md.md)], the *data_
 - `abfss://<container>@<storage>.dfs.core.windows.net/<file path>` to access Azure Data Lake Storage
 - `https://onelake.dfs.fabric.microsoft.com/<workspaceId>/<lakehouseId>/Files/<file path>` - to access OneLake in Microsoft Fabric
 
+When accessing data stored in Azure Data Lake Storage Gen2, use the `abfss://<container>@<storage>.dfs.core.windows.net/<file path>` or `https://<storage>.dfs.core.windows.net/<container>/<file path>` URI formats instead of the Blob endpoint.
+
+The DFS and ABFS schemes provide full support for the hierarchical namespace (HNS), which enables directory semantics, optimized file operations, and POSIX-style access control lists (ACLs). 
+
+In contrast, the Blob endpoint does not expose HNS features and treats all paths as flat object keys. This can lead to reduced performance, limited directory behavior, and incompatibility with engines that expect ADLS Gen2 filesystem semantics.
+
 > [!NOTE]
 > This article and the supported URI patterns differ on different platforms. For the URI patterns that are available in SQL Server, Azure SQL Database, and Azure SQL Managed Instance, [select the product in the version dropdown list](openrowset-bulk-transact-sql.md?view=sql-server-ver17&preserve-view=true#bulk-data_file_path).