Forum Discussion
Unexpected High Cost for Dataflows Standard Compute Despite Using Reserved F32 Capacity
Hi Parthiban006,
Coming to your "Has this separate billing for Dataflows Gen2 always been around, or is it new?" query, Dataflows Gen2 has always been billed separately from reserved Fabric capacity (F-SKUs). It’s not a recent change but it’s simply how the model has worked from the start, even if that wasn’t always obvious in pricing summaries or calculators.
Kindly go through the below links to get a better understanding of how Dataflow is billed.
Pricing for Dataflow Gen2 - Microsoft Fabric | Microsoft Learn
Data Factory Pricing - Microsoft Fabric | Microsoft LearnPricing for data pipelines - Microsoft Fabric | Microsoft Learn
Now coming to "Why doesn't the Azure Pricing Calculator or most Microsoft docs explicitly show this?" query, You’re right most documentation focuses on general Compute and Storage for Fabric, without clearly calling out that Dataflow Gen2 incurs its own compute charges.
I suggest you to go through a official Microsoft source "Fabric Operations” which shows the billing meter used for Dataflow Gen2. Under the Data Factory section, it lists "Dataflow Gen2 Refresh -> billed via “Dataflows Standard Compute Capacity Usage CU”. These operations are categorized under Fabric, but charged separately. Fabric operations - Microsoft Fabric | Microsoft Learn
That wording directly confirms that Dataflow Gen2 refreshes are metered independently of your reserved F-SKU capacity even though they appear alongside Fabric in billing breakdowns.
Best Regards,
Hammad.
Hi Anonymous,
Thanks a lot for the detailed explanation it really helped clarify the billing behavior.
I have a follow-up question regarding the timeline and transparency of this pricing model:
- Is this separate metering and billing for Dataflow Gen2 something that has been in place since the beginning of Fabric, or is it a recent change?
- The Azure Pricing Calculator and most official Microsoft documentation still mention only Compute and Storage as the primary cost components for Fabric. If Dataflow Gen2 is billed separately from Fabric capacity, shouldn't this be explicitly mentioned in the pricing documentation or calculator?
Could you kindly share a link to the official Microsoft documentation that clearly states that Dataflow Gen2 compute is billed separately from Fabric capacity (F-SKU)? This would help me and others in the community better plan and optimize workloads.
Thanks again for your support!
Hi Parthiban006,
Coming to your "Has this separate billing for Dataflows Gen2 always been around, or is it new?" query, Dataflows Gen2 has always been billed separately from reserved Fabric capacity (F-SKUs). It’s not a recent change but it’s simply how the model has worked from the start, even if that wasn’t always obvious in pricing summaries or calculators.
Kindly go through the below links to get a better understanding of how Dataflow is billed.
Pricing for Dataflow Gen2 - Microsoft Fabric | Microsoft Learn
Data Factory Pricing - Microsoft Fabric | Microsoft Learn
Pricing for data pipelines - Microsoft Fabric | Microsoft Learn
Now coming to "Why doesn't the Azure Pricing Calculator or most Microsoft docs explicitly show this?" query, You’re right most documentation focuses on general Compute and Storage for Fabric, without clearly calling out that Dataflow Gen2 incurs its own compute charges.
I suggest you to go through a official Microsoft source "Fabric Operations” which shows the billing meter used for Dataflow Gen2. Under the Data Factory section, it lists "Dataflow Gen2 Refresh -> billed via “Dataflows Standard Compute Capacity Usage CU”. These operations are categorized under Fabric, but charged separately. Fabric operations - Microsoft Fabric | Microsoft Learn
That wording directly confirms that Dataflow Gen2 refreshes are metered independently of your reserved F-SKU capacity even though they appear alongside Fabric in billing breakdowns.
Best Regards,
Hammad.