Header Place holder

Azure Data Lake Storage Gen2Azure Data Lake Storage Gen2

Massively scalable, secure data lake storage built on Blob Storage

Apply for trial Buy Now

Azure Data Lake Storage Gen2 is the world’s most productive Data Lake. It combines the power of a Hadoop compatible file system with integrated hierarchical namespace with the massive scale and economy of Azure Blob Storage to help speed your transition from proof of concept to production.

  1. Is fully integrated with the Azure Blob Storage platform; Every Blob Storage capability (Azure Active Directory Integration, At Rest Encryption, High-availability and disaster recovery, Automated Lifecycle Policy Management, Storage Account Firewalls, etc.) can be used by Azure Data Lake Storage
  2. Is optimized for leading cloud analytic engines
  3. Is tightly integrated with all elements of the Azure Big Data Analytics stack to deliver fast insights
  4. Allows analytics data to coexist with object data in the same store with no programming changes or data copying
  5. Performs faster than other data stores thus making your analytics workloads run faster and lowering your TCO

Pricing Details

General Purpose v2 provides access to the latest Azure storage features, including Cool and Archive storage, with pricing optimized for the lowest GB storage prices. These accounts provide access to Data Lake Storage, Block Blobs, Page Blobs, Files, and Queues.

Azure Data Lake Storage Gen2 provides the choice of organizing data in two different ways. With hierarchical namespaces option, customers can organize their Data Lake into structured directories, folders and files. With flat namespaces, customers can operate their Data Lake as an unstructured blob store. Regardless of the two options, customers will pay for the same storage price as per the table below. However, with the hierarchical namespace option, customers will be charged for additional meta-data associated with the folder and directory structure as part of the bill.

Data storage prices

All prices are per GB, per month.

*The following prices are tax-inclusive.

Local Redundant Storage (LRS) Geo-Redundant Storage (GRS) Read/Access Geo-Redundant Storage (RA-GRS)
Hierarchical
Namespace
Flat
Namespace
Hierarchical
Namespace
Flat
Namespace
Hierarchical
Namespace
Flat
Namespace
Hot Cool Hot Cool Hot Cool Hot Cool Hot Cool Hot Cool
1GB/month ¥0.149 ¥0.11 ¥0.149 ¥0.11 ¥0.298 ¥0.22 ¥0.298 ¥0.22 ¥0.372 ¥0.279 ¥0.372 ¥0.279

Transaction prices

*The following prices are tax-inclusive.

Local Redundant Storage (LRS) Geo-Redundant Storage (GRS) Read/Access Geo-Redundant Storage (RA-GRS)
Hierarchical
Namespace
Flat
Namespace
Hierarchical
Namespace
Flat
Namespace
Hierarchical
Namespace
Flat
Namespace
Hot Cool Hot Cool Hot Cool Hot Cool Hot Cool Hot Cool
Write Operations* (every 4MB, per 10,000) ¥0.059 ¥0.117 ¥0.045 ¥0.09 ¥0.118 ¥0.234 ¥0.09 ¥0.18 ¥0.118 ¥0.234 ¥0.09 ¥0.18
Read Operations** (every 4MB, per 10,000) ¥0.02 ¥0.039 ¥0.015 ¥0.03 ¥0.02 ¥0.039 ¥0.015 ¥0.03 ¥0.02 ¥0.039 ¥0.015 ¥0.03
*The following API calls are considered write operations: AppendFile,CreateFilesystem,CreatePath,CreatePathFile,FlushFile,SetFileProperties,SetFilesystemProperties,RenameFile,RenamePathFile,CopyFile

**The following API calls are considered read operations: ReadFile, ListFilesystemFile

Archive early deletion

In addition to the per-GB, per-month charge, any blob that is moved to Archive is subject to an Archive early deletion period of 180 days. This charge is prorated. For example, if a blob is moved to Archive and then deleted or moved to the Hot tier after 45 days, the customer is charged an early deletion fee equivalent to 135 (180 minus 45) days of storing that blob in Archive.

Other Operations and Meta data Storage meters

*The following prices are tax-inclusive.

