Forum Discussion
Git integration when Fabric disabled
Hi all,
Could anyone confirm whether Git integration is supported for Power BI items when Fabric is disabled at the tenant level? I’ve come across conflicting information.
Based on my testing in two separate Fabric tenants with a Fabric capacity—where Fabric is disabled at both the tenant and capacity levels (the “Users can create Fabric items” setting is turned off)—Git integration works as expected for Power Bi items.
Based on Microsoft’s official documentation, this configuration should not be supported.:
Git integration admin settings - Microsoft Fabric | Microsoft Learn
That said, another Microsoft page indicates that Git integration works on Premium capacities or with a PPU license, without explicitly listing the Fabric admin switch as a prerequisite:
Power BI implementation planning: Integration with Other Services - Power BI | Microsoft Learn
I’m interested to hear what others have observed in practice.
Hi MDBI ,
Thanks for reaching out to Microsoft Fabric Community.
One possible way to look at this is that the Git integration admin settings page is primarily describing Git integration in the context of Fabric workloads. In the documentation, the reference to the Fabric admin switch appears to apply to items such as Lakehouse, Warehouse, Notebooks, and Dataflows Gen2, where disabling Fabric at the tenant level would also prevent Git integration for those items.
Power BI items seem to be treated slightly differently. Git integration for Power BI reports and semantic models is documented as being tied to Premium capacity or a PPU license, and the Fabric creation setting is not explicitly listed as a prerequisite. This could explain why Git integration continues to be available for Power BI items even when the “Users can create Fabric items” setting is turned off.
That said, since this distinction is not clearly spelled out in the documentation, if you need an official confirmation on whether this behavior is fully supported or subject to change, raising a Microsoft support ticket would be the best way to get a definitive clarification from the product team.
Similar threads for Reference:
Solved: Git integration without Fabric capacity - Microsoft Fabric Community
Solved: Power BI - Git integration - Microsoft Fabric Community
Hope this helps. Please reach out for further assistance.
Thank you.
9 Replies
I think your confusion comes from second documentation but if you have premium capacity then you can use Fabric features - bascially a P1 can support all the features of F64 including git integration.
Hi MDBI ,
Thanks for reaching out to Microsoft Fabric Community.
One possible way to look at this is that the Git integration admin settings page is primarily describing Git integration in the context of Fabric workloads. In the documentation, the reference to the Fabric admin switch appears to apply to items such as Lakehouse, Warehouse, Notebooks, and Dataflows Gen2, where disabling Fabric at the tenant level would also prevent Git integration for those items.
Power BI items seem to be treated slightly differently. Git integration for Power BI reports and semantic models is documented as being tied to Premium capacity or a PPU license, and the Fabric creation setting is not explicitly listed as a prerequisite. This could explain why Git integration continues to be available for Power BI items even when the “Users can create Fabric items” setting is turned off.
That said, since this distinction is not clearly spelled out in the documentation, if you need an official confirmation on whether this behavior is fully supported or subject to change, raising a Microsoft support ticket would be the best way to get a definitive clarification from the product team.
Similar threads for Reference:
Solved: Git integration without Fabric capacity - Microsoft Fabric Community
Solved: Power BI - Git integration - Microsoft Fabric Community
Hope this helps. Please reach out for further assistance.
Thank you.
