Add triage and troubleshooting guidance for Rate Optimization report $0 savings issue #1848
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue Summary
Users deploying FinOps Hub with Azure Data Explorer (ADX) are experiencing $0 savings displayed in the Rate Optimization Power BI report for certain reservations, despite having properly configured FOCUS cost exports, price sheets, reservation details, and reservation transactions at the MCA Billing Profile level.
Root Cause
The issue occurs when price sheet data is missing or ingested after cost data. The Rate Optimization report calculates commitment discount savings using the formula:
However, Microsoft Cost Management does not include list and contracted prices for all accounts, particularly for MCA billing profiles. According to the FinOps hubs data processing pipeline, price enrichment happens during cost data ingestion:
When price data is missing, the savings calculation documentation specifies:
Response Provided
This PR documents comprehensive triage guidance including:
Root cause analysis - Explained why $0 savings appear (missing price data required for savings calculations)
Critical finding - YES, the order of ingesting Price Sheet matters! Price data must be ingested BEFORE FOCUS cost data to properly populate missing prices during the cost data transformation process.
Step-by-step solutions:
Data quality diagnostics - Provided KQL query to identify specific pricing scenarios causing $0 savings
Authoritative documentation links - Referenced 9 official Microsoft Learn and FinOps toolkit documentation sources:
Impact
This guidance helps users:
Related Issues
Addresses reported customer deployment issues where properly configured exports still show $0 savings due to data ingestion ordering and missing price enrichment.
Original prompt
Fixes #1811
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.