Merge pull request #278753 from sreekzz/patch-52

Added a note

Author: prmerger-automator[bot]

articles/hdinsight/hdinsight-hadoop-use-blob-storage.md

@@ -35,7 +35,8 @@ Sharing one blob container as the default file system for multiple clusters isn'
 
 ## Access files from within cluster
 
-There are several ways you can access the files in Data Lake Storage from an HDInsight cluster. The URI scheme provides unencrypted access (with the *wasb:* prefix) and TLS encrypted access (with *wasbs*). We recommend using *wasbs* wherever possible, even when accessing data that lives inside the same region in Azure.
+> [!NOTE]
+> Azure storage team has discontinued all active developments on WASB and recommend all customers to use the ABFS driver to interact with Blob and ADLS gen2. For more information, see [The Azure Blob Filesystem driver (ABFS): A dedicated Azure Storage driver for Hadoop](/azure/storage/blobs/data-lake-storage-abfs-driver)
 
 * **Using the fully qualified name**. With this approach, you provide the full path to the file that you want to access.
 
@@ -155,7 +156,7 @@ The default Blob container stores cluster-specific information such as job histo
 While creating an HDInsight cluster, you specify the Azure Storage account you want to associate with it. Also, you can add additional storage accounts from the same Azure subscription or different Azure subscriptions during the creation process or after a cluster has been created. For instructions about adding additional storage accounts, see [Create HDInsight clusters](hdinsight-hadoop-provision-linux-clusters.md).
 
 > [!WARNING]  
-> Using an additional storage account in a different location than the HDInsight cluster is not supported.
+> Using an additional storage account in a different location other than the HDInsight cluster is not supported.
 
 ## Next steps