Forum Discussion

tripleacoder's avatar
tripleacoder
Helper 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 in order to use an app key/secret instead. I can get a token, but when I make the same REST call I get 401 Unauthorized.

 

I have given the app the following Application permissions in Power BI Service (is this needed?):

Read and write all content in tenant

View all content in tenant

These permissions have been granted by an Azure Administrator.

 

In addition to the Delegated permissions that worked with user authentication:

Read and write all Datasets

View all Datasets

 

I have decode the two tokens.

The token for app key autentication contains this:

"roles": [
"Tenant.ReadWrite.All",
"Tenant.Read.All"
],

 

while the token for user based authentication contains this:

"scp": "Dataset.ReadWrite.All Workspace.ReadWrite.All",

 

What am I missing..?

  • 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

23 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable

    Why does the sample code for the power bi embedded 'app owns data' scenario use the client credentials route when it is not supported? 

    • sjc4062's avatar
      sjc4062
      Frequent Visitor

      I had a simliar issue where i could use my own credentials but not the service account and the issue was the service account didnt have a power bi pro license. Not sure if thats the same issue but might be worth looking at

      • tripleacoder's avatar
        tripleacoder
        Helper I

        sjc4062 wrote:

        I had a simliar issue where i could use my own credentials but not the service account and the issue was the service account didnt have a power bi pro license. Not sure if thats the same issue but might be worth looking at


         

        That might be it. But when I go to assign licenses and search for the service principal it does not come up in the results. Not sure if it is getting filtered away because only users and groups are valid, or if it's because I am not an Azure global admin.

    • tripleacoder's avatar
      tripleacoder
      Helper I

      v-jiascu-msft wrote:

       

       

      It seems you only need an access token. Please refer to developer/embed-sample-for-customers

       


      That link talks about using a special user account (username + password) for the app, not an app secret/service principal, which is what I am trying to do.

       

      However, I have been told elsewhere that roles are not needed in order to authorize service principals. Only "App permissions" are needed.

      • v-jiascu-msft's avatar
        v-jiascu-msft
        Microsoft Employee

        Hi tripleacoder,

         

        Your requirements are quite clear now. You'd like to use the App secret (aka client secret) instead of the user password authentication. I'm afraid this isn't workable in Power BI. The reason is simple. Even the global admin can't access other's contents. How can an App access everything?

         

        Best Regards,
        Dale

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi All,

     

    I am also geeting the same error when accessing power BI rest API's. I am able to generate token but not proceeding further. Can you please paste your code, which ran successfully exclusive of all tennat id and username and pwd.

     

    Thanks & Regards


    tripleacoder wrote:

    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 in order to use an app key/secret instead. I can get a token, but when I make the same REST call I get 401 Unauthorized.

     

    I have given the app the following Application permissions in Power BI Service (is this needed?):

    Read and write all content in tenant

    View all content in tenant

    These permissions have been granted by an Azure Administrator.

     

    In addition to the Delegated permissions that worked with user authentication:

    Read and write all Datasets

    View all Datasets

     

    I have decode the two tokens.

    The token for app key autentication contains this:

    "roles": [
    "Tenant.ReadWrite.All",
    "Tenant.Read.All"
    ],

     

    while the token for user based authentication contains this:

    "scp": "Dataset.ReadWrite.All Workspace.ReadWrite.All",

     

    What am I missing..?



    tripleacoder wrote:

    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 in order to use an app key/secret instead. I can get a token, but when I make the same REST call I get 401 Unauthorized.

     

    I have given the app the following Application permissions in Power BI Service (is this needed?):

    Read and write all content in tenant

    View all content in tenant

    These permissions have been granted by an Azure Administrator.

     

    In addition to the Delegated permissions that worked with user authentication:

    Read and write all Datasets

    View all Datasets

     

    I have decode the two tokens.

    The token for app key autentication contains this:

    "roles": [
    "Tenant.ReadWrite.All",
    "Tenant.Read.All"
    ],

     

    while the token for user based authentication contains this:

    "scp": "Dataset.ReadWrite.All Workspace.ReadWrite.All",

     

    What am I missing..?




     

  • ironmanwk's avatar
    ironmanwk
    Regular Visitor

    My teammate been trying to get REST API to work as well but also encounter the same 401 error message. Is this still an on-going issue or there is a solution we can apply?

  • Anyone got this worked out?  I'm running into the same issue where we need to assign workspaces to a capacity via this POST Call

    Invoke-PowerBIRestMethod -Url 'admin/capacities/AssignWorkspaces' -Method Post -body $bodyStr

    This works for my ID but fails for ServicePrincipal.  Is the ServicePrincipal only allowed for "Read-Only" API calls (GET method)?

     

    Please let me know as we're trying to automate some scripts using ServicePrincipal/App ID.  Not sure what we're missing.

    • Anonymous's avatar
      Anonymous
      Not applicable

      Hi, did you solve it, appreciate for your response, thanks!

      • pvuppala's avatar
        pvuppala
        Helper V

        Ended up using personal account to run the PowerShell script.  Eventually would like to use Power Automate via Service Principal client/secret.