Forum Discussion
Helper IPower BI Workspace git integration
I was under the impression that connecting a workspace to git only was allowed if the workspace was assigned to a fabric capacity.
I was testing git integration out with a workspace backed by a fabric trial capacity and it was all good.
Then I looking through workspace settings for a PPU workspace and the git options were available, which I thought was odd. I tried it and it worked as well!
We don't currently license Fabric, but git integration is a desired capability that I want to use. Now I'm wondering if I have just stumbled on to a mistake or if git integration was quietly released to PPU.
Get started with Git integration - Microsoft Fabric | Microsoft Learn
"To access the Git integration feature, you need a Fabric capacity."
It's not a mistake.
Power BI implementation planning: Integration with Other Services - Power BI | Microsoft Learn
If your workspace uses Fabric capacity, Premium capacity, or PPU license modes, you can use Git integration to connect a workspace to a remote Git repository to support more advanced lifecycle management scenarios.
3 Replies
- AlexisOlson
Super User
It's not a mistake.
Power BI implementation planning: Integration with Other Services - Power BI | Microsoft Learn
If your workspace uses Fabric capacity, Premium capacity, or PPU license modes, you can use Git integration to connect a workspace to a remote Git repository to support more advanced lifecycle management scenarios.
- Greg_Deckler
Community Champion
mattcarter865 I'm not surprised that this worked. PPU gave you "Premium" features back when was just Power BI. PPU basically kind of provisioned you a premium capacity effectively. When Fabric came along, everyone that was Premium got Fabric. So you "sort of" have a Fabric capacity when you are using PPU more or less. The lines are really blurry these days.
rohit1991It sounds like your workspace is already assigned to a Git-enabled workspace connection, but it’s not letting you disconnect or view the Git option anymore.
Could you please check the following:
-
The workspace was previously connected to a Git repository and was later converted to a non-Git-enabled state for example, if the Premium license changed or settings were reverted.
-
There are residual Git metadata bindings that weren’t properly cleared.
There are few suggestions which i would like to raise :
-
Check if your workspace is still in a Premium or Fabric capacity Git integration only works with those.
-
Go to the deployment pipeline settings (if used) and see if any source control options are still referenced.
-
