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.
