Forum Discussion
Advocate IIFabric workspace git integration
shashiPaul1570_ Apparently, when we try to configure settings by clicking the three dots next to the workspace, we get an error saying, "You need a Premium license for this workspace to continue.".
However, when we open the workspace and attempt to assign it from there, the error doesn't appear. Seems like a UI bug.
Super UserHi Rahel,
Can you send a screenshot of the license tab in the workspace settings?
Are you connected to Azure DevOps, or GitHub?
Can you confirm if the Users can synchronize workspace items with their Git repositories and Users can synchronize workspace items with GitHub repositories switches in the admin portal are on?
If you found this helpful, consider giving kudos. If I answered your question or solved your problem, mark this post as the solution.
- Rahel
tayloramy shashiPaul1570_ Thank you, workspace is assigned to Fabric Capacity (SKU:F64 reserved) and Users can synchronize workspace items with their Git repositories is Enabled.
- shashiPaul1570_
Responsive Resident
Hi Rahel,
Since your workspace is already on Fabric capacity and Git integration is enabled, just note:
Users only need a Pro license to work in the Git-enabled workspace. They don’t need individual Premium licenses as long as the workspace is assigned to Fabric capacity.
Git integration currently supports items like semantic models, dataflows Gen2, notebooks, pipelines, and reports.
Sync is metadata-only — it won’t move Lakehouse data itself.
If you still see “Premium required” messages, double-check in workspace settings that it shows assigned to Fabric capacity, and confirm in the Admin portal that Git integration tenant settings are switched on.
This should ensure Git sync works without additional license errors.
Hope this helps! If it does, a Kudos and Accepted Solution would be awesome.
Thanks
Shashi Paul- Rahel
shashiPaul1570_ Hi I have pro licence and have admin access to the workspace. workspace is assinged F64 capacity and git integration in admin setting is enabled. Strange that it doesn't work.
