PBIP deployment using GitHub actions

Thankyou, GilbertQ, for your response.

Hi mikeklink,

We appreciate your enquiry through the Microsoft Fabric Community Forum.

Based on my understanding, the issue occurs because deploying PBIP folders requires the Fabric REST APIs or the FabricPS-PBIP PowerShell module. By default, service principals are not enabled for API access unless a Fabric administrator updates the tenant settings. In the absence of this configuration, authentication fails even if the service principal exists.

Please follow the steps below, which may help resolve the issue:

1. Request a Fabric administrator to enable Service principals can use Fabric APIs in the Fabric Admin portal, and scope this setting to a security group that contains the service principal.
2. Assign the service principal the necessary permissions, such as Contributor or higher, on the target Fabric workspace.
3. Use the FabricPS-PBIP PowerShell module or the Fabric REST APIs in the GitHub Actions pipeline to deploy PBIP projects to the workspace.

For further guidance, please refer to the links below:
Deploy a Power BI project using Fabric APIs - Microsoft Fabric REST APIs | Microsoft Learn
Embed Power BI content in an embedded analytics application with service principal and an application secret - Power BI | Microsoft Learn
Analysis-Services/pbidevmode/fabricps-pbip at master · microsoft/Analysis-Services · GitHub
Automate deployment pipelines with APIs for Power BI items - Microsoft Fabric | Microsoft Learn
Automate Power BI Premium workspace and semantic model tasks with service principals - Microsoft Fabric | Microsoft Learn

We hope this information helps resolve the issue. Should you have any further queries, please feel free to contact the Microsoft Fabric community.

Thank you.