MC1259829: Changes to OneLake operation reporting in Microsoft Fabric
Microsoft Fabric's OneLake introduces storage tiers (hot, cool, cold) and updates operation reporting by including tier names, consolidating proxy/redirect operations, and grouping by workspace in the Capacity Metrics app. Billing rates remain unchanged. Changes start April 1, 2026; item-level de...
[Introduction]
We're introducing OneLake storage tiers (hot, cool, and cold) in Microsoft Fabric. As part of this rollout, we are updating how OneLake compute operations appear in your capacity billing. These updates improve clarity and align reporting with the new storage tier model. There is no change to billing rates.
Key updates include
- Operation names include the storage tier. For example, “OneLake Read via Proxy” becomes “OneLake Read (Hot).”
- Proxy and Redirect operations are consolidated. Operations previously reported separately will appear under a single operation name. Because consumption rates are the same, this has no billing impact.
- Operations are reported at the workspace level. A new OneLake item in the Fabric Capacity Metrics app groups operations by workspace instead of individual items. For item-level detail, use OneLake diagnostics to understand usage across Fabric and non-Fabric workloads.
Units of measure and consumption rates remain unchanged.
[When this will happen]
- Operation name updates begin April 1, 2026.
- Operation consolidation and Metrics app updates will roll out over the following weeks.
[How this affects your organization]
Who is affected
- All organizations using Microsoft Fabric with OneLake storage and capacity billing
What will happen
- Operation names will include the applicable storage tier (for example, “Hot”):
- Proxy and Redirect operations will appear under a single consolidated operation name:
- OneLake operations will be grouped by workspace under a new OneLake item in the Fabric Capacity Metrics app.
- Item-level compute reporting will move to OneLake diagnostics.
The following example illustrates how the report now appears:
There is no change to billing rates or your total costs.
Operation name changes:
[What you can do to prepare]
- Review any custom analytics or automation. Update operation names in reports, dashboards, and scripts to align with the new naming convention before April 1, 2026.
- Plan for workspace-level reporting. If you rely on item-level operation details in the Capacity Metrics app, configure OneLake diagnostics to maintain that granularity.
- Review the documentation for OneLake compute consumption in Microsoft Fabric.
- Share with your helpdesk and reporting teams if they monitor capacity or cost analytics.
No other action is required.
Learn more:
- Install the Microsoft Fabric capacity metrics app | Microsoft Fabric | Microsoft Learn
- OneLake compute and storage consumption | OneLake | Microsoft Fabric | Microsoft Learn
- OneLake diagnostics | OneLake | Microsoft Fabric | Microsoft Learn
- OneLake storage tiers - Microsoft Fabric Roadmap
- OneLake, the OneDrive for data | OneLake | Microsoft Fabric | Microsoft Learn
[Compliance considerations]
No compliance considerations identified. Review as appropriate for your organization.
[Support]
For assistance, contact your Microsoft account team or visit Microsoft Fabric support.