4.1.1. Antivirus Policies
💡 First Principle: Antivirus only protects a device while it stays on, stays current and stays configured the way you intended — and those are exactly the things malware and well-meaning users try to change. So an antivirus policy is less about switching Defender on than about locking in its settings, keeping its updates flowing and making sure it reports back when something's wrong.
What's in the policy. The Antivirus policy type carries the same antivirus settings you'd find in the Endpoint protection and Device restriction configuration templates, but only those settings. Each platform has its own profiles:
| Platform | Profile | What it manages |
|---|---|---|
| Windows | Microsoft Defender Antivirus | Real-time and cloud protection, scans, potentially unwanted app (PUA) blocking |
| Windows | Microsoft Defender Antivirus exclusions | Excluded paths, extensions and processes |
| Windows | Windows Security experience | What users see in the Windows Security app; tamper protection |
| Windows | Defender Update controls | Engine, platform and security intelligence update channels |
| macOS | Antivirus | Defender settings that replace .plist files; requires Defender for Endpoint installed on the Mac |
| Linux | Microsoft Defender Antivirus, Microsoft Defender Antivirus Exclusions | Defender settings and exclusions |
The Windows profiles use the Settings Catalog format and work on Intune-managed devices and devices managed by Defender for Endpoint, including Windows Server. A useful co-management detail: unlike the antivirus settings in a Device restriction profile, the Microsoft Defender Antivirus profile works on co-managed devices, provided the co-management Endpoint Protection workload slider is set to Intune.
Cloud protection. Cloud-delivered protection is on by default, and Microsoft recommends keeping it that way, because so much depends on it: block at first sight, sample submission, tamper protection, emergency signature updates, EDR in block mode and some ASR rules. In the Microsoft Defender Antivirus profile you'll see Allow cloud protection, Submit samples consent and Cloud block level, which ranges from the default level through High (more aggressive, more false positives) and High plus to Zero tolerance, which blocks all unknown executables. Setting sample consent to Never send lowers protection and disables block at first sight — a quiet way to weaken a device.
Potentially unwanted apps. PUA protection has three values: 0 off, 1 block, 2 audit. Microsoft recommends starting in audit mode. Blocked PUA files are quarantined, and PUA events appear in the device's Event Viewer, not in Intune.
Exclusions and conflicts. Every exclusion lowers protection, and Microsoft says so plainly. Exclusions are also special in how they combine: excluded paths, extensions and processes support policy merge, so a device that receives three antivirus policies gets the combined superset of all their exclusions. Settings that don't merge resolve differently: the most secure value applies; if the values are equally secure, the most recently modified policy applies; and if that still doesn't settle it, nothing is delivered.
Tamper protection. On Windows, tamper protection is set in the Windows Security experience profile. As the name suggests, it protects Defender's own settings from being tampered with. It requires the device to be onboarded to Defender for Endpoint, and it turns on at the first check-in after onboarding.
Controlled configuration (preview). A 2026 addition extends tamper protection further. The Controlled Configuration (Device) setting in the same profile makes Intune "the single authoritative source" for Defender settings: Intune's values take exclusive precedence over Group Policy, Configuration Manager, third-party tools and local changes, and unconfigured settings fall back to secure defaults. Its values are Off (Default), which turns off both controlled configuration and tamper protection, Tamper Protection (On) and Controlled Configuration (On). During the preview it enforces only settings from the Antivirus and Attack surface reduction endpoint security templates — not EDR, firewall, account protection or Settings Catalog policies — and an overlapping Settings Catalog setting reports Not applicable on a controlled device.
Reporting. Endpoint security > Antivirus shows a summary and an Unhealthy endpoints list, which shows only devices with detected issues. The Reports node adds the Antivirus agent status and Detected malware reports. Updating security intelligence on demand is a remote action, covered in Phase 3.
⚠️ Exam Trap: Two antivirus policies with different exclusion lists don't conflict — exclusions merge, so the device gets every exclusion from both. That's also why an unexpected exclusion is dangerous: you have to check every policy assigned to the device, not just the one you're looking at. Non-merging settings, by contrast, resolve to the most secure value.
Reflection Question: A security team wants Defender settings that Intune deploys to stop being overridden by a legacy Group Policy and by local administrators. Which setting would you evaluate, what is its release status, and which kinds of Intune policy would it not yet protect?