Deployment Pipelines API - Error with itemType DataPipeline via Service Principal only

[garddolau]

Hi Team,

Are there any known issues when deploying a DataPipeline via the Deployment Pipelines API using a Service Principal?

I successfully deploy them fine a token from my user account, when I run the exact same config with a token via service principal I get an error as below when checking the Long Running Operation ID:

{

    "status": "Failed",

    "createdTimeUtc": "2025-06-06T14:24:04.9231194",

    "lastUpdatedTimeUtc": "2025-06-06T14:24:05.4603678",

    "percentComplete": null,

    "error": {

        "errorCode": "DeploymentOperationFailed",

        "moreDetails": [

            {

                "errorCode": "UnknownError",

                "message": "An error occurred while processing the operation",

                "relatedResource": {

                    "resourceId": "eca1929e-b57b-4e4f-85f4-48462eca3c94",

                    "resourceType": "DataPipeline"

                }

            }

        ],

        "message": "Failed to deploy content to target stage"

    }

}

[garddolau · Accepted solution]

Hi All, happy to report that MS support have now resolved this issue.  I've confirmed its fixed in these regions UK South and West Europe

[v-tsaipranay]

Hi @garddolau ,

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.

[garddolau]

Can anyone for MS confirm there is currently a known limitation/issue for this combination please?

(a) Deployment Pipelines REST API = https://api.fabric.microsoft.com/v1/deploymentPipelines/{{deployment_pipeline_id}}/deploy

(b) itemType = DataPipeline

(c) via Service Principal

(d) Service Principal has admin access on all 3 workpsaces inlcude in the deployment pipeline

(e) Service Principal has admin access on the deployment pipeline

(f) Method being used to post to the API works fine other item types eg(Lakehouse, VariableLibrary, SemanticModel, Notebook)

(g) When completing the test I am only trying 1 DataPipeline

(h) When completing the test the Data Pipeline being used to test is empty so has no dependencies

[v-tsaipranay]

Hi @garddolau ,

Thank you for sharing the detailed test scenario.

Based on the current official documentation, deploying Dataflows using a Service Principal is not supported. However, there is no mention of any limitation for DataPipelines, which suggests that deploying them using a Service Principal should be supported.

The behavior you're experiencing where the deployment works fine with a user token but fails with a Service Principal, even though the Service Principal has admin access to all workspaces and the deployment pipeline. Other artifact types like Lakehouse and Semantic Models deploy successfully and the DataPipeline being tested is empty indicates that this may be a backend limitation or issue that isn’t yet documented.

At this time, we cannot confirm it as an officially known limitation, but your scenario is consistent with recent community reports and internal findings.

To get an official confirmation and allow deeper investigation, we recommend raising a support ticket with the Microsoft support team. This will help the backend team check logs and confirm whether it’s a known issue or a gap.

You can raise a support request here by following the guide: How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

Hope this helps. Please reach out for further assistance.
If this post helps, then please consider to give a kudos and Accept as the solution to help the other members find it more quickly.

Thank you.

[v-tsaipranay]

Hi @garddolau ,

We are following up once again regarding your query. Could you please confirm if the issue has been resolved through the support ticket with Microsoft?

If the issue has been resolved, we kindly request you to share the resolution or key insights here to help others in the community. If we don’t hear back, we’ll go ahead and close this thread.

Should you need further assistance in the future, we encourage you to reach out via the Microsoft Fabric Community Forum and create a new thread. We’ll be happy to help.

Thank you.

[garddolau]

Hi,

I've finally got a support ticket opened with Microsoft, i'll update when I have feedback.

Thanks for your suggestion

[v-tsaipranay]

Hi @garddolau  ,

Thank you for the update and for continuing to work with Microsoft Support on resolving the issue.

Please stay in touch with the Microsoft support team, as they are best equipped to assist with any further troubleshooting or updates related to your ticket. Once the issue is resolved, we kindly ask that you share the resolution with the community so that others facing a similar challenge can benefit from your experience.

Thank you again for your patience, and we look forward to hearing from you regarding the outcome.

[v-tsaipranay]

Hi @garddolau ,

Thank you for reaching out to the Microsoft Fabric Community Forum, and we appreciate you bringing this to our attention.

You're correct that during FabCon 2025, Microsoft announced expanded support for Service Principals in Deployment Pipelines, and the current REST API documentation no longer explicitly lists DataPipelines as unsupported.

It appears that deploying DataPipeline artifacts using a Service Principal may still encounter functional limitations or backend constraints, even if not yet documented. The error you're encountering (DeploymentOperationFailed, UnknownError) is consistent with this scenario.

Please follow the recommendations which help you clearing your issue:

• Ensure the Service Principal has the appropriate workspace-level permissions (either "Admin" or "Member") on both the source and target stages.
• Verify that the Service Principal has Fabric Contributor permissions at the tenant level, if required.
• Monitor the Microsoft Fabric Roadmap and Ideas portal for updates on expanded support for APIs and Service Principals.

If the issue persists despite proper permission setup, we recommend raising a formal support ticket so that the backend team can investigate and help you resolve the issue.
You may refer to the following article for guidance on creating a support ticket: How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

Hope this helps. Please reach out for further assistance.
If this post helps, then please consider to give a kudos and Accept as the solution to help the other members find it more quickly.

Thank you.

[burakkaragoz]

Hi @garddolau ,

This is a great question and something many users run into with Fabric Lakehouse Semantic Models. Here’s what’s going on and what your options are:

Currently, you can’t create or manage field parameters directly from the Fabric Service UI for semantic models that were built entirely in Lakehouse. The traditional method of downloading to a PBIX file, making changes in Power BI Desktop, and then republishing is only available if you already have a PBIX version of your model. If your model only exists as a Service model, that option is not available.

Field parameters are still mostly managed through Power BI Desktop. The Service does not yet provide a way to add or edit them directly for Lakehouse semantic models.

What you can do right now is this:

• If you have a PBIX backup or can rebuild the model in Power BI Desktop, you can add field parameters using the Modeling menu, then publish it back to Fabric.
• If your model only exists in the Service, there is currently no supported way to add new field parameters. You might consider alternative approaches like using calculation groups or DAX-based solutions, depending on your reporting needs.

The Fabric team is working on adding more modeling features to the Service, and field parameters are a highly requested feature. It’s worth following the Microsoft Fabric Ideas portal and release notes for updates.

If you need help with rebuilding your model in Desktop or want to discuss alternatives for your scenario, just let me know. I’m happy to help with step-by-step guidance or suggestions that fit your use case.

[nilendraFabric]

Hi @garddolau 

Service Principals are NOT supported for deploying Fabric Data Pipelines via the Deployment Pipelines API.
This limitation is confirmed by both Microsoft documentation and multiple community reports. When you attempt to deploy a DataPipeline using a Service Principal, you typically encounter errors such as `DeploymentOperationFailed`, `UnknownError`, or `FeatureNotAvailable`.
• User accounts work, but Service Principals do not.

[garddolau]

Support was annouced during Fabcon 2025, the REST API pages were also updated, no mention of DataPieplines not being supported anywhere that I can find.  Deployment Pipelines - Deploy Stage Content - REST API (Core) | Microsoft Learn

FabCon 2025: Fueling tomorrow’s AI with new agentic capabilities and security innovations in Fabric ...