Forum Discussion

vsub14's avatar
vsub14
New Member
1 year ago

Dataset refresh error after change org os365 password DMTS_OAuthTokenRefreshfailederror

Hi,

We have published reports to powerbi service and the data sourced from sharepoint site CSV/Excel Files. As part of orgnizational policy we are changing password of common org account(os365) every 3 months which is used for authentication of sharepoint site/files. Whenever we change password , the datasets of the reports not refreshed and failed with error msg as given below . 

 

 

We need to manually goto each dataset /datasource credentials (web) and edit credentials and sign in again as given below . After that we are able to refresh the data sets successfully.  Since we have more than 25+ reports in different workspaces its tedious process to update credentials in each data whenever there is change in password of common account.  Is there any way to overcome this issue of manually updating password in datasets. 

 

 

Thanks in advance.

vsub14

 

 

3 Replies

  • Hi vsub14 

     

    One of the options you can do is to create a service account, which will have a power bar license, but where the username and password does not change. This can be given to a restricted amount of users so that you will not have to manually update the passwords for the datasets. 

    • vsub14's avatar
      vsub14
      New Member

      Hi GilbertQ 

       

      Thanks for your reply.

       

      We tried this option of Service account which will have power bi license and username/password never expire/change. Our management wants to change the password of service account immediately whenever any key member of BI Team leaves the organization so that there won't be misuse of this account. Is there any other option to overcome this problem.?

       

      Thanks in advance.

       

      Vsub14

      Preview
       
       
       
      • GilbertQ's avatar
        GilbertQ
        Icon for Super User rankSuper User

        Hi vsub14 

         

        I would still suggest this option. Because if you have to change the username and pawword when someone from your team leaves, it should not be that often, so it wouldn't be such a big process to complete.