Your Windows devices show as onboarded on the EDR Onboarding Status tab, and their telemetry appears in the Microsoft Defender portal. A colleague expected onboarding to also turn on cloud-delivered protection and attack surface reduction rules, but neither is configured. What explains this?
Choose an answer to check it. Afterward, select any option to review its explanation.
A broken connection would affect onboarding packages and policy flow, but the devices are onboarded. Even a working connection doesn't configure ASR rules by itself.
The package type matters if onboarding fails. These devices are onboarded and sending telemetry, so the package worked, and neither package type configures protection settings.
An EDR onboarding policy connects the device to Defender so it sends telemetry. Antivirus settings, ASR rules and firewall settings are separate, so you deploy them through endpoint security policies.
Tamper protection locks Defender settings and depends on onboarding, not the other way round. It doesn't deploy protection settings.
id q09e0d09278