Local Redundant Storage (LRS) Geo-Redundant Storage (GRS) Read/Access Geo-Redundant Storage
(RA-GRS)
Hierarchical
Namespace
Flat
Namespace
Hierarchical
Namespace
Flat
Namespace
Hierarchical
Namespace
Flat
Namespace
Hot Cool Hot Cool Hot Cool Hot Cool Hot Cool Hot Cool
List and Create Container Operations (per 10,000) ¥0.059 ¥0.117 ¥0.045 ¥0.09 ¥0.118 ¥0.153 ¥0.09 ¥0.18 ¥0.118 ¥0.153 ¥0.09 ¥0.18
Iterative Write Operations (100’s)* ¥0.059 ¥0.117 ¥0.045 ¥0.09 ¥0.118 ¥0.153 ¥0.09 ¥0.18 ¥0.118 ¥0.153 ¥0.09 ¥0.18
All other Operations (per 10,000), except Delete, which is free ¥0.0195 ¥0.039 ¥0.015 ¥0.03 ¥0.0195 ¥0.039 ¥0.015 ¥0.03 ¥0.0195 ¥0.039 ¥0.015 ¥0.03
Data Retrieval (per GB) Free ¥0.0657 Free ¥0.0657 Free ¥0.0657 Free ¥0.0657 Free ¥0.0657 Free ¥0.0657
Data Write (per GB) Free Free Free Free Free Free Free Free Free Free Free Free
Meta-data storage (GB / Month) ¥0.167 N/A N/A N/A ¥0.334 N/A N/A N/A ¥0.418 N/A N/A N/A
*The following API calls are considered iterative write operations: RenameDirectory,RenamePath,RenamePathDir

Data transfer prices for ADLS Gen2

When you write data into GRS accounts, that data will be replicated to another Azure region. The Geo-Replication Data Transfer charge is for the bandwidth of replicating that data to another Azure region. This charge also applies when you change the account replication setting from LRS to GRS or RA-GRS. View the Data transfer prices on Blobs pricing page.

FAQ

Expand all
  • How is Azure Data Lake Storage Gen2 different from Blob Storage?

    Azure Data Lake Storage is optimized for running analytic workloads on unstructured data. Azure Data Lake Storage Gen2 is optimized for fast I/O of high volume data, thereby making analytic workloads run faster and lowering the TCO for analytic jobs. Further, Azure Data Lake Storage Gen2 provides the added flexibility of organizing data either in a flat or hierarchical namespace.

  • What is the different between hierarchical and flat namespaces?

    With hierarchical namespaces, you can organize data into structured folders and directories. With a flat namespace, your files will be organized in a flat structure just like Blob Storage. A hierarchical namespace allows operations like folder renames and deletes to be performed in a single atomic operation, which with a flat namespace requires a number of operations proportionate to the number of objects in the structure. Hierarchical namespaces store additional meta-data for your directory and folder structure. However, as your data volume grows, hierarchical namespaces keeps your data organized and more importantly yields better storage performance on your analytic jobs – thus lowering your overall TCO to run analytic jobs.

  • When should I use a Blob Storage versus Data Lake Storage flat namespaces?

    While Blob Storage and Data Lake Storage with flat namespace are similar in the way data is stored, Data Lake Storage with flat names performs better for analytic workloads. You should put data into Blob Storage, if you are confident that there is no need to run analytics services like Azure Databricks, Azure HDInsight etc. However, if you need to run occasional analytics jobs, you should put such data into Azure Data Lake Storage Gen2 with flat namespaces. For data that will be use constantly for analytics, we recommend that you put such data into Azure Data Lake Storage Gen2 with hierarchical namespaces.

  • Are larger files better than smaller files?

    Yes, larger files are more cost effective and yield better analytic performance. For files > 4MB in size, Azure Data Lake Storage Gen2 offers lower price for every 4MB block of data read beyond the first 4MB. To read a single file that is 16 MB is cheaper than reading 4 files that are 4MB each. In both cases, the total number of transactions are 4. However, the last 12 MB, read as three transactions, from the 16MB file are cheaper, there by making the total cost of reading a 16MB file cheaper than reading 4 files that are 4MB each.

    More importantly, Azure Data Lake Storage Gen2 is highly optimized to perform faster on larger files. This means that your analytics jobs will run faster, when operating on larger files, thus further your TCO for running analytics jobs.

Support & SLA

If you have any questions or need help, please visit Azure Support and select self-help service or any other method to contact us for support.

Azure Data Lake Storage Gen2 itself doesn’t provide financially supported service level agreements. Its availability depends on the used service level for Basic storage. To learn more about the details of the Service Level Agreement, please visit the Service Level Agreements page.