Enable to configure Git integration

[YukiK]

I'm trying to configure my azure repo in a PBI workspace.

I have the admin access the workspace and contributor in the ADO project.

My guess is something is missing on the ADO side, but I'm not sure what other permissions 😞

Any help is appreciated!

[pborah]

Hi @YukiK , please ask the DevOps admin to ensure following permissions are enabled for your role.

[Neverwish]

Have you been able to find a solution as we are having the exact same problem!

[Neverwish]

Found our solution, after creating a main branche, add first a second one which you are going to use.

Once this one is there the connection starts working based on the new branch!

[matthewsre]

I'm having this exact same issue and it's not clear to me why I am able to select the Organization but not see any of my projects. 

@YukiK, were you ever able to figure out what was preventing this on the ADO side?

@Kaviraj11, are you able to provide any clarity on what is needed in ADO for the project to show up after selecting the organization?

[YukiK]

@matthewsreNope. I'm guessing it's the issue somewhere in the ADO project. Still working with the ADO admin and IT to figure this out. The weird thing is, this guy from another department was able to set this up and had been using it in his team.

[Kaviraj11]

Could you check the tenant settings? Probably only specific groups might be able to establish the connection.

[YukiK]

If the tenant setting is not enabled, this is the kind of error I get. So, I can't even get that error I mentioned in my initial post if the tenant setting for git integration is not enabled.

[Kaviraj11]

You will need an Admin to setup the connection to Git 

• Member/Contributor: Once connected to a workspace, a member/contributor can commit and update changes, depending on their Azure DevOps role. For actions related to the workspace connection (for example, connect, disconnect, or switch branches) seek help from an Admin.Git integration process - Microsoft Fabric | Microsoft Learn

[YukiK]

According to the documentation you listed, I should be able to assign a repo to a workspace since I'm the workspace admin and have an ADO contributor role with read access. 

I wonder what exactly is missing that gives me that error.