Settings
Configure how the scanner generates commitment recommendations: how much history to consider, which utilization window to alert on, and what counts as "underutilized" or "expiring soon". Open Settings > Scanner from the left sidebar, then expand the Commitment Coverage card.
On This Page
Permissions
Viewing settings is available to read-only roles. Saving changes requires a role with write access to scanner settings. Without it, the controls are visible but disabled and the Save button shows a tooltip explaining why.
Changes apply on the next scan
Saving a setting does not retroactively re-evaluate existing recommendations. The new values take effect on the next scan. To see the impact sooner, run an on-demand scan from the Scans page.
Defaults
- Recommendation Lookback Period
- 30 days
- Underutilized Evaluation Window
- 30 days
- Underutilized Threshold
- 85%
- Expiry Warning Window
- 90 days
Recommendation Lookback Period
Controls how much historical Azure usage data feeds into Purchase recommendation generation. Three options:
- 7 Days
- Reacts faster to recent usage changes. Useful right after a major workload migration.
- 30 Days
- Default. Balanced view of recent usage patterns. Right for most environments.
- 60 Days
- Smooths out fluctuations over a longer window. Use when steady-state usage is more important than reacting to recent changes.
Underutilized Evaluation Window
Controls which utilization window the scanner uses to decide whether a commitment is underutilized. Three options:
- 1 Day
- Most reactive. Catches sudden drops but can be noisy.
- 7 Days
- Balanced reactivity for most environments.
- 30 Days
- Default. Most stable window. Use for environments where you only want to alert on sustained underuse.
Display window vs. evaluation window
This setting and the Utilization Window dropdown on the Commitments dashboard are separate. The dashboard dropdown only controls how inventory is displayed. This setting controls which window is used to evaluate underutilized alerts. Changing the dashboard dropdown does not change which commitments get flagged.
Underutilized Threshold
The percentage below which a commitment is flagged as underutilized. Numeric input, valid range 1 to 100, default 85.
Tune for your environment
Raise the threshold (for example, to 90) if you want to surface any commitment that isn't fully utilized. Lower it (for example, to 70) if 85 is producing too many alerts and you only want to see commitments that are clearly underused.
Expiry Warning Window
How many days out to start flagging commitments as expiring. Numeric input, valid range 1 to 365, default 90. Only applies in enhanced tier; base tier cannot read commitment expiry dates.
The Expiring Soon section on the Commitments dashboard uses this same window. The Critical / Warning / Upcoming badges are computed from days-until-expiry within this window:
- Critical: 30 days or fewer.
- Warning: 60 days or fewer.
- Upcoming: more than 60 days, up to your configured warning window.
Troubleshooting
I changed the threshold but my recommendations look the same.
Answer
Settings apply on the next scan. To pick up the new threshold sooner, run an on-demand scan from the Scans page. Existing recommendations don't re-evaluate retroactively, they're refreshed when the scanner re-runs the recommendations phase.
The Save button is disabled even though I've made changes.
Answer
Either your role lacks write access to scanner settings (hover the button for the tooltip), or one of the numeric inputs is out of range. Both threshold (1 to 100) and expiry window (1 to 365) show inline validation errors when out of range.