Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Blob APIs work with accounts that have a hierarchical namespace (a file system structure that organizes blob data into directories and files). This support unlocks the ecosystem of tools, applications, and services, as well as several Blob storage features for accounts that have a hierarchical namespace.
Multi-protocol access on Data Lake Storage lets you use the full ecosystem of tools and applications, including third-party ones. You can point these tools and applications to accounts that have a hierarchical namespace without modifying them. These applications work as is even if they call Blob APIs, because Blob APIs operate on data in accounts that have a hierarchical namespace.
Blob storage features such as diagnostic logging, access tiers, and Blob storage lifecycle management policies work with accounts that have a hierarchical namespace. Therefore, you can enable hierarchical namespaces on your Blob storage accounts without losing access to these important features.
Note
These articles summarize the current support for Blob storage features and Azure service integrations.
How multi-protocol access on Data Lake Storage works
Blob APIs and Data Lake Storage APIs can operate on the same data in storage accounts that have a hierarchical namespace. Data Lake Storage routes Blob APIs through the hierarchical namespace, giving you first-class directory operations and POSIX-compliant access control lists (ACLs).
Existing tools and applications that use Blob APIs automatically gain these benefits. Developers don't need to modify them. Data Lake Storage consistently applies directory and file-level ACLs regardless of the protocol that tools and applications use to access the data.