Forum Discussion
Azure DevOps + Deployment Pipeline Integration Error
I would advise looking to try this in a YAML pipeline instead, using the PowerShell script provided by Microsoft instead of the task.
I have a post that covers how to do that below:
https://www.kevinrchant.com/2024/06/11/update-fabric-deployment-pipeline-stages-with-deploymentpipelines-deployall-and-yaml-pipelines/I hope this helps, if so give it some kudos and/or mark it as the solution.
Hi Dinesh, I did already switch it to use the new ID and still received the error. I looked at the GitHub repo for this add-on and found other people with the same issue, and there did not seem to be any responses, so I'm suspecting there's an issue with the add-on. I'm going to attempt to use the sample PowerShell scripts rather than the add-on, as some folks said they had success with that.
Hi LeifB ,
Thank you for the update. As you mentioned in your previous response, you want to use the PowerShell scripts rather than the add-on. Please try below PowerShell script that authenticates using SPN, retrieves the pipeline details, and deploys content from Test --> Production using the Power BI REST API.
$tenantId = "<TENANT_ID>"
$clientId = "<SP_CLIENT_ID>"
$clientSecret = "<SP_CLIENT_SECRET>"
$pipelineId = "<PIPELINE_ID>" # Take from Power BI URL
$sourceStage = 1 # Test stage
$targetStage = 2 # Production stage
$tokenUrl = "https://login.microsoftonline.com/$tenantId/oauth2/v2.0/token"
$body = @{
grant_type = "client_credentials"
client_id = $clientId
client_secret = $clientSecret
scope = "https://analysis.windows.net/powerbi/api/.default"
}
Write-Host "Requesting OAuth token..."
$tokenResponse = Invoke-RestMethod -Uri $tokenUrl -Method POST -Body $body
$accessToken = $tokenResponse.access_token
$headers = @{
Authorization = "Bearer $accessToken"
"Content-Type" = "application/json"
}
Write-Host "Fetching pipeline details..."
$pipelineUrl = "https://api.powerbi.com/v1.0/myorg/deploymentPipelines/$pipelineId"
$pipelineDetails = Invoke-RestMethod -Uri $pipelineUrl -Headers $headers -Method GET
Write-Host "Pipeline Name: $($pipelineDetails.displayName)"
Write-Host "Stages:"
$pipelineDetails.stages | ForEach-Object { Write-Host "Order: $($_.order) Name: $($_.displayName)" }
$deployUrl = "https://api.powerbi.com/v1.0/myorg/deploymentPipelines/$pipelineId/deploy"
$deployBody = @{
sourceStageOrder = $sourceStage
targetStageOrder = $targetStage
} | ConvertTo-Json
Write-Host "Deploying from Test to Production..."
$deployResponse = Invoke-RestMethod -Uri $deployUrl -Headers $headers -Method POST -Body $deployBody
Write-Host "Deployment Status: $($deployResponse.status)"
Write-Host "Deployment ID: $($deployResponse.id)"
Please try below steps.
1. Uses OAuth 2.0 client credentials flow for SPN.
2. Please Confirm the pipeline exists and lists all stages.
3. Calls the /deploy endpoint to move artifacts from Test --> Production.
Note: SPN must have Pipeline.ReadWrite.All permission. SPN must be Admin on
The pipeline and All workspaces in the pipeline stages. Power BI pipeline must have Development, Test, Production stages .
Please refer below link.
Automate deployment pipelines with APIs for Power BI items - Microsoft Fabric | Microsoft Learn
Pipelines - REST API (Power BI Power BI REST APIs) | Microsoft Learn
Solved: Automate Deployment Pipelines | Power BI API and I... - Microsoft Fabric Community
I hope this information helps. Please do let us know if you have any further queries.
Regards,
Dinesh
I gave your script a try and got the following error, it seems to be the same as when I tried the task from the add-on. I triple-checked that the SPN has all of the required access, and the pipeline ID is correct.
One of the GitHub issues I saw mentioned that they thought this problem was due to the workspace having Git integration set up - we also have this on the Test workspace, but this was a core piece of the version control setup, so removing it would render the solution useless. Is this a known limitation?
Hi LeifB ,
Thank you for the update. It appears this issue might require deeper investigation from the Microsoft Fabric support team. I recommend opening a Microsoft support ticket so they can trace the issue. To raise a support ticket for Fabric and Power BI, kindly follow the steps outlined in the following guide:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn
Regards,
Dinesh
Hi LeifB ,
We are following up to inquire whether you have raised the support ticket. If you have already done so, we kindly request you to share your feedback regarding the issue raised.In case a solution has been provided, we would be grateful if you could share it with the community. This will assist others facing similar challenges and benefit the wider community. If you need any more assistance, please feel free to connect with the Microsoft Fabric community.
Regards,Dinesh