Microsoft Intune compliance reporting shows whether managed devices meet their assigned compliance policies, but a compliant status does not guarantee that every security control is correctly enforced. Businesses should review policy assignments, resolve configuration conflicts, remove outdated exceptions, check inactive devices, and assess settings against CIS benchmarks. Regular reviews and documented evidence help identify security gaps, reduce endpoint risks, and improve compliance reporting accuracy.
Plenty of mid-sized businesses moved their device fleet to Intune years ago. When the migration finished, the compliance figure settled at a comfortable number.
After that, running Intune usually falls to whoever has time, or remembers to set permissions for a new team member. But when policies are only added as new needs come up, and few are removed, gaps widen and the platform becomes harder to manage.
Meanwhile, the cost of weak endpoint controls has kept climbing. In 2024/25, medium-sized businesses reported an average loss of $97,200 per cybercrime report to the Australian Signals Directorate, a 55% rise on the year before.
Auditors and insurers now want evidence that controls are in place on every device. The Intune compliance report is usually the first thing a team pulls up when they’re asked for it.
So what is that figure measuring, and when did anyone last check?
Endpoint Platform Debt: How Does It Build Up?
Endpoint platform debt is the gap between how your tenant was initially set up, and how it should be running now. It builds slowly; each change made sense at the time, but over months or even years, the disparities grow.
Common sources include:
- Pilot policies that never left: Profiles built to test the migration stayed assigned after go-live. Some still target groups whose membership has since changed.
- Exceptions with no end date: An exclusion group created for one executive’s laptop or a legacy app tends to stay in place. More devices quietly join it over time.
- Changes made by many hands: Internal staff move on and contractors come and go. Without a naming convention or a single owner, nobody can say why a given policy exists.
- Old security baselines left assigned: New baseline versions are released over time, and Intune provides a process for migrating an existing baseline profile to a newer version. Tenants that skip this step often end up with old and new versions running side by side.
- Group Policy still in the mix: On hybrid-joined devices, Group Policy and Intune can both configure the same setting.
Over a few years, these items stack up. At that point, it’s hard for anyone to say which settings a given device is enforcing, and the dashboard shows no sign of it.
Considering adopting AI tools? Make sure you’ve taken the risks and obligations seriously: AI Security Risks: The Importance of Strong Governance
What Does ‘Compliant’ Mean in Intune?
Intune counts a device as compliant when it meets the conditions set in the compliance policies assigned to it. However, that definition has gaps.
Devices With No Policies Can Pass
Intune has a tenant-wide setting that decides how it treats devices with no compliance policy assigned. The default is Compliant, and Microsoft’s documentation describes that default as the security feature being switched off.
Under the default, any device that slips through your group assignments will still show as compliant. Microsoft advises reviewing this setting if you use device compliance status in Conditional Access policies. If you do, an unassigned device can satisfy a rule that requires a compliant device.
Switching the setting to Not Compliant is the right long-term move. Before you do, make sure every production device has a policy assigned, or people will be locked out.
A Pass Only Covers Rules You Wrote
A compliance policy checks a short list of conditions. If a BitLocker requirement was never added, or was removed to fix a problem on a few laptops, unencrypted devices will still pass.
Timing matters too; a device that stops reporting is only treated as noncompliant once it misses the compliance status validity period, which defaults to 30 days. A device can go quiet for weeks and keep its compliant status.
Stale Devices Drop Out of View
Device cleanup rules hide devices from the Intune portal and its reports once they haven’t checked in for a set number of days, anywhere from 30 to 270. Hidden devices stay in Microsoft Entra ID.
This gives you a tidier dashboard – sitting over a directory that still holds old device identities.
Conflicting Policies and Cyber Security
Intune treats every policy type as an equal source of device settings. When a device receives different values for the same setting from more than one policy, the affected settings might fail to apply. Microsoft’s guidance is that Intune generates an error and applies neither setting when this happens.
So a control that two admins each configured can end up enforced by neither of their policies.
Conflicts tend to come from four places:
- Two configuration policies: Intune shows the conflict, and Microsoft recommends checking every place you’ve configured policy to resolve it.
- Two compliance policies: When two compliance policies evaluate the same setting, the most restrictive one applies. This means compliance and configuration policies behave in different ways when they overlap.
- Security baselines and other profiles: Baselines can manage the same settings as device configuration profiles. Running several baselines, or customised copies of one, can create conflicts that need investigating.
- Group Policy and Intune: The MDMWinsOverGP setting only covers settings in the Policy CSP. Microsoft recommends against setting the same value in both Group Policy and MDM unless MDMWinsOverGP covers it.
When two settings reach the same device and Intune can’t work out which one should apply, Intune’s baseline monitoring shows a Conflict state. Not enough teams review this on a regular schedule.
Meanwhile, the device keeps reporting as compliant, because its compliance policy may never check the setting that failed.
The Cost of Misconfigured Policies
Policy drift changes how devices behave for the people using them. This issue rarely makes it onto a risk register, so it usually goes unmeasured.
Some patterns come up again and again in tenants that have drifted:
- Inconsistent behaviour across a team: A setting applies on some devices and fails on others, so two people doing the same job get different results. Support staff then chase faults that trace back to policy, which is rarely the first place they look.
- Access blocked at the wrong moment: A compliance state that hasn’t refreshed can trip a Conditional Access rule. The user loses access to email or files until someone forces a sync.
- Settings copied from a stricter profile: Controls lifted wholesale from a high-security template can break line-of-business apps. The usual fix is another exception, which adds to the debt.
- Workarounds: When a managed device gets in the way, people turn to a personal laptop or an unapproved app to get their work done. Those sit outside every policy you’ve written.
Each workaround moves a piece of work beyond your controls, and none of it appears in the compliance figure.
The ASD Essential Eight is being retired next year. Make sure you’re prepared: Essential Eight Retirement: What Businesses Need to Know
How to Run a Baseline Check Against CIS
An independent benchmark gives you a fixed standard to measure your own rules against. CIS benchmarks are developed through a community consensus process and set out secure configuration guidelines for devices managed through Intune.
Here’s a step-by-step guide to get started:
- Get the current benchmark: Version 5.0.0 of the CIS Intune benchmarks is available for both Windows 11 and Windows 10. Use the one that matches your fleet, and record the version you assessed against.
- Start with Level 1: CIS designed its Level 1 profile to reduce attack surface while keeping machines usable and business functions running. For most mid-sized organisations, it’s the right place to begin. Keep Level 2 for devices or roles that handle sensitive data.
- List everything that sets a value: Export your compliance policies, configuration profiles, endpoint security policies, and security baselines. Include any GPOs that still reach hybrid-joined devices, and note who created each item and when.
- Map each recommendation to its source: For every CIS control, record which policy sets it. Flag controls that are set in more than one place, and controls that aren’t set anywhere.
- Check every place a control is set: Your map from step 4 shows where each CIS control should be applied. Check the per-setting status in your configuration policies, the setting compliance report for compliance policies, and the device results for any custom scripts. If a control is on your map but fails on the device, the cause is usually a conflict, an exclusion, or a script that didn’t run.
- Trial every exception: Each exclusion needs a named owner and an end date. If no one can explain why an exclusion exists, remove it.
- Test changes in a pilot group: CIS recommends trying its guidance in a test environment first to gauge the impact, whichever profile level you choose. Include the line-of-business apps that cause you the most trouble in that pilot.
- Keep a record: A spreadsheet map is enough for the first pass. Add the date of each check, the result for each control, and the report or export that proves it. Keep that record up to date between reviews, so the next assessment builds on this one.
Put a Second Number Next to the First
Keep reporting the compliance figure, and add another one alongside it: the share of CIS Level 1 controls your devices enforce without conflict.
Track both figures every quarter so that if the benchmark score drops while compliance holds steady, you’ll spot drift before an auditor does.
And if you need a second set of eyes, Atarix is a Microsoft specialist for mid-sized businesses, and Intune is central to the work we do. Our Intune assessment scores your tenant against CIS and the Essential Eight, showing exactly where your compliance figure and the benchmark disagree.
If you want to know what your dashboard isn’t showing you, reach out to our team.



