Multi-protocol access on Azure Data Lake Storage (preview)

Blob APIs now work with accounts that have a hierarchical namespace. This unlocks the entire ecosystem of tools, applications, and services, as well as all Blob storage features to accounts that have a hierarchical namespace.

Until recently, you might have had to maintain separate storage solutions for object storage and analytics storage. That's because Azure Data Lake Storage Gen2 had limited ecosystem support. It also had limited access to Blob service features such as diagnostic logging. A fragmented storage solution is hard to maintain because you have to move data between accounts to accomplish various scenarios. You no longer have to do that.

Note

Multi-protocol access on Data Lake Storage is in public preview, and is available in all regions. You don't have to enroll in the public preview because it is automatically available to all accounts that have a hierarchical namespace. To review limitations, see the Known issues article.

Use the entire ecosystem of applications, tools, and services

With multi-protocol access on Data Lake Storage, you can work with all of your data by using the entire ecosystem of tools, applications, and services. This includes Azure services such as Azure Stream Analytics, IOT Hub, Power BI, and many others. For a complete list, see Integrate Azure Data Lake Storage with Azure services.

This also includes third-party tools and applications. You can point them to accounts that have a hierarchical namespace without having to modify them. These applications work as is even if they call Blob APIs, because Blob APIs can now operate on data in accounts that have a hierarchical namespace.

Note

To review limitations, see the Known issues article.

Use all Blob storage features

Blob storage features such as diagnostic logging, access tiers, and Blob storage lifecycle management policies now work with accounts that have a hierarchical namespace. Therefore, you can enable hierarchical namespaces on your blob storage accounts without loosing access to these important features.

Note

To review limitations, see the Known issues article.

How multi-protocol access on data lake storage works

Blob APIs and Data Lake Storage Gen2 APIs can operate on the same data in storage accounts that have a hierarchical namespace. Data Lake Storage Gen2 routes Blob APIs through the hierarchical namespace so that you can get the benefits of first class directory operations and POSIX-compliant access control lists (ACLs).

Multi-protocol access on Data Lake Storage conceptual

Existing tools and applications that use the Blob API gain these benefits automatically. Developers won't have to modify them. Data Lake Storage Gen2 consistently applies directory and file-level ACLs regardless of the protocol that tools and applications use to access the data.

Next steps

See Known issues