Billing & Cost Management Guidelines & Best Practices for MS Fabric

[pallavi_r]

Dear Team,

I need help here with respect to guidelines on cost management for Fabric Resource Usage & Computation.
We are starting a project with a low Fabric Capacity.
The volume of the data will not be heavy but these are the basic features will be implemented.
1. Medallion Architecture
2. Spark notebook execution for data transformation
3. pull data with Dataflow gen 2
4. Create data factory pipeline
5. Use ML model for prediction and forecasting
6. Build power bi report (by Pro users)
Can we use F2 capacity to achieve all these.

Can anyone please help me with what are guidelines to keep cost in control so that it does not spike in Azure cost due to computation.
For example what components can be paused or a particular component/feature that incurs a lot compared to other component.
Asking this as I need to be careful with cost and billing while working on actual project.

Please help if you anyone has worked on billing and cost management factor on Fabric Capacity.

Hope my question is clear or I can elaborate my problem statement further.

Thanks,
Pallavi

[pallavi_r]

Thanks @Greg_Deckler , will check all these and get back. Thank you.

[Greg_Deckler]

@pallavi_r 

Yes, every Fabric capacity has all of the same workloads.

Make sure to turn off any auto-scaling features and turn your capacity off when not using it.

Evaluate and optimize your Microsoft Fabric capacity - Microsoft Fabric | Microsoft Learn

Pause and resume your capacity - Microsoft Fabric | Microsoft Learn