microsoft / microsoft/finops-toolkit
Enable savings calculations in Power BI reports for CSP customers
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 603
- Forks
- 248
- Avg merge
- 7d 11h
- Merged PRs (30d)
- 11
Description
In the FinOps Power BI report for CSP customers, the Cost Summary section is displaying inconsistent and incorrect values in one of its charts.
Issue Details:
The Total Savings field shows seemingly random values.
The Effective Savings field remains at 0, even when the customer has purchased Reserved Instances (RIs).
This misrepresentation leads to confusion and inaccurate cost optimization insights for CSP customers.
Expected Behavior:
When RIs are purchased, both Total Savings and Effective Savings should reflect accurate and consistent values based on actual usage and reservation benefits.
The chart should correctly sum and display savings metrics without discrepancies.
Steps to Reproduce:
Open the FinOps Power BI report for a CSP customer with active Reserved Instances.
Navigate to the Cost Summary section.
Observe the values in the Total Savings and Effective Savings fields.
Impact:
Misleading financial insights for CSP customers.
Potential miscommunication in cost optimization assessments.
Reduced trust in the accuracy of FinOps reporting.
Suggested Fix:
Review and correct the logic used to calculate and display Total Savings and Effective Savings.
Ensure alignment with RI purchase data and actual usage metrics.
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 in the FinOps Power BI report's Cost Summary section with the chart showing Total Savings and Effective Savings. Reproduce the issue using a CSP customer with active Reserved Instances, then trace both values against RI purchase data, actual usage, and reservation benefits. Done means both fields show accurate, consistent savings values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- analytics, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100