Microsoft Defender for Cloud
Cloud and workloads

Enable Agentless Scanning Vms

In brief

The page now states that Defender for Cloud charges continue while agentless VM scans are suspended. It also reiterates that existing snapshots incur storage charges until deleted and that the 250-snapshot safeguard is not a guarantee.

What Defender admins need to know

Administrators should account for ongoing Defender for Cloud and snapshot storage charges when suspending scans. No required action or deadline is stated.

Summaries are generated from the documentation change itself.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

Note

Existing snapshots continue to incur storage charges until deleted. Defender for Cloud charges also continue while scans are suspended. The safeguard doesn't guarantee a maximum of 250 snapshots.

GCP machines aren't scanned