Forum Discussion

FabricUser101's avatar
FabricUser101
New Member
1 year ago
Solved

Can't add dataset application perms for Power BI Azure integration?

I'm trying to let a Service Principal account refresh my Power BI semantic model from a Python script. I've registered the app through Azure. I've done: Added the Service Principal account to the w...
Need Help
  • V-yubandi-msft's avatar
    V-yubandi-msft
    1 year ago

    Hi FabricUser101 ,

    Thank you for reaching out. I understand you’re trying to refresh a Power BI semantic model using a Service Principal and a Python script, but you’re encountering issues because you can’t find the Dataset.ReadWrite.All application permission in Azure, and your script likely fails with a permissions error.

     

    In addition to Akash_Varuna & tackytechtom  responses.

     

    Since you’ve already enabled  Allow service principals to use Fabric APIs,  let’s add your Service Principal to an allowed group. Confirm Allow service principals to use Fabric APIs  is enabled, select Specific security groups, and add your PowerBI ServicePrincipals group.
     Automate Power BI Premium workspace and semantic model tasks with service principals - Power BI | Microsoft Learn

     

    You’ve added the Service Principal to the workspace, but let's make sure it has the correct role. Verify that your Service Principal (its security group) has at least the Contributor role (Admin is also acceptable). This role allows it to refresh the semantic model.

    Roles in workspaces in Power BI - Power BI | Microsoft Learn

    Regards,

    Yugandhar.

davidschiedam's avatar
davidschiedam
Regular Visitor
10 months ago

Hey V-yubandi-msft ,

Tried all of the above. Could this be due to the fact that the underlying data is through Direct Query and my workspace doesn't have premium capacity? So changing the semantic data to Import Mode could be the solution.

 

Best,
David

V-yubandi-msft's avatar
V-yubandi-msft
Icon for Community Support rankCommunity Support
10 months ago

Yes, that could very well be the reason. When a dataset is in DirectQuery mode and the workspace is not on Premium/Fabric capacity, a Service Principal won’t be able to run queries against it even if all the permissions are correctly set. This often results in the 401 error you're seeing.

DirectQuery datasets require Premium (F/P/PPU) capacity to allow Service Principals to query via API/XMLA.

If Premium isn’t available, switching the dataset to Import mode is a good workaround, because Import mode supports Service Principal queries even in non Premium workspaces.

 

So yes, changing it to Import mode or using a Premium workspace are both valid solutions.

 

-Yugandhar.