The line items your Microsoft partner’s quote leaves out, and why they show up in month four instead of the SOW.
Fabric Lab · Issue 06 · By Dave Goyal
A CFO asked me a fair question last quarter: if the quote said $180K, how did we end up spending $412K in year one. I did not have a clean answer for her on the spot, so I went back and pulled the real numbers across every mid-market Fabric deployment I could get honest data on. Twelve of them. Every one landed at roughly 2.4x the quoted figure. Not close to double. Over double.
Where The Money Actually Goes
None of the eight items below are exotic. None require a bad vendor or a botched project. They are simply the parts of a Fabric migration that a licensing quote does not price.
Parallel running. Keeping the old ERP-reporting stack alive alongside Fabric while the new one gets proven, typically three to six months of double infrastructure and double support.
Viewer licensing below F64. Every plant floor supervisor who opens a Power BI report needs a Pro or Premium Per User license until you cross the F64 threshold. At a few hundred viewers, that number adds up faster than most quotes assume.
The Copilot capacity jump. Copilot in Fabric requires F64 minimum. If the original quote assumed F16 or F32 for BI alone, layering Copilot in later means a capacity jump nobody priced up front.
Reserved capacity bought for peak, run below average. Capacity gets sized for the busiest month, then sits partially idle the other eleven.
Pipeline debugging hours. Data Factory pipelines built fast during the initial build often need real engineering time once they hit production data volumes and edge cases.
Semantic model consolidation. Multiple teams building overlapping models before anyone owns a shared one, then paying to merge them later.
Training, ongoing. Not a one-time cost. Every new hire and every Fabric feature release adds another training cycle.
Change management for business users. The most underestimated line on the list, and the one that stalls adoption longest.
Why This Keeps Happening
None of this is a Microsoft problem or even necessarily a bad-partner problem. A capacity-and-licensing quote is, structurally, a quote for capacity and licensing. It was never going to capture the labor, the overlap period, or the change management. The gap is not deception. It is scope.
The fix is not a better quote. It is a different question asked before signing: not “what capacity do we need,” but “what does the full first year actually cost, including the eight items above, on our numbers.”
What This Means For You
If you are budgeting a Fabric project right now, take the quoted first-year total and model a realistic range of 2x to 2.4x on top of it before you present a number to your board. Presenting the quote as the budget sets up a mid-year surprise that was avoidable.
If you are already six months into a deployment and the bill is running high, check it against the eight line items above before assuming something went wrong. It may simply be the normal shape of a Fabric Year 1, arriving without warning because nobody named it going in.
If your partner’s quote does not itemize licensing math, viewer math, capacity math, and a labor estimate separately, ask for a version that does before you sign.
The One Ask
If you want your own Fabric quote or renewal checked against these eight line items, I am opening a few slots this month for a True Cost of Fabric Migration review: one week, fixed scope, a realistic Year 1 range on your actual numbers.
No pitch at the end. You keep the number whether or not we ever talk again.
Reply here or DM. Which of the eight line items hit you hardest? Tell me in the comments.
I read every reply.
Next issue: The Manufacturer Who Cut Their Power BI Bill In Half. Sometimes the fix costs nothing but an afternoon of license audits.
#MicrosoftFabric #FinOps #ITBudgeting #CIO #DataStrategy
Click here to read this article on Dave’s Demystify Data and AI LinkedIn newsletter.