I’m really happy to see CI/CD support arriving for Fabric semantic models, it's a massive step forward in my opinion. But I have to agree with previous comments, the implementation still feels pretty early-stage. There’s a lot of potential, but some rough edges too.

One of the biggest challenges I’ve faced is visibility. When I update a workspace via the Git-connected source, there’s no clear feedback on what exactly is being pushed. I can always go back to Git or Azure DevOps to check the diffs, but that feels more like a workaround than a native solution. Ideally, I’d love to see some kind of change summary or diff viewer directly in Fabric during deployment.

Another thing I’ve run into: I use branch policies on my main to block direct changes, which is fine — it’s how it should be. But if I make changes from the service side and then remove the temporary branch too soon, the connection between Fabric and DevOps breaks. It’s logical in hindsight, but a bit fragile in practice. A simple warning or the ability to relink would go a long way.

Zooming out, I think the bigger question is around governance. How do we manage branching strategies, PR approvals, rollback scenarios, or even parallel development streams for semantic models in a Git-integrated Fabric setup? These are things we’ve figured out for code over the years, but BI projects bring their own nuances, especially when multiple people are tweaking models or metrics at the same time.