top of page

OneLake storage pricing in Microsoft Fabric: $0.026 per GB and a 5 TB example

6 minutes ago
8 min read
Cover showing the title OneLake storage pricing in Microsoft Fabric with a 5 TB example on a teal data skyline. Data Studios original cover

OneLake storage in Microsoft Fabric is billed separately from the capacity you buy. Microsoft's documentation states that OneLake storage "is billed at a pay-as-you-go rate per GB of data used and doesn't consume Fabric Capacity Units (CUs)", so an F2 or F64 capacity covers compute while every gigabyte in a lakehouse or warehouse adds its own line to the Azure bill. In the East US region, Microsoft's Azure retail price list shows $0.026 per GB per month for OneLake hot storage, $0.019 for cool, $0.004 for cold and $0.2 for OneLake cache, all checked on November 22, 2026.


Two settings change the storage bill more than anything else: disaster recovery, which moves data to the more expensive BCDR storage meters, and the storage tier assigned to files. For a 5 TB lakehouse kept entirely in hot storage, the published rates give $130.00 a month. The same data with disaster recovery enabled costs $234.00 a month, and a tiered layout with most historical data in cool and cold storage brings the base figure down to $64.50.


The storage meter keeps running when a capacity is paused. Microsoft's consumption page says that "when a capacity is paused, the data stored continues to be billed using the pay-as-you-go rate per GB", which is the first surprise for teams that pause an F SKU at night to save money.


··········


ONELAKE STORAGE PRICES BY TIER IN EAST US.


The figures below come from Microsoft's Azure retail prices API for the Microsoft Fabric service in the eastus region, filtered on the OneLake product, as listed on November 22, 2026. All are in USD with the unit "1 GB/Month". The public Fabric pricing page showed placeholders instead of prices when checked, so the API is the source for every number here. Prices vary by region, and teams outside East US should look up their own region before budgeting.


........


OneLake meter

Billed for

USD per GB per month

OneLake Storage Hot

Default tier for all data

0.026

OneLake Storage Cool

Files set to cool (30-day minimum)

0.019

OneLake Storage Cold

Files set to cold (90-day minimum)

0.004

OneLake BCDR Storage Hot

Hot data with disaster recovery on

0.0468

OneLake BCDR Storage Cool

Cool data with disaster recovery on

0.0342

OneLake BCDR Storage Cold

Cold data with disaster recovery on

0.0085

OneLake Cache

KQL cache and Data Activator retained data

0.2

Storage Mirroring

Mirrored data above the free allowance

0.026

Storage Mirroring Free

Mirrored data within the free allowance

0.0


........


The BCDR meters cost 1.8 times the regular rate for hot and cool data and about 2.13 times for cold data. The cache meter applies, according to the footnote on Microsoft's Fabric pricing page, to KQL cache storage and Data Activator retained data, and it is not affected by hot, cool or cold tiering or by disaster recovery coverage. The storage meters apply to data that Fabric items such as lakehouses, warehouses and mirrored databases keep in OneLake.


··········


HOW ONELAKE STORAGE BILLING WORKS WITH FABRIC CAPACITY.


A Fabric capacity bill has two separate parts. Compute is the F SKU, billed per capacity unit hour; the base meter in the same price list is $0.18 per CU hour in East US, which puts an F2 running all month (730 hours) at $262.80, a figure compared in more detail in our article on Power BI Embedded A SKUs vs Fabric F SKUs. Storage is the OneLake meter, billed per GB per month whether or not the capacity is running.


Transactions sit between the two. Microsoft's capacity consumption page states that "OneLake doesn't include a separate charge for transactions (for example, reads, writes) to your data"; reads and writes consume capacity units from the F SKU instead. When a capacity is paused, Microsoft says all transactions to it are rejected, so no CUs are consumed, but the stored data keeps accruing storage charges.


Soft delete adds a smaller, often forgotten amount. The OneLake recovery page, last updated October 2, 2026, says OneLake "retains deleted files for seven days before permanent removal" and that "you pay for soft-deleted data at the same rate as active data." Pipelines that overwrite large tables every day therefore carry up to a week of deleted files on the storage bill.


Mirroring is the one storage cost the capacity partly absorbs. Microsoft's pricing page lists free mirroring storage for replicas that scales with the SKU: 2 TB with F2, 8 TB with F8, 64 TB with F64 and so on up to 8,192 TB with F8192. Mirrored data above that allowance is billed at the Storage Mirroring rate of $0.026 per GB per month in East US.


··········


ONELAKE HOT, COOL AND COLD TIERS: RETENTION RULES AND RETRIEVAL CUS.


Microsoft's OneLake storage tiers page, last updated June 3, 2026, says that "all workspaces in Fabric start with a default tier of Hot." Administrators can change the workspace default, set a tier per file through the blob APIs (Set Blob Tier, Copy Blob, or the access-tier header on upload), or define lifecycle management rules that move files between tiers automatically. The page adds that OneLake only supports changing the tier of files that are fully billable, and only for block blobs.


Cheaper tiers come with conditions. Cool storage has a minimum retention of 30 days and cold storage a minimum of 90 days, and files deleted, overwritten or moved to another tier before that period are subject to an early deletion penalty. Files in a soft-deleted state are exempt from that penalty. Reading from cool or cold storage also has a cost: the consumption page lists OneLake data retrieval at 200 CU seconds per GB for cool and 600 CU seconds per GB for cold, with no retrieval charge for hot.


Retrieval is charged in capacity units, so it competes with reports and notebooks for the same F SKU. Reading 500 GB from cold storage in a month uses 300,000 CU seconds, or 83.33 CU hours, which is worth $15.00 at the $0.18 pay-as-you-go rate. The same read from cool storage uses 27.78 CU hours, or $5.00. Tables that Power BI reports query every day belong in hot storage; closed fiscal years and raw landing files that are rarely read are the natural candidates for cool and cold.


