Settings: Scanner
Tune how scans behave. Each section is collapsible and saves independently, so you can adjust one setting without touching the rest. Changes take effect on the next scan, not retroactively. Open Settings > Scanner from the left sidebar.
Sections On This Page
Cost Anomaly Detection
Controls the sensitivity of cost anomaly detection. Lower values surface more anomalies, higher values only surface significant shifts.
- Minimum Change %
- Default 10. Range 0.1 to 100. Minimum percentage change required to flag a cost anomaly.
- Minimum Dollar Change
- Default $1.00. Range ≥ $0.01. Minimum absolute change required to flag a cost anomaly.
Recommended Settings
Aggressive (surface more)
Min % = 5, Min $ = $1.00. For cost-sensitive teams that want to catch small shifts early.
Balanced (default)
Min % = 10, Min $ = $1.00. Good starting point for most environments.
Conservative (cut noise)
Min % = 25, Min $ = $10.00. For large tenants where small fluctuations are background noise.
VM Sizing Recommendations
Controls how aggressive rightsizing recommendations are and how much performance data is required before a recommendation is made.
- Sizing Aggressiveness
- Dropdown. Default Balanced. Three options, each with a target utilization headroom.
- Minimum Data Window
- Default 7 days. Range 0 to 365. VMs with fewer days of performance data than this threshold don't receive sizing recommendations. Set to 0 to include all VMs.
Aggressiveness Options
Conservative
70% target utilization
More headroom for workload spikes. Fewer, safer downsize recommendations.
Balanced (Default)
80% target utilization
Sensible starting point for most environments. Balances savings against performance buffer.
Aggressive
90% target utilization
Tighter sizing, less headroom, more savings. Validate in non-production before applying.
Start Balanced, then move
Begin at Balanced and review the recommendations it produces. Move to Aggressive only after validating recommendations in a non-production environment first.
Existing recommendations are preserved
Raising the Minimum Data Window doesn't invalidate recommendations you already have, it only affects whether new recommendations are created.
Subscription Quota Monitoring
Controls the minimum vCPU quota utilization threshold for quota collection during scans. Quotas below this threshold aren't collected, which keeps scans fast when most subscriptions are nowhere near their limits.
- Minimum Utilization %
- Default 25. Range 1 to 100.
Lower the threshold for proactive monitoring
If you want to track quota usage well before it becomes a constraint, lower the threshold. Keep it higher if you only care about subscriptions that are at or near their limits.
Orphaned Resources
Documentation coming soon
The Orphaned Resources section exists on Settings > Scanner but its specific fields aren't documented yet. If you need to tune orphaned-resource detection, contact support in the meantime.
Commitment Coverage
Documentation coming soon
The Commitment Coverage section controls reservation and savings plan coverage settings. Specific fields aren't documented yet, this page will be updated once the details are confirmed.
Recommended starting point
Leave everything at default for the first scan or two, then tune based on the noise level you see in anomalies, recommendations, and quota data.