Forum Discussion
Advocate IWorking in git as a team and project submission
you won't have much fun trying it this way.
you could try to create multiple branches and connect each branch to a separate workspace, assuming that all users are full members in the same tenant (not guest accounts) and have repo admin rights as well (full users, not stakeholders). but... merging the branches is going to be a nightmare. it simply does not work as nice as it does in synapse or ADF for that matter.
I recommend following
1) all team members work in the same workspace on different components (that's the way we're handling it in our team)
2) each team member works in their own workspace and their own repo (assuming all team member are from the same tenant and have a full license (basic) and have contribute permissions to the devops project.
in any case keep following in mind:
Git integration in Fabric is still in beta. more than half the object types are not supported (Dataflow Gen 2, Pipelines, Default Semantic Models, Direct Lake semantic models, Lakehouse configurations, warehouses, KQL Databases, Real time Analytics Endpoints, Event Streams, KQL Query Sets, etc)
So there is currently very little benefit from hooking up git directly to the workspace, unless you only plan on working on notebooks, reports and semantic models.
Advocate IHi,
Update on Azure git in Fabric - it doesn't seem to work :)). we created accounts for each team member with the same credentials as for fabric and created organizations to be able to connect form Fabric. One team member was able to connect to the created project - but for the rest of us - there-s no organisation in the Git provider... even if we have our created organization and that one created by our colleague where we're added as users.
what is wrong with Azure DevOps git and Fabric? :))
A few things to consider:
Azure Devops integration with fabric only works for one single tenant. all workspace admins should be in the same tenant.
When one admin sets up the sync, nobody else should need to setup sync anymore. it happens at workspace level and once configured is triggered by the sync button.
Anybody who wants to work with a Git Repo in Azure Devops needs a Basic or VSEnterprise license. Stakeholder is not enough. Again, having the workspace admin set up the sync should be enough.
Question is: what are you trying to achieve? hooking up a single workspace with a git repo in Azure Devops is normally quite simple and only requires one person to have enough rights to setup. I have the feeling you're trying something more complex.
- cmiroslav
The idea was to use a repo created by one team member using his/hers Fabric account where we would add the other two members as users to work on different branches and to combine our work in a main branch.
One of us created an organization in his/her Azure DevOps account, added to his/her workspace and added us as users. We could see that project in our Azure account. Next we tried to connect to the organization created by that team member, but no organization was in the drop-down list.
Also we tried to create an organization in our Azure DevOps account, with an initialized project inside to connect to our workspace in fabric, but even this way - no organization is in the dropdown list.
Can we use a repo in this way?
Thank you
you won't have much fun trying it this way.
you could try to create multiple branches and connect each branch to a separate workspace, assuming that all users are full members in the same tenant (not guest accounts) and have repo admin rights as well (full users, not stakeholders). but... merging the branches is going to be a nightmare. it simply does not work as nice as it does in synapse or ADF for that matter.
I recommend following
1) all team members work in the same workspace on different components (that's the way we're handling it in our team)
2) each team member works in their own workspace and their own repo (assuming all team member are from the same tenant and have a full license (basic) and have contribute permissions to the devops project.
in any case keep following in mind:
Git integration in Fabric is still in beta. more than half the object types are not supported (Dataflow Gen 2, Pipelines, Default Semantic Models, Direct Lake semantic models, Lakehouse configurations, warehouses, KQL Databases, Real time Analytics Endpoints, Event Streams, KQL Query Sets, etc)
So there is currently very little benefit from hooking up git directly to the workspace, unless you only plan on working on notebooks, reports and semantic models.