Missing recommendations or anomalies

Recommendations and anomalies require sufficient data and an eligible scope.

Checks

1. Confirm provider billing and resource inventory are present.
2. For rightsizing or Spot analysis, confirm utilization telemetry is available.
3. Remove filters and widen the date range.
4. Check production/non-production or environment filters.
5. Confirm thresholds are not excluding the opportunity.
6. Check whether the recommendation was dismissed or routed to another state.
7. For commitment recommendations, verify commitment inventory and usage coverage.
8. For license recommendations, verify entitlement sources.
9. For Perspective anomalies, verify that the Perspective matches resources and spend.

A result of “no recommendations” can be valid. It can also mean incomplete telemetry, insufficient history, restricted access, or an unsupported resource type.

What to check by recommendation type

Type	Required signal
Rightsizing	Cost, resource inventory, and utilization telemetry.
Spot	Workload suitability, interruption tolerance, and compute inventory.
Commitment	Eligible spend history, current commitment inventory, and usage coverage.
License	Entitlement source, running software inventory, and utilization context.
Anomaly	Spend history for the selected scope and current-period billing data.