Fabric CI/CD Deployment Failure – Need Resolution for Partial Deployment and API Errors

[Shiva3]

We are encountering issues during the deployment stage of our Fabric CI/CD pipeline. The deployment includes notebooks and data pipelines, and we are using both a Service Principal and a Service Account for testing. While some items are successfully deployed to the workspace, the deployment ultimately fails with the following errors:

Error Details and Analysis

1. Power BI Report Not Yet Available (Service Principal)

[error] Unhandled error occurred calling POST on 'https://api.powerbi.com/v1/workspaces/ws_id/items'.
Message: Requested 'Power BI Report' is not available yet and is expected to become available in the upcoming minutes.

2. Connection Access Denied (Service Principal)

[error] Unhandled error occurred calling POST on 'https://api.powerbi.com/v1/workspaces/ws_id/items'.
Message: User does not have access to the connection used in the Pipeline. Please verify the user's permissions.

3. Unsupported Dataflow Operation (Service Account)

[error] Unhandled error occurred calling GET on 'https://msitapi.fabric.microsoft.com/v1/workspaces/ws_id/dataflows/dataflow_id'.
Message: Operation not supported for requested item.

Observed Behavior: Partial deployment succeeded (notebooks and some pipelines), but deployment failed overall

Request for Support:

1. Please help with a solution to successfully complete the deployment.
2. Confirm if there is a known delay in Power BI report availability post-deployment.
3. Clarify the required permissions for a Service Principal to access connections in Fabric pipelines.
4. Confirm if GET operations on dataflows are supported in the current Fabric API.

How can we exclude these problematic items (Power BI reports, connections, or dataflows) from the deployment pipeline temporarily, so that the rest of the deployment can proceed successfully?

We are looking for guidance on how to modify deployment scripts or templates to skip or conditionally handle these components.

[Shiva3 · Accepted solution]

We observed that the issues were resolved after updating the Data Pipeline permissions and using a service account. MFA has been disabled for this service account, and currently, CI/CD deployments are functioning smoothly.

However, I’m concerned about the following warning:

WARNING: Starting July 1, 2025, MFA will be gradually enforced for Azure public cloud. Authentication using a username and password via the command line will no longer be supported with MFA. Please consider switching to one of the supported authentication methods. More details: https://go.microsoft.com/fwlink/?linkid=2276314

If MFA becomes mandatory, I may not be able to authenticate via CLI using the current setup, which could potentially disrupt our deployment process.

Any suggestions on how to handle this transition smoothly and ensure uninterrupted CI/CD workflows?

[v-tsaipranay]

Hi @Shiva3 ,

Thank you for reaching out to the Microsoft Fabric Community. We understand you're encountering partial failures during your CI/CD deployment involving notebooks, pipelines, Power BI reports, and dataflows. Below is our guidance addressing each of your concerns:

The error indicating the Power BI report is “not available yet” is typically due to a propagation delay after the report is published. This is a known behavior in deployment pipelines. To mitigate this, we recommend implementing a retry mechanism with a delay to allow the report to become available before the deployment proceeds. You can refer to this Automate deployment pipeline by using Fabric APIs - Microsoft Fabric | Microsoft Learn for more context on such delays.

The “access denied” error suggests the service principal lacks permission to use one or more connections in your pipeline. Please ensure the service principal has at least Contributor access to the workspace and permissions to the underlying data sources (e.g., Lakehouse, SQL DB). You may also review the connection configurations to confirm the service principal is explicitly granted access.

The failure from the GET call on the dataflow indicates that certain operations on dataflows are currently unsupported or limited through Fabric APIs. This is expected behavior, as full API support for dataflows is still being rolled out.

To avoid full deployment failure due to a few problematic components, we recommend breaking your deployment into modular steps with individual error handling. You can use scripting logic (e.g., try-catch, conditionals) to skip specific artifacts when errors occur, allowing the rest of the deployment to continue. 

Hope this helps. Please reach out for further assistance.

If this post helps, then please consider to Accept as the solution to help the other members find it more quickly and a kudos would be appreciated.

Thank you.

[v-tsaipranay]

Hi @Shiva3 ,

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.

[KevinChant]

Out of curiosity, how are you handling your CI/CD deployments? Are you hard coding in all your API calls?