March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early bird discount ends December 31.
Register NowBe one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch now
Today, my company has a GitHub organization, and we are starting to use Microsoft Fabric. I noticed that I can link a Fabric workspace to one of my personal repositories, but I would prefer that this doesn't happen. I would like to limit the interaction of Microsoft Fabric to my company's organization. Is that possible? How can I do it, and what references should I read to better understand this?
Hi @hiran-filho
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet.
In case if you have any resolution please do share that with the community as it can be helpful to others.
Otherwise, will respond back with more details and we will try to help.
Best Regards,
Jing
hi @v-jingzhan-msft and @Tutu_in_YYC
Let me try to explain:
I have a workspace admin in Fabric who, during the integration process, despite being logged into the company’s Fabric account with corporate credentials, mistakenly integrated it with a personal GitHub organization instead of the company's organization.
What I would like to do is restrict the company's Fabric to be integrated only with the company's GitHub organization, to prevent this kind of error from happening.
Is there a way to implement this process?
best regards
Hi @hiran-filho
Sorry I don't find such a setup or configuration in Fabric. Maybe you can try:
What's more, are you using a classic personal access token (PAT) or a fine-grained one? I learned that a classic PAT will grant access to all repositories within the organizations that you have access to, as well as all personal repositories in your personal account. However, a fine-grained PAT allows you to specify more detailed permissions and access controls and it can be restricted to specific repositories and actions within an organization. You may try generating a fine-grained PAT for the Fabric git integration if possible.
Managing your personal access tokens - GitHub Docs
Setting a personal access token policy for your organization - GitHub Docs
In addition, I recommend that you provide a specified repo URL when you add an account.
Hope this would be helpful. If you still have questions, feel free to ask.
Best Regards,
Jing
If this post helps, please Accept it as Solution to help other members find it. Appreciate your Kudos!
Hi @hiran-filho
If your organization don't want to use these Git Integration features, you can disable them in Admin Portal tenant settings. These switches can be enabled by the tenant admin, capacity admin, or workspace admin, depending on your organization's settings.
If you want to limit the Git integration within a workspace, currently only worksapce admins can connect/disconnect a workspace with a repository. When creating a connection, it requires a field Repository URL (optional). If you don't enter a URL, you can connect to any repo you have access to. If you enter a URL, you can only connect to this repository. If you want to connect to GitHub organization only, you can provide a specified repo URL of your Github organization here to avoid seeing your personal repos.
Get started with Git integration - Microsoft Fabric | Microsoft Learn
Best Regards,
Jing
If this post helps, please Accept it as Solution to help other members find it. Appreciate your Kudos!
Here you go. See if this helps
https://learn.microsoft.com/en-us/fabric/cicd/git-integration/intro-to-git-integration?tabs=azure-de...
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
Your insights matter. That’s why we created a quick survey to learn about your experience finding answers to technical questions.
Arun Ulag shares exciting details about the Microsoft Fabric Conference 2025, which will be held in Las Vegas, NV.
User | Count |
---|---|
8 | |
3 | |
2 | |
1 | |
1 |
User | Count |
---|---|
8 | |
6 | |
5 | |
4 | |
4 |