AHB eligible resources can misclassify Linux-priced VM rows as Windows candidates

Summary

The AHB "Eligible resources (last n days)" query can label or imply Windows licensing candidates when compute pricing behavior is Linux-rate, especially in DevTest/mixed-license scenarios.

Upstream query id: 99d44f1f-c53a-40ee-b749-8e5557ec58c7 in src/templates/finops-hub/dashboard.json.

Customer impact

• False-positive interpretation of AHB candidates.
• Confusing output when VM metadata appears Windows-like but contracted unit price aligns with Linux baseline.
• Reduced trust in AHB eligibility guidance.

Repro pattern

1. Use a subscription with DevTest or mixed VM licensing records.
2. Open Licensing & SaaS (Preview) > Eligible resources (last n days).
3. Observe candidates that appear Windows-eligible despite Linux-rate compute pricing behavior.

Proposed fix

Harden the query using two-path detection and price baseline validation:

• Build Linux VM baseline from Ingestion.Prices_final_v1_2 (non-Windows VM meters).
• Keep explicit Not Enabled path, but require compute contracted price (USD-normalized) above Linux baseline.
• Add fallback path using Virtual Machines Licenses meter evidence when status is empty.
• Exclude currently enabled resources.
• Adjust wording to avoid hard Windows-label implication for ambiguous rows.

Reference implementation

Working patch in fork:

• Commit: https://github.com/FallenHoot/finops-hub-bicep/commit/cb28e0c
• Report note: https://github.com/FallenHoot/finops-hub-bicep/blob/main/docs/library/dashboard/BUGREPORT-AHB-ELIGIBILITY-WINDOWS-LABELING-2026-06-22.md

If useful, I can open a PR with the exact query change against the toolkit template.