Microsoft has introduced a powerful new capability in Microsoft Fabric that helps organizations reduce long-term storage expenses while maintaining compliance and accessibility requirements. The new OneLake storage tiers and lifecycle management features, currently in preview, give administrators greater control over how data is stored and managed over time.
As organizations continue to accumulate massive volumes of analytical and historical data, storage costs can grow rapidly. Many businesses are required to retain data for years due to auditing, governance, or regulatory obligations, yet much of that data is rarely accessed after its initial use. Microsoft’s new OneLake enhancements are designed to address this challenge by enabling automatic movement of data into more cost-effective storage tiers.
Understanding OneLake Storage Tiers
OneLake now supports three distinct storage tiers, each optimized for different access patterns and cost considerations:
Hot Tier – Designed for frequently accessed and active data workloads.
Cool Tier – Intended for infrequently accessed data where lower storage cost is prioritized.
Cold Tier – Optimized for long-term archival and retention at the lowest storage price point.
Currently, all existing OneLake data resides in the hot tier by default. Organizations can now move files between tiers manually, assign tiers during upload, define workspace-level defaults, or automate the process entirely using lifecycle management policies.
While cool and cold storage significantly reduce storage expenses, they also introduce higher transaction and retrieval costs compared to the hot tier. This creates a strategic balance between cost savings and access performance.
Automating Storage Optimization with Lifecycle Management
A major highlight of the update is the introduction of lifecycle management policies. These policies allow administrators to automate tier transitions based on customizable rules such as:
File creation date
Last modification date
Last access date
For example, organizations can configure policies to:
Move files not modified in 30 days to the cool tier.
Transfer files inactive for 90 days into the cold tier.
Automatically return files to the hot tier when they are accessed again.
This automation ensures that storage costs are continuously optimized without requiring manual intervention. It also aligns storage strategies with real-world data usage patterns.
Real-World Cost Savings Example
Microsoft demonstrated the potential financial impact using a scenario involving 10TB of historical bronze-layer data stored over five years. According to the example:
Join the conversation! Your thoughts help the community grow.