Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!View all the Fabric Data Days sessions on demand. View schedule
In our environment we use a multitude of dataflows and want to leverage enhanced compute as we have plenty of premium capacity at the moment. The problem is that we don't place dataflows into the same workspace because of the fact that we need to separate scheduling of dataflows (when a dataflow has a linked table it will forcibly refresh that table, even if the source fails). What we're noticing is that we're not netting any benefit from our model when we link tables from ingestion dataflows to our computed dataflows and leverage computed tables. The model which was suggested to us to use by MSFT is one whereby we have a workspace for ingestion and/or staging dataflows, one for cleansing and ETL dataflows, and specific workspaces for ETL processing on the dataflows that we need to feed from.
The documentation for this purposes is very vague when it comes to separated workspaces and enhanced compute. Keep in mind they're all running on the same capacity, but when it comes to where Power BI places the data into an Azure SQL repository is that separated per workspace? I know Matthew Roche has blogs on this and MSFT has documentation, but none of it pertains to separate workspaces... only in one workspace. Can anyone clarify how we can make this work if it even will work?
Hi @cvillegas ,
I can't find any documents that clarify it. But we enable Enhanced Compute on the power bi premium that dataflows in all workspace that holds in premium capcity will benifit from it.
>>The model which was suggested to us to use by MSFT is one whereby we have a workspace for ingestion and/or staging dataflows, one for cleansing and ETL dataflows, and specific workspaces for ETL processing on the dataflows that we need to feed from.
You can also create link entity across workspace . Refresh for links from entities in different workspaces behaves like a link to an external data source. When the dataflow is refreshed, it takes the latest data for the entity from the source dataflow. If the source dataflow is refreshed, it doesn't automatically affect the data in the destination dataflow.
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Best Regards,
Dedmon Dai
Check out the November 2025 Power BI update to learn about new features.
Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!