microsoft / microsoft/finops-toolkit

Reservation Savings not visible in v14 Fabric Deployment

Open
#2,181 8 comments 0 reactions 1 assignee View on GitHub

@anshu2813 is already working on this.

Since Jun 16, 2026.

Skill: Data factory Skill: KQL Status: 🕵️‍♀️ Investigating Tool: Fabric Tool: FinOps hubs
Dominant language
PowerShell
Stars
603
Forks
248
Avg merge
7d 11h
Merged PRs (30d)
11

Description

I have deployed v14 of Finops toolkit solution using both ADX and Fabric as Finops Hub.
Since I have started using v14 with ADX in the solution now with the reingestion of the cost export I am able to see the savings from Reservations that we are making.

We also wanted to try the fabric deployment of this solution instead of using ADX Cluster from cost point of view.

Couple of things which I noticed different is when I choose the deployment with Fabric then the ingestion_ExecuteETL pipeline in ForEach Activity Batch count setting values goes to 256 (Is it because I enter 256 as Fabric SKU where we have our Event house deployed) not sure why but when i checked in my ADX deployment of solution I saw that the batch count is set as 1 in the same pipeline. After updating the pipeline I could see the data getting ingested in Fabric deployment. Also we are using fabric capacity from central team instead of deploying fabric sku just for us.

Image

I also see that in the Fabric deployment sometimes the pipeline ingestion_ETL_dataexplorer gets failed due to the activity called Unit Capacity is available as below. Not sure why this is happening is it due to the fabric capacity issue?

Image

Also one most important thing for us which we cannot see when we setup Rate Optimization powerbi report using Fabric Eventhouse URI is the savings from Reservations which is not visible there. When I look at the table then I can see that the Effective Cost in fabric deployment is same as List Cost (Higher than Contracted Cost) whereas in ADX I could see that Effective Cost is less than contracted Cost for the rows where the commitment disount type is Reservation which helps in calculating savings from Reservations.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.