Moving away from PBIX: I'm documenting a zero-cost CI/CD blueprint for Enterprise Power BI

For a long time, I’ve felt that while Power BI has evolved, many teams are still stuck treating their semantic models like advanced Excel files. Manual deployments are no longer just "slow", they’ve become a hard bottleneck to scalability.

I’ve decided to document my own personal project over the next few weeks: a complete, zero-cost Enterprise Power BI DevOps blueprint. My goal is to apply

code-first software engineering principles to Microsoft Fabric and Power BI.

The architectural shift I’m documenting:

Separation of Metadata vs. Data: Treating schema changes (measures, relationships) as instant metadata operations, completely decoupled from data processing.

Separation of Model vs. Report: Treating the core semantic model as a standalone "data product" that is versioned and deployed independently of the visual layer.

I’m starting this series now and will be posting the architecture, the GitHub Action pipelines, and the XMLA orchestration logic as I build it out.

If you're interested, I can give the link to follow along with the series, in the comments.

But my main focus is, I'm curious to hear from the community here in this subreddit since I've read so many different topics on Power BI for years in this subreddit. I think your opinions would help my journey.

As we move into this "code-first" world for our semantic layers, what is the biggest technical hurdle you’ve faced? Is it the XMLA/Service Principal permissioning, or is it more of a cultural shift in how your teams handle PBIX version control?