Billing & Cost Management Guidelines & Best Practices for MS Fabric
Hi Everyone,
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 for demo purpose.
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
0
5 comments
Pallavi Routaray
4
Billing & Cost Management Guidelines & Best Practices for MS Fabric
Learn Microsoft Fabric
skool.com/microsoft-fabric
Helping passionate analysts, data engineers, data scientists (& more) to advance their careers on the Microsoft Fabric platform.
Leaderboard (30-day)
Powered by