microsoft / microsoft/finops-toolkit
[External][Cost Management] ListCost missing in Cost Management exports
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 603
- Forks
- 248
- Avg merge
- 7d 11h
- Merged PRs (30d)
- 11
Description
🐛 Problem
Microsoft Cost Management does not include ListCost and ListUnitPrice in all exported cost data. There are 2 bugs with this:
- ListCost and ListUnitPrice should always be specified.
- If not available, ListCost and ListUnitPrice should be null and not 0.
This is documented in Ingest cost details data as a limitations for PayGPrice column in actual/amortized cost data. This limitation also applies to the ListCost and ListUnitPrice columns in FOCUS data.
👣 Repro steps
- Export FOCUS cost data.
- Filter rows where ListCost == 0 and ContractedCost > 0.
🤔 Expected
- All rows should have an accurate ListCost and ListUnitPrice values.
- The only records with a ListCost or ListUnitPrice of 0 should be free.
- If a value is not available, they should be null. (However, ListCost and ListUnitPrice should always be available.)
ℹ️ Additional context
This is a tracking bug only. The FinOps toolkit community is not responsible for this and cannot resolve the issue. Subscribe to this issue to be notified when the issue has been resolved.
We are tracking the following workarounds until this issue is resolved:
- #835
- #615
Related issues:
- #834
- #727
[!NOTE]
If you are facing this issue, you can file a support request with the Cost Management team to convey the importance of these columns for your needs; however, as a known issue, the support request will likely be closed. The intent of creating a support request is to raise awareness of your needs and increase the priority of the fix.
🙋♀️ Ask for the community
We could use your help:
- Please vote this issue up (👍) to prioritize it.
- Let us know if you see an opportunity to improve the experience from the toolkit.
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 reviewing the Microsoft Cost Management export behavior described in the issue and reproduce the FOCUS-data filter where ListCost is 0 while ContractedCost is greater than 0. Compare the expected null and accurate-value behavior with the linked workarounds (#835 and #615); completion depends on a fix from the Cost Management team, not a toolkit change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100