Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us at FabCon Vienna from September 15-18, 2025, for the ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM. Get registered
Hi Folks,
I'm currently evaluating the best approach for connecting to our data in a Microsoft Fabric environment and would love to hear the community's thoughts on creating semantic model: dataflow vs direct connection to the warehouse? Thanks 🙂
Solved! Go to Solution.
Hi @RonaldBalza-943,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution I have provided for the issue worked.
If my response addressed, please mark it as "Accept as solution" and click "Yes" if you found it helpful.
Thanks and regards,
Anjan Kumar Chippa
Hi @RonaldBalza-943,
Thank you for reaching out to Microsoft Fabric Community.
It is completely based on the data and your requirement:
Use Direct Connection if you are working with a structured fabric Warehouse, and your data is already clean and ready for modeling and you need the best performance especially for large datasets, then building your semantic model directly on the warehouse is the best approach.
Use the Dataflow’s if you need to perform any custom ETL transformations using power query, and if you are working with the data from multiple sources and if you want to reuse transformation logic across models.
So if your warehouse is your primary and trusted data source, I would recommend creating your semantic model directly on the warehouse. So that you get improved performance and data freshness especially when used with Direct Lake.
If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!
Thanks and regards,
Anjan Kumar Chippa
Hi @RonaldBalza-943,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution I have provided for the issue worked? or let us know if you need any further assistance.
If my response addressed, please mark it as "Accept as solution" and click "Yes" if you found it helpful.
Thanks and regards,
Anjan Kumar Chippa
Hi @RonaldBalza-943,
We wanted to kindly follow up to check if the solution I have provided for the issue worked.
If my response addressed, please mark it as "Accept as solution" and click "Yes" if you found it helpful.
Thanks and regards,
Anjan Kumar Chippa
Hi @RonaldBalza-943,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution I have provided for the issue worked.
If my response addressed, please mark it as "Accept as solution" and click "Yes" if you found it helpful.
Thanks and regards,
Anjan Kumar Chippa
Hi @RonaldBalza-943 ,
Great question—this is a key architectural decision in any Microsoft Fabric implementation, and the right choice often depends on your data modeling needs, performance expectations, and governance strategy.
Pros:
Cons:
Pros:
Cons:
Would be happy to dive deeper into your use case if you can share more about your data volume, refresh needs, or team structure!
Appreciate chat-gpt 😅. Really needed someone that has experience on implementing either one or the other. But hey, thanks for the effort!
Yes, I received support in editing the correct text and adding technical details. Thanks for your feedback though 😊
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Fabric update to learn about new features.
User | Count |
---|---|
55 | |
22 | |
15 | |
10 | |
4 |
User | Count |
---|---|
73 | |
56 | |
17 | |
11 | |
7 |