Forum Discussion

0_0's avatar
0_0
Frequent Visitor
1 year ago

Automated Deployment w/ Service Principal in DevOps

Hello,   Given that it has been sometime since the public preview of the service principal integration with ADO, I'm attempting deployment via a SPN and have run across an issue, this is more of a ...
admin
CICD
workspaces
0_0's avatar
0_0
Frequent Visitor
1 year ago

Thanks, I managed to get the connection functional thanks to your suggestion but am unable to connect the workspace from Git:

 

try {
     Invoke-RestMethod -Headers $global:fabricHeaders -Uri $connectUrl -Method POST -Body $connectToGitBody
     Write-Host "Workspace '$workspaceName' connected to Git." -ForegroundColor Green
} catch {
     Write-Host "Failed to connect workspace to Git: $($_.Exception.Message)" -ForegroundColor Red
     return
}

 

Failed to connect workspace to Git: Response status code does not indicate success: 400 (Bad Request). I'm assuming it would be an issue with the permissions of the connections, It has access to the repository with the ability to contribute as well as contributor access in our workspace and is able to call public APIs enabled within the admin portal. 
Anonymous's avatar
Anonymous
Not applicable
1 year ago

Hi 0_0,
Thank you for the update. The 400 Bad Request error when connecting the workspace to Git likely stems from an issue with the $connectToGitBody or Service Principal permissions for Git operations(Verify the SPN has Admin access)

check whether the JSON includes a valid connectionId (not null) from the Fabric workspace’s configured connection. Log $connectToGitBody before Invoke-RestMethod to confirm

If the issue still happening, please let me know.

Regards,
Harshitha.

  • Anonymous's avatar
    Anonymous
    Not applicable
    1 year ago

    Hi 0_0,
    I hope the information provided above assists you in resolving the issue. If you have any additional questions or concerns, please do not hesitate to contact us. We are here to support you and will be happy to help with any further assistance you may need.

    Regards,
    Harshitha.

    • 0_0's avatar
      0_0
      Frequent Visitor
      1 year ago

      Hey Anonymous ,

       

      I'm still unable to connect to git, I have a feeling it may be with the portion or the delegated scopes for the SPN itself.

          $connectToGitBody = @{}
    if ($gitProviderDetails.gitProviderType -eq "AzureDevOps") {
        Write-Host "Getting connection by name: $connectionName"
        $connection = GetConnectionByName $connectionName
        Write-Host "Connection lookup result: $($connection | ConvertTo-Json -Depth 3)"

        if (-not $connection) {
            Write-Host "A connection with the requested name was not found." -ForegroundColor Red
            return
        }

        $connectToGitBodyObject = @{
            gitProviderDetails = $gitProviderDetails
            myGitCredentials = @{
                source = "ConfiguredConnection"
                connectionId = $connection.id
            }
        }

        if (-not $workspace.Id) { Write-Host "Workspace ID is null"; return }
        if (-not $connection.id) { Write-Host "Connection ID is null"; return }
        $connectToGitBody = $connectToGitBodyObject | ConvertTo-Json -Depth 3
        Write-Host "Connect to Git body: $connectToGitBody"

        try {
            Invoke-RestMethod -Headers $global:fabricHeaders -Uri $connectUrl -Method POST -Body $connectToGitBody
            Write-Host "Workspace '$workspaceName' connected to Git." -ForegroundColor Green
        } catch {
            Write-Host "Failed to connect workspace to Git. Detailed error: $($_ | ConvertTo-Json -Depth 3)" -ForegroundColor Red
            return
        }
    }

       

      Thanks!

      • Anonymous's avatar
        Anonymous
        Not applicable
        1 year ago

        Hi 0_0 ,
        We regret the inconvenience caused. Please consider raising a Microsoft support ticket for further investigation. You can explain all the troubleshooting steps you have taken to help them better understand the issue.

        You can create a Microsoft support ticket with the help of the link below: 
        https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket