microsoft / microsoft/finops-toolkit
Unable to load Power BI optimisation reports.
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 603
- Forks
- 249
- Avg merge
- 7d 11h
- Merged PRs (30d)
- 11
Description
🐛 Problem
Unable to load optimisation reports.
👣 Repro steps
I have deployed FinOps hub v12 with ADX and have loaded the KQL reports into PowerBI.
I am using Version: 2.143.878.0 64-bit (May 2025) of Power BI, so I get this error when loading the reports:
After closing this error, the CostSummary report loads fine, with the exception that I can’t get to the public price units:
My developer workstation is in a restricted environment which blocks the network access to this. This isn’t my main problem, but I wonder if it is contributing (see further down).
My main issue is with the two optimisation reports. I load the report, enter my ADX cluster URI and get the following error:
Closing that error opens the report (in this case, Workload optimisation) but then gives me a credential error:
I’ve verified that the account I am using has viewer access on both DBs. If I open a blank report and connect to the Hub database, I can get recommendations data from the v1_2 table using this account:
Going back to the out of the box workload optimisation report, and into power query, I see this error:
Going to the error takes me to the Source step:
Troubleshooting:
- I’ve verified the recommendations export is working and there is data in the ingestion folder
- Verified database credentials on both databases, including a test connection
- Verified the correct ADX cluster URI is in the report Setup
🤔 Expected
The data for optimisations should load.
🙋♀️ Ask for the community
- Any ideas on the error?
- Does not being able to load the public pricing table cause issues with the recommendations data?
Thanks.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure in the Workload optimisation and other optimisation reports after entering the ADX cluster URI. Inspect the Power Query Source step and compare it with a blank report that successfully reads the v1_2 table. Done means the optimisation data loads with the documented credentials and cluster configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- analytics, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100