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!Learn from the best! Meet the four finalists headed to the FINALS of the Power BI Dataviz World Championships! Register now
I have used PBIX files in Source control before but it never seemed to really work well. I published from Power BI desktop and that worked ok for a small number of data sets and reports.
I am looking for a good way to use source control (be able to see and understand the changes) and br able to deploy to non premium workspace (this may be Pro workspace or PPU workspace)
Previously the production workspace for deployment pipelines required a premium workspace.
Is this still true for Fabric workspaces? Is there anydownaside to useing PBIP Project structure? Can you deploy to a non premium Fabric workspace?
I cant seem to find any clear info
Thanks
Look into saving your Power BI work in a pbip file (it really a set of files) and use the TMDL option. It is in Preview, but this is the way forward from Microsoft on SourceControl.
TMDL in Power BI Desktop developer mode (Preview) | Microsoft Power BI Blog | Microsoft Power BI
There are others in the community sharing alot of information on this topic - Support for TMDL | pbi-tools
Thanks.
That seems half of the puzzle. But the deployment?
I want to be able to push from source control programatically to potentially multiple workspaces.
I dont want the fabric workspace to pull from Source Control (IT to push, users to admin their workspace)
Wonder why PBIP has been in preview for so long?
Thanks
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Check out the February 2026 Power BI update to learn about new features.