Forum Discussion

cvr's avatar
cvr
Frequent Visitor
1 year ago
Solved

Power BI Service unable to read the application metadata

Hi Power BI community,   I am experiencing an unexpected error since yesterday when logging-in to the Power BI Service with this error page     I'm in the latest version of Google Chrome b...
  • Nasif_Azam's avatar
    1 year ago

    Hey cvr ,

    Thanks for sharing the error message and steps you've already taken. Here's a breakdown of what this error means and what else you can try to resolve it.

     

    What the Error Means

    The error AppMetadataInaccessible in Power BI typically indicates that your browser could not retrieve essential metadata for the app or report. This is usually due to a network-related issue, such as:

    • Firewalls or proxies blocking metadata endpoints.

    • VPN interference or DNS issues.

    • Expired or blocked session cookies.

    What You've Already Tried

    You've taken some good first steps:

    • Cleared browser cache.

    • Tried Incognito mode.

    • Used the latest version of Chrome.

    • Authenticated successfully via Microsoft Authenticator.

    Since those didn’t solve the problem, here are a few more things you can try.

     

    Additional Troubleshooting Steps

    1. Check Firewall / Network Rules

    • If you're on a corporate or secured network, some Power BI service URLs may be blocked.

    • Ask your IT team to whitelist the following domains (if not already):

      • *.powerbi.com

      • *.analysis.windows.net

      • login.microsoftonline.com

      •  

        aadcdn.msftauth.net

      • *.msidentity.com

     

    2. Test with a Different Network

    • Try accessing Power BI Service using a different Wi-Fi or mobile hotspot to see if it’s a local network issue.

    3. Disable VPN and Proxy Temporarily

    • If you use a VPN or proxy, turn it off temporarily and try logging in again.

    4. Try a Different Browser or Device

    • Open the same link in Microsoft Edge or Firefox.

    • Alternatively, try logging in from another device entirely to isolate whether the issue is browser/system specific.

    5. Check for Expired Sessions

    • Go to https://powerbi.microsoft.com/ > log out manually.

    • Clear cookies specifically for powerbi.com using Chrome settings:

      • chrome://settings/siteData?searchSubpage=powerbi.com

    • Then try logging in again.

    6. Check Power BI Service Status

     

    Still Not Working?

    If none of these work, you can:

    1. Use the Activity ID and Request ID you posted and raise a ticket to Microsoft Support:

    2. Mention the error type AppMetadataInaccessible and provide:

      • Date and Time

      • Activity ID

      • Request ID

      • Browser details

     

     

    If you found this solution helpful, please consider accepting it and giving it a kudos (Like) it’s greatly appreciated and helps others find the solution more easily.


    Best Regards,
    Nasif Azam

  • Datawizguru's avatar
    11 months ago

    I ran into this exact same issue recently - the “AppMetadataInaccessible” error when trying to access Microsoft Fabric. After checking devices, browsers, cache, network, and VPN settings, nothing worked.

    The actual root cause turned out to be a Fabric tenant routing mismatch.

    My account was being routed to a region where my Fabric application metadata didn’t exist, which caused the metadata loading failure even though the login itself was successful.

    Solution (what fixed it for me):

    I forced Fabric to open in my tenant’s correct region using the "preferredRegion" parameter:

    https://app.powerbi.com/?experience=fabric&preferredRegion=southafricanorth

    You can replace southafricanorth with your correct region (e.g., southafricasouth, westeurope, northeurope).

    As soon as I did this, Fabric loaded without any issues.

    Why this works:

    Fabric tries to route your account to its default region, but if the routing table is misaligned or the metadata for your tenant isn’t replicated in that region, the app fails to load. Forcing the region redirects your session to the cluster where your tenant’s metadata actually exists.