Issues Triggering Fabric Deployment Pipeline via Azure DevOps & Selective Deployment Filtering

[Sukiazure007]

Hi Everyone,

I am trying to trigger a Microsoft Fabric Deployment Pipeline using Azure DevOps to deploy the full content by making a POST request to:

bash

CopyEdit

https://api.fabric.microsoft.com/v1/deploymentPipelines/{deploymentPipelineId}/deploy

However, the request fails with the following error:

json

CopyEdit

{ "requestId": "431d2a0c-02f1-4e06-8262-1b421b2d2203", "errorCode": "UnknownError", "moreDetails": [], "message": "An unexpected error occurred while processing the request" }

Interestingly, when I perform selective deployment, the request works fine. This suggests that access, permissions, and stage IDs are not the cause of the issue.

My Questions:

1. What are the possible reasons for a full deployment failure when selective deployment works? Are there specific limitations, service restrictions, or known issues with full deployment via API?

2. Is there a way to exclude a specific type of asset (e.g., Warehouses) during selective deployment while allowing all other assets to be deployed?

   Any insights or experiences with similar issues would be greatly appreciated!

   Thanks in advance.

[Sukiazure007]

Thanks for the response. Looks like a limitation with some of the items which is causing the issue. I'm doing some workaround to only deploy the tested item using a variable for selective deployment.

[v-tsaipranay]

Hi @Sukiazure007 ,

Thanks for the update. It looks like your workaround of using variables for selective deployment is a good approach. You can refine this by dynamically controlling which assets are deployed based on your testing criteria. Adding validation checks in your pipeline to ensure only tested items are deployed could further reduce errors.

For further guidance, you can refer to the Microsoft Fabric documentation for CICD best practices: Best practices for lifecycle management in Fabric - Microsoft Fabric | Microsoft Learn

If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.

Thank you

[v-tsaipranay]

Hi @Sukiazure007 ,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.

Thank you.

[v-tsaipranay]

Hi @Sukiazure007  ,

May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you.

[v-tsaipranay · Accepted solution]

Hi @Sukiazure007 ,

Thank you for reaching out to the Microsoft Fabric Community forum.

1. The "UnknownError" during full deployment, while selective works, suggests a potential issue with specific assets or an API limitation. We don’t see a known bug exactly, but it could be related to payload size or unsupported items. Could you test with a smaller set of assets? If the issue persists, you might need to raise it with Microsoft support, including the requestId.
2. To exclude Warehouses in selective deployment, fetch the item list (GET API), filter out "type": "Warehouse" in your DevOps script, and include the rest in the POST payload. There’s no direct "exclude by type" feature yet.

I am also including a similar issue that has been resolved for your better understanding. Please take a look:
Solved: Deployment Pipeline error - Microsoft Fabric Community

If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.

Thank you

[v-tsaipranay]

Hi @Sukiazure007 ,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.

Thank you.