Unanswered

How to Disconnect and Change Git Repository for Solution Binding?

(3) Share

Report

Posted on by abhisc

Hi everyone,

I’ve been exploring the new Git integration feature in Power Platform for ALM (Git Integration - Solution Binding), and I successfully connected my solution to an Azure DevOps repository. The feature is working great so far!

However, I now need to switch to a different repository and branch. I'm unable to find a straightforward way to disconnect the current repository or reconfigure the solution to point to the new repo/branch.

Could someone guide me on how to:

Disconnect the solution from the current repository?
Rebind it to a new repository and branch?

Any insights, step-by-step instructions, or references to documentation would be highly appreciated.

Thanks in advance! 😊

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (2)

Answers (0)

CU06020426-0 2 on at

Like (0)

Report

Hey Abhisc,

Do you mean this error message?

TF401019: The Git repository with name or identifier Azure_Repo_Name does not exist or you do not have permissions for the operation you are attempting.

When you try to connect to another repo/remove the old repo from azure?

I have the same issue, and I have tried removing the repo it was pointing to, but got this error.

I'm assuming this is related to the warning during the git connection "This step cannot be undone"

I'm trying to work out at what level I have to reset things to get back to that initial step, keen for some assistance on this one.

Cheers

Screenshot 2025-0...

Your file is currently under scan for potential threats. Please wait while we review it for any viruses or malicious content.

Was this reply helpful? Yes No
TG-18092334-0 3 on at

Like (0)

Report

Looking for an answer to this question as well. My understanding currently is that we are unable to edit those Git connection details ourselves after the initial set up. Would be great to be able to update the branch/folder/other Git settings after the fact without having to create a Microsoft support ticket each time.

Was this reply helpful? Yes No