Skip to main content

Scanner Settings

Set sizing aggressiveness and the minimum data window for each resource type. Open Settings > Scanner from the left sidebar and expand Sizing Recommendations. It has three sub-sections, Virtual Machines, Managed Disks and App Service Plans, each with its own Sizing Aggressiveness and Minimum Data Window (days).

Permissions

Viewing the card requires read access to scanner settings. Saving requires the Configure Scanner Settings permission; without it, the fields are read-only.

The Sizing Recommendations card at its defaults. Each resource type is tuned independently.

Save Changes saves all three sub-sections together. Reset to Default restores Balanced and 7 days in every sub-section, which you then save.

Defaults

Sizing Aggressiveness
Balanced (80%), for every resource type
Minimum Data Window
7 days, for every resource type

Changes apply on the next scan

Saving doesn't recalculate anything. The next scan regenerates every recommendation of the changed type, so badges and savings may all change.

Sizing Aggressiveness

The maximum projected utilization a target may reach. Higher aggressiveness means tighter sizing, larger savings and less buffer for spikes. For what each resource type measures against the ceiling, see Aggressiveness.

Conservative

70% target utilization. Largest headroom for workload spikes.

Balanced

80% target utilization. Moderate headroom, good savings.

Aggressive

90% target utilization. Tightest sizing, maximum savings.

Start with Balanced

Consider Aggressive only where spike tolerance allows, such as non-production or horizontally scaled workloads. There's no per-resource override; to leave one resource alone, hide its recommendation.

Minimum Data Window

The days of performance data a resource needs before its first recommendation, from 0 to 365. Existing recommendations keep updating regardless. How a short window behaves depends on the resource type:

Virtual Machines
0 includes every VM regardless of history. Short windows produce lower confidence.
Managed Disks
For disks on stopped VMs, deallocated days count as data days. Below 7 lowers the trust floor (see below).
App Service Plans
Below 7 lowers the trust floor (see below).

The trust floor for disks and App Service plans

Managed disks and App Service plans compute P95 statistics only from at least 7 days of data. A window below 7 lowers that floor to the window's value, so statistics come from fewer days. A window of 0 is testing mode: statistics from a single day and recommendations on the first scan with any data, with Low confidence and explicit warnings.

Testing mode is for evaluation

A Minimum Data Window of 0 for disks or App Service plans produces recommendations from a single day of data. Use it to evaluate a new install, and don't act on the results without validation.

Troubleshooting

I changed aggressiveness but recommendations look the same

Answer

Settings apply at the next scan. Wait for the scheduled scan or run one manually.

Save Changes is greyed out

Answer

There are no unsaved changes, a field has an error, or you lack the Configure Scanner Settings permission. Hover the button to see which.

I want recommendations for resources that have only run a few days

Answer

Lower that resource type's Minimum Data Window, for example to 3 or 0, save, and wait for the next scan. Treat the results as preliminary.

Was this page helpful?

Last updated October 27, 2026