Microsoft Defender for Cloud
Cloud and workloads

Investigate Defender for Endpoint misconfiguration recommendations (agentless)

In brief

The page now explicitly names the Defender for Cloud and Defender for Endpoint integration, adds a stable anchor, changes “Next step” to “Next steps,” and updates metadata.

What Defender admins need to know

No administrator action is indicated; the changes improve documentation clarity and linking.

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.

Microsoft Defender for Cloud integrates with Microsoft Defender for Endpoint to identify endpoint detection and response configuration issues for machines.

As part of thesethe Defender for Cloud and Defender for Endpoint integration, Defender for Cloud uses agentless scanning to evaluate whether Defender for Endpoint is configured correctly on protected machines. Examples of these checks include:

  • Both full and quick scans are out of 7 days
  • Signature out of date

After remediation is complete, it can take up to 24 hours for the machine to appear in the Healthy resources tab.

Next stepsteps

[!div class="nextstepaction"] Verify that machines have an EDR solution configured