Forum Discussion

tripleacoder's avatar
tripleacoder
Icon for Helper I rankHelper I
7 years ago
Solved

Power Bi REST API - 401 Authorization error when using app secret

I have a console app that uses the REST API to get a dataset (and later add rows to it). This works when I supply my own user/password credentials.   Now I have registered the app as a Web/API app ...
Need Help
  • v-jiascu-msft's avatar
    v-jiascu-msft
    7 years ago

    Hi tripleacoder,

     

    As far as I know, the permissions of Power BI are all based on the users. So an App can't act as a user. Please refer to developer/power-bi-permissions where all the descriptions have "user". 

    Regarding "Tenant.ReadWrite.All", the documentation above also has a description. Actually, these permissions only can retrieve the profiles rather than data. Please refer to admin/reports_getreportsasadmin.

    One simple proof we can see is that even an admin can't access all the App workspaces. The data is the precious asset of a company. I think this is reasonable.

     

     

    Best Regards,
    Dale

  • tripleacoder's avatar
    tripleacoder
    Icon for Helper I rankHelper I
    7 years ago

     

    Could you try to mention an access level in API request?

     

    https://docs.microsoft.com/en-us/rest/api/power-bi/embedtoken/reports_generatetoken#tokenaccesslevel

     

     

    I'm not sure what you mean. The link goes to "Required access level for EmbedToken generation", but I'm not using the Embed Token API.

     

    I get the token using this code:

     

     

    const string authorityUri = "https://login.microsoftonline.com/" + tenantId;

AuthenticationContext authContext = new AuthenticationContext(authorityUri);

        
AuthenticationResult result = null;
         
result = await authContext.AcquireTokenAsync(resourceUri, clientCredential);

     

      • Anonymous's avatar
        Anonymous
        Not applicable
        7 years ago

        Most organization have app registrations locked down pretty tight. I am not familiar with that tool for app registration, but I don't imagine it is meant to be a workaround for corporate security restrictions, and I would expect it to fail for most users within most Azure tenants.