Forum Discussion

M_Misselbrook's avatar
M_Misselbrook
New Member
2 months ago
Solved

Error loading Power BI report

Hi all, would anyone be able to assist with the following. I'm trying to view our company Power BI reports via a shared account. The shared account has the relevant permissions and it has previously worked. However, it now does not work and I receive the following when trying to open/view the report:

Clicking the support button takes me to Microsoft Fabric and has led me here. Would anyone have any suggestions on how to fix? Many thanks, Mike

  • Hi M_Misselbrook 

    Thanks for shring this. 

    This usually happens when the shared account’s access token or permissions have expired or changed. Even if the account still has rights, Power BI Service may block shared credentials depending on tenant policies.

    Here are the common fixes you can try-

    1. Clear cached credentials-  In Power BI Desktop - File -Options - Data Source Settings - clear the saved credentials for that account, then re‑sign in.

    2. Check tenant restrictions-Some organizations disable shared accounts for Power BI due to security policies.

    3. Confirm with your admin if shared logins are still allowed.

    4.Verify license-The shared account must have a valid Power BI Pro or Fabric license to view reports. If the license expired, access will fail.

    5. Re‑share the report-Ask the report owner to re‑share it directly with your personal account instead of relying on the shared one.

     

    if the tenant  blocks shared logins, you’ll need to use your own account with proper permissions.

     

    If this reply helped mark it a solution,this keeps the community strong and motivated to contribute continously.

     

    Thanks 

    sunita

     

     

4 Replies

  • trivedisunita's avatar
    trivedisunita
    Continued Contributor

    Hi M_Misselbrook 

    Thanks for shring this. 

    This usually happens when the shared account’s access token or permissions have expired or changed. Even if the account still has rights, Power BI Service may block shared credentials depending on tenant policies.

    Here are the common fixes you can try-

    1. Clear cached credentials-  In Power BI Desktop - File -Options - Data Source Settings - clear the saved credentials for that account, then re‑sign in.

    2. Check tenant restrictions-Some organizations disable shared accounts for Power BI due to security policies.

    3. Confirm with your admin if shared logins are still allowed.

    4.Verify license-The shared account must have a valid Power BI Pro or Fabric license to view reports. If the license expired, access will fail.

    5. Re‑share the report-Ask the report owner to re‑share it directly with your personal account instead of relying on the shared one.

     

    if the tenant  blocks shared logins, you’ll need to use your own account with proper permissions.

     

    If this reply helped mark it a solution,this keeps the community strong and motivated to contribute continously.

     

    Thanks 

    sunita

     

     

  • Hi  M_Misselbrook ,


    Thank you for reaching out to Microsoft Fabric Community and thanks to trivedisunita  for providing meaningful insights.


    Just wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. 

     

     Best Regards,

    Abdul Rafi.

  • Hi M_Misselbrook ,

    Could you please confirm if the issue has been resolved? If not, feel free to reach out if you have any further questions.

    Your update would be helpful for other members who may face a similar issue.

    Best Regards,
    Abdul Rafi

  • Thank you very much for the above advice. I think generally it is a security permissions issue but in particular an issue with Microsoft Edge and the permissions on that. I have subsequently tried via Google Chrome and on most of the shared accounts, it works going via Chrome. Unfortunately, not on all the accounts though, which is rather confusing and makes me think it is an organisation permissions issue. Thanks, I will keep trying...