Intune compliance policy starter set for Windows devices
A compliance policy is how Intune decides whether a Windows device is in a trusted state: encrypted, patched enough, firewall on, antivirus running. Conditional Access can then use that result to keep noncompliant devices out of email and files. The mistake is turning on "require a compliant device" before a sensible policy is assigned and devices have actually reported in.
Two layers: tenant settings, then a Windows policy
Microsoft splits this into two areas, documented in Device compliance policies in Microsoft Intune:
- Compliance policy settings are tenant-wide. They act like a built-in policy that every device receives, including how to treat devices that have no assigned compliance policy.
- Device compliance policies are platform-specific rule sets you assign to groups. Windows, macOS, iOS and Android each need their own policy. This guide is the Windows starter.
You need an Intune license for the users or devices in scope. If you will use the compliance result in Conditional Access, you also need Microsoft Entra ID P1.
Set the tenant-wide options first
In the Intune admin center, go to Endpoint security > Device compliance > Compliance policy settings.
- Mark devices with no compliance policy assigned as: change this from the default, Compliant, to Not compliant. Microsoft recommends the change if you use Conditional Access with device compliance, so a device you never targeted cannot slip through as "compliant." The Company Portal will show that no compliance policies have been assigned, which is the correct signal while you are still rolling out.
- Compliance status validity period (days): the default is 30 (you can set 1 to 120). If a device does not successfully report on its policies within that period, Intune treats it as noncompliant. Leave 30 unless you have a reason to shorten it, and do not shorten it so far that laptops off the network over a holiday are mass-blocked.
Change the tenant-wide setting before you create a Conditional Access policy that requires a compliant device, but after you have a plan to assign real policies to every platform you support. See also Monitor results of your device compliance policies.
Create a Windows 10 and later policy
Follow Microsoft's steps in Create device compliance policies: Devices > Compliance > Create policy, platform Windows 10 and later. The setting reference is Windows compliance settings. A practical starter set is below. Leave anything you have not verified in your estate at Not configured rather than inventing a requirement that marks half the fleet noncompliant on day one.
| Category | Starter setting | Why, and what to watch |
|---|---|---|
| Device Health | Require BitLocker | Confirms OS-volume encryption. This value is measured at boot through Device Health Attestation, so a device that has just finished encrypting usually needs a reboot before it becomes compliant. Enable BitLocker and confirm recovery-key escrow first; see our BitLocker via Intune checklist. |
| Device Health | Require Secure Boot | Requires a factory-trusted boot path. Microsoft notes this is supported on some TPM 1.2 and 2.0 devices; hardware that does not support it will show as not compliant. Inventory firmware support in the pilot before you require it company-wide. |
| Device Health | Require code integrity | Checks that drivers and system files loaded into the kernel are trusted. |
| Device properties | Minimum OS version | Use the major.minor.build.revision format Microsoft documents (the ver command shows it). Set this to a currently supported Windows version you actually deploy, not an aspirational build nobody has reached yet. Update the number when you complete a feature-update wave. |
| System security — Device security | Firewall, TPM, Antivirus, Antispyware: Require | Firewall must stay on. TPM require will fail devices with no usable TPM, so confirm hardware first. Antivirus and antispyware checks look for solutions registered with Windows Security Center, not only Microsoft Defender. |
| System security — Defender | Microsoft Defender Antimalware, security intelligence up-to-date, and real-time protection: Require | Use these when Defender is your standard. If a third-party antivirus is registered and you do not use Defender, do not require the Defender-specific service settings without testing; the Antivirus check above may already be enough. |
| System security — Password | Require a password to unlock the device | A basic PIN or password requirement is reasonable. Be conservative with short inactivity timeouts and password expiry unless you have a written standard; those settings surprise users and do not replace phishing-resistant sign-in to Microsoft 365. |
| Microsoft Defender for Endpoint | Leave Not configured unless MDE is onboarded | A machine-risk requirement only works if Defender for Endpoint (or the threat service you integrated) is actually reporting risk for those devices. |
Do not turn on Configuration Manager compliance settings unless the device is truly co-managed. Intune-only devices return a "not available" status for that section.
Actions for noncompliance
Every policy includes a built-in action, Mark device noncompliant, scheduled for zero days, so a failed setting marks the device noncompliant immediately. That status is what Conditional Access can block on. Microsoft documents how to add more actions in Configure compliance policies with actions for noncompliance.
For a first rollout, consider moving "mark noncompliant" to one day and adding an email notification at day zero, so the user and help desk see the problem before access is affected. Do not add a retire or wipe action to a starter policy. Retire is destructive, and Microsoft requires an admin to confirm retirement after a device is marked for it.
Assign to a pilot, then watch the report
Assign the policy to a small device or user group that covers each hardware model you support. Watch Devices > Monitor (setting compliance and policy reports) until you understand every noncompliant device. Common first-week noise includes BitLocker that has not been rebooted, Secure Boot on unsupported firmware, and a minimum OS number that is ahead of your update rings.
Windows can re-evaluate some settings (firewall, antivirus, BitLocker, Defender, OS build, real-time protection, Secure Boot) when they change locally, rather than waiting for the next scheduled check-in. That is helpful, but it is not a reason to skip a pilot.
Only after the pilot is clean should you expand the assignment with your wave-based Intune rollout. If new PCs enroll with Autopilot, have this policy ready for the pilot group as described in the Autopilot checklist.
Then, and only then, Conditional Access
Create the "require compliant device" (or compliant or hybrid joined) Conditional Access policy in report-only mode, exclude emergency access accounts, and switch it on only when sign-in logs and compliance reports agree. The sequence is in our Conditional Access starter policies guide.
Want help scheduling the waves that this policy rides on? The Device Rollout Planner workbook includes a readiness checklist, wave schedule and device tracker so compliance is assigned with the rollout, not as an afterthought.