microsoft / microsoft/finops-toolkit
[Power BI] Remove deprecated features in storage reports
Open
Nobody has claimed this yet.
Tool: Power BI
- Dominant language
- PowerShell
- Stars
- 603
- Forks
- 248
- Avg merge
- 7d 11h
- Merged PRs (30d)
- 11
Description
⚠️ Problem
Power BI storage reports are very slow due to all the processing requires to align different versions of FOCUS and minor bug fixes that have been applied, which should no longer be needed. This includes:
- Support for FOCUS 1.0-preview.
- Tracking data quality issues with the x_SourceChanges column.
- Fixing x_SkuTerm values to be numbers for MCA.
- Informative x_FreeReason column to explain why a row might have no cost.
- Unique name columns to help distinguish between multiple objects with the same display name.
🛠️ Solution
- Only run extra steps when a Deprecated: Perform Extra Query Optimizations parameter is enabled for storage reports
- In 0.9, disable the PEQO parameter in storage reports
- On or after July 2025, remove the PEQO parameter and corresponding steps
- Consider adding a parameter for supporting historical FOCUS versions
- Document which versions of FOCUS are supported by which FTK versions
- Document that older FOCUS version are supported by FinOps hubs with Data Explorer
🙋♀️ Ask for the community
We could use your help:
- Please vote this issue up (👍) to prioritize it.
- Please vote this issue up with a 🚀 if you need support for older FOCUS versions.
- Leave comments to help us solidify the vision.
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 with the Power BI storage reports and the deprecated PEQO parameter and identify the corresponding extra query-optimization steps. Remove the parameter and steps after July 2025, then document supported FOCUS versions and the older-version behavior with FinOps hubs and Data Explorer.
Written by the indexing model from the issue text.
Assessment
- Domain
- data, documentation
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100