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 LeifB ,
Thank you for reaching out to the Microsoft Community Forum.
The error indicates that the Power BI Deployment Pipeline stage name provided in your ADO task does not match what Power BI expects.
Please try below things to fix the issue.
1. Go to Power BI Service --> Deployment Pipelines --> Your Pipeline. Check the stage names are same for Development, Test, and Production all are case-sensitive.
2. Go to Power BI, open the pipeline and copy its ID from the URL. And check the ADO task references the correct pipeline.
3. Go to Power BI Admin Portal --> Deployment Pipelines, confirm the SPN is an Admin. Also check workspace permissions for each stage.
4. Please use the latest version of BI Automation Tools for ADO.
I hope this information helps. Please do let us know if you have any further queries.
Regards,
Dinesh
Hi Dinesh, thanks for the reply. I followed your steps and unfortunately still got the same error. Can you confirm that this is the setting the SPN should be on? If so, I did confirm that it is.
To clarify, we only have Test and Production workspaces/stages. Is it required to have Development as well in order to use the BI Automation Tools?
Edit: I tried deleting and recreating the Deployment Pipeline to have all 3 stages and ran it again, but now it's saying that it can't find the pipeline. I did confirm that I added the SPN as an admin on the pipeline and all workspaces.
Hi LeifB ,
The SPN is correctly added as an Admin on the pipeline. So permissions are not the issue.
Is it required to have Development as well in order to use the BI Automation Tools?Yes, the Power BI Deployment Pipeline API expects all three stages to exist. Even if you only plan to use Test and Production, the pipeline object must include all three stages because the API schema is fixed. If Development is missing, the API call will fail with "PipelineStageNotFound" error.
The error “pipeline not found” refers to when you recreated the pipeline, the pipeline ID changed. Your ADO task might still be referencing the old pipeline name or ID. The BI Automation Tools task uses the pipeline name internally, but if the service connection cached the old ID, it can cause this error.
Please check below things to fix the issue.1. Go to the new pipeline in Power BI. Copy the ID from the below URL.'
https://app.powerbi.com/groups/me/deploymentpipelines/{pipelineId}
Use this ID in your ADO task if the add-on supports direct ID entry.
2. Go to the task settings, re-select the pipeline from the dropdown. Save and queue the pipeline again.
I hope this information helps. Please do let us know if you have any further queries.
Regards,
Dinesh
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.
