Fabric workspace git integration

[Rahel]

Hello Fabrican's,
If the workspace is assigned as a Fabric workspace, why does it display the message 'You need a Premium license for this workspace to continue' when attempting Git integration?

[Rahel · Accepted solution]

@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.

[shashiPaul1570_]

Hi @Rahel,

Good catch — this does look like a UI bug. Using the ellipsis  shows the “Premium license required” error, but configuring Git from inside the workspace settings works fine.

For now, use the workspace settings path as the workaround, and I’d suggest flagging it in your support ticket so the Fabric team can address the UI issue.

Best regards,
Shashi Paul

[Rahel]

@tayloramy @shashiPaul1570_    Thank you we will open support ticket.

[shashiPaul1570_]

Hi @Rahel,

Perfect 👍 — opening a support ticket is the right next step here. The Fabric support team can check the backend provisioning for Git integration directly.

It would be great if you could share the outcome back here once it’s resolved — that way others running into the same issue can benefit from your experience.

Best of luck, and I’m glad we could narrow this down together!

Best regards,
Shashi Paul

[Rahel]

@shashiPaul1570_ Sure I will loop back here once I have an update. Hopefully the Fabric team can shed some light on what’s going on behind the scenes. Appreciate your help in narrowing this down it’s been super useful!

[shashiPaul1570_]

Really glad I could help narrow things down with you — appreciate the kind words! 🙏

[tayloramy]

@Rahel If those are enabled in the admin portal and the workspace is on a F-sku capacity, Git should work. 

Despite the banner, are you able to configure Git? 

Perhaps this is just an interface bug? 

If you found this helpful, consider giving kudos. If I answered your question or solved your problem, mark this post as the solution. 

[shashiPaul1570_]

Hi @Rahel,

That banner appears when the workspace isn’t on a qualifying capacity for Git (or tenant Git is disabled).

What’s required:

1. Capacity

• Fabric Git integration needs the workspace on Fabric capacity (F-SKU). Power BI Premium capacity can work, but some SKUs only support Power BI items—not all Fabric items. A Pro (non-capacity) workspace will show the “need Premium” message. 

https://learn.microsoft.com/en-us/fabric/cicd/git-integration/git-get-started?utm_source=chatgpt.com...

• Microsoft also notes you must have a valid Premium license/capacity to connect to repos. Microsoft Learn

1. Admin/Tenant switches

• In Admin portal, enable the Git integration tenant settings (Azure DevOps/GitHub). 

• https://learn.microsoft.com/en-us/fabric/cicd/git-integration/license-change?utm

1. Permissions

• You must be Workspace Admin, and the target workspace must have capacity (no template apps). 

Quick checks

• Workspace → Settings → Premium/Fabric: it should show Assigned to capacity: Fxx (not Pro).

• Admin portal → Tenant settings → Git integration: enabled.

• Try again from the workspace’s Git integration pane.

If your workspace is on PPU or Pro, switch it to an F-SKU capacity, or use a Premium capacity that supports the items you’re trying to version. That removes the banner.

Hope this helps! If it does, a Kudos and Accepted Solution would be awesome.

Thanks
Shashi Paul 

[tayloramy]

Hi @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  connected to Azure DevOps

[tayloramy]

@Rahel It appears that you have does all the right things. 

If you ignore the banner warning, does GIt work and sync the workspace? 

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 I wouldn’t mind the banner if it actually worked but it doesn’t, and I can’t proceed:

[tayloramy]

@Rahel in that case I recommend opening a support ticket. 
Seems like something is not provisioned properly in your tenant. 

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_]

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.

[shashiPaul1570_]

Hi @Rahel,

Thanks for confirming the details. Since you have a Pro license, Admin rights, F64 capacity, and Git integration enabled, a couple more things to check:

Propagation delay — After enabling Git integration in the Admin portal, it can take ~30 minutes to propagate. Try logging out, clearing browser cache, or testing in a private/incognito window.

Repo permissions — Make sure you have contributor rights in the target Azure DevOps/GitHub repo you’re connecting to. Without this, the error can appear even if the workspace is on Fabric capacity.

Workspace type — Git integration works only on Fabric workspaces, not “My Workspace” (personal).

Connection path — Go to Workspace settings → Git integration → Connect, and enter the repo details there.

1. If all looks good and it still fails, I’d recommend opening a Microsoft support ticket. There are some cases where the backend Git integration provisioning doesn’t complete properly even though the toggle is on.
   (https://support.fabric.microsoft.com/?utm)

That should help narrow it down. 🙌

If this helps, please give a Kudos 👍 and mark as Accepted Solution ✅ so others can benefit.

Best regards,
Shashi Paul