··········


ONELAKE DISASTER RECOVERY: WHAT BCDR STORAGE ADDS.


Disaster recovery is a capacity-level switch. Microsoft's OneLake disaster recovery page, last updated October 23, 2026, says "you can enable or disable disaster recovery (DR) for a specific capacity through the capacity admin portal", that the secondary region cannot be modified, and that enabling it "might take an extended period of time." Once it is on, OneLake data is geo-replicated and, in the words of the consumption page, "the storage is billed as Business Continuity and Disaster Recovery (BCDR) Storage."


The cost of that switch has two parts. Storage moves to the BCDR meters listed above, and Microsoft states that write operations consume more capacity units when disaster recovery is enabled for a capacity. Teams with several capacities can keep disaster recovery on the production capacity that holds certified data and leave it off for development and sandbox capacities, since the setting is per capacity.


··········


ONELAKE COST EXAMPLE FOR A 5 TB LAKEHOUSE.


The example below is illustrative. It assumes a lakehouse of 5,000 GB in East US, 100 GB of tables overwritten every day (so about 700 GB sits in soft delete at any time), 50 GB of KQL cache for an eventhouse, and no mirrored data. The tiered layout keeps 1,000 GB in hot, 1,500 GB in cool and 2,500 GB in cold. All amounts are monthly and were computed in Python from the published rates.


........


Scenario

Storage layout

Monthly USD

A

5,000 GB hot, no DR

130.00

B

5,000 GB hot, DR on

234.00

C

1,000 hot, 1,500 cool, 2,500 cold, no DR

64.50

D

Same tiers as C, DR on

119.35

Add-on

700 GB soft-deleted at hot rate

18.20

Add-on

50 GB OneLake cache

10.00

A with add-ons

Hot, no DR, soft delete and cache

158.20

C with add-ons

Tiered, no DR, soft delete and cache

92.70


........


Scenario C costs $65.50 less than scenario A each month, a 50.4% reduction, and $786.00 less over a year ($774.00 against $1,560.00). Turning on disaster recovery for the all-hot layout adds $104.00 a month. Scenario C splits into $26.00 for hot data, $28.50 for cool and $10.00 for cold, so the cool tier ends up as the largest line even though it holds less data than cold.


The calculation is short enough to rerun with a team's own volumes and regional prices:


prices = {"hot": 0.026, "cool": 0.019, "cold": 0.004,
          "bcdr_hot": 0.0468, "bcdr_cool": 0.0342, "bcdr_cold": 0.0085,
          "cache": 0.2}
layout = {"hot": 1000, "cool": 1500, "cold": 2500}  # GB
dr_enabled = False
soft_deleted_gb = 100 * 7   # daily overwrites kept for seven days
cache_gb = 50

prefix = "bcdr_" if dr_enabled else ""
storage = sum(gb * prices[prefix + tier] for tier, gb in layout.items())
soft = soft_deleted_gb * prices[prefix + "hot"]
cache = cache_gb * prices["cache"]
print(f"storage {storage:.2f}  soft delete {soft:.2f}  cache {cache:.2f}  total {storage + soft + cache:.2f}")

With the values shown, the script prints a total of $92.70, matching the last row of the table. It does not include the capacity units consumed by retrieval from cool and cold storage or by writes, which come out of the F SKU rather than the storage bill. The comparable storage decision on Google Cloud is covered in our article on BigQuery logical vs physical storage billing.


··········


COMMON MISREADINGS OF ONELAKE STORAGE COSTS.


Pausing a capacity does not stop storage billing. Microsoft's documentation is explicit that stored data continues to be billed per GB while the capacity is paused, so a trial or a paused development capacity with a large lakehouse still generates charges; the end-of-trial rules are covered in our piece on the Microsoft Fabric free trial and the move to a paid capacity.


Storage is not included in the F SKU price, except for the mirroring allowance. The free mirroring storage scales with the SKU, but it applies only to mirrored replicas. Lakehouse tables loaded by pipelines, notebooks or dataflows are billed at the regular OneLake rates.


Deleting data does not remove it from the bill immediately. Soft-deleted files are billed at the active rate for seven days, and files removed from cool or cold storage before 30 or 90 days trigger the early deletion penalty described on the tiers page.


Cheaper tiers are not free to read. Every GB read from cool or cold storage consumes capacity units at the retrieval rates in the consumption documentation, and that consumption is drawn from the same capacity that runs reports and notebooks.


··········


ONELAKE STORAGE PRICING: WHAT TO CHECK IN YOUR TENANT.


Microsoft publishes the OneLake storage rates per GB per month, the BCDR storage rates, the seven-day soft delete period, the 30-day and 90-day minimums for cool and cold storage, and the retrieval rates in CU seconds per GB. For a 5 TB lakehouse in East US those figures put the monthly storage bill between $64.50 and $234.00 depending on tiering and disaster recovery, before soft delete and cache.


The amounts that depend on each tenant are the region of the capacity, whether disaster recovery is enabled on it, the default tier of each workspace and any lifecycle rules, and how much data is overwritten daily. Microsoft's documentation does not give a dollar figure for the early deletion penalty or state a release status for the storage tiers feature, and the public pricing page did not display prices during this check, so the Azure pricing calculator and the Cost Management view of the subscription are the places to confirm what a specific capacity is being charged. Teams comparing Fabric with Power BI licenses alone can start from our breakdown of Power BI Pro vs Premium Per User vs Fabric F64.


··········


FOLLOW US FOR MORE.


·····


DATA STUDIOS


·····


datastudios.org


bottom of page