What is an Intune audit?
An Intune audit reviews whether Microsoft Intune is managing and protecting the devices and applications your organisation expects it to cover. It examines policy design, assignments, exclusions, deployment results, administrative access and the connection between device posture and access to company data.
The central question is not simply whether a security policy exists. It is whether the right devices receive it, whether it takes effect, and what happens when a device fails the requirement. A tenant can contain well-written policies while important groups, platforms or access paths remain outside their coverage.
Intune is one part of the wider environment. Our Microsoft 365 security audit connects endpoint findings with Microsoft Entra ID, email and collaboration controls. This guide provides a practical review method; it does not claim that any tenant has been tested or that a checklist alone establishes compliance.
Define the audit scope before collecting evidence
Start with the population you want to assess. Separate corporate-owned devices from personal devices, enrolled devices from app-protection-only use, and active endpoints from stale records. List Windows, macOS, iOS/iPadOS and Android populations separately. Shared devices, kiosks, contractors and privileged workstations may need different treatment.
Record the management model as well as the platform. A co-managed endpoint, an Intune-enrolled laptop and a personal phone using protected applications are not equivalent. Confirm which service owns each security setting and where you expect to find the resulting evidence. Include licences and integrations in the scope so recommendations are achievable with the tenant’s entitlements.
| Scope item | Information to record |
|---|---|
| Device population | Platform, ownership, business use, approximate count and active-device definition. |
| Management approach | Enrollment method, co-management responsibilities, app-only protection and exceptions. |
| Business access | Applications and data that devices can reach, including privileged administration. |
| Policy ownership | Responsible team, deployment groups, exclusions and change approval process. |
| Evidence period | Configuration snapshot date, report timestamps and agreed log-review window. |
Agree a predominantly read-only review. Policy changes, device wipes, retirements and production access-blocking tests belong in separately approved work. The audit should explain what was observed, what was sampled and what could not be verified.
Intune audit checklist: ten areas to review
| Area | Audit question | Evidence to request |
|---|---|---|
| Inventory and enrollment | Are the expected devices present, correctly classified and recently reporting? | Device inventory, enrollment restrictions and last check-in records. |
| Policy assignments | Do included groups, exclusions and filters match the intended population? | Assignment exports and representative effective-device results. |
| Compliance | What makes a device compliant, and how are unassigned or inactive devices handled? | Compliance policies, tenant settings and noncompliance actions. |
| Conditional Access | Does the intended access path actually require the relevant device state? | Entra policy configuration, exclusions and sign-in evidence. |
| Endpoint configuration | Are encryption, firewall, antivirus and other required settings applied? | Configuration and endpoint-security reports, including conflicts. |
| Updates | Are update policies translating into current devices? | Update assignments, deployment status and overdue exceptions. |
| BYOD and apps | Is company data protected in the supported applications people use? | App protection assignments, settings and representative results. |
| Administration | Who can alter policies, retrieve sensitive data or perform remote actions? | Roles, assignments, scope tags and privileged-access arrangements. |
| Auditability | Can significant changes be attributed and investigated? | Intune audit logs and configured downstream retention arrangements. |
| Lifecycle | Are exceptions, leavers, lost devices and stale records handled consistently? | Procedures, sampled tickets and evidence of completed actions. |
For every area, distinguish configuration evidence from operational evidence. A policy export explains intent; a device result explains deployment; a relevant access observation helps explain the consequence. The strongest findings connect all three.
Device compliance: examine the meaning behind the status
Intune compliance policies evaluate devices against configured requirements. Review the platform-specific settings, assignments and noncompliance actions. Pay particular attention to the tenant setting for devices with no compliance policy assigned: do not assume the label “compliant” proves that a substantive policy was evaluated.
Review the compliance-status validity period and the treatment of devices that stop reporting. Understand any grace periods before interpreting a status as an immediate enforcement decision. A point-in-time report should be accompanied by the device’s last check-in and the relevant policy status, especially when investigating an apparent mismatch.
As a practical sample, choose one expected compliant device, one noncompliant device, one recently enrolled device and one stale or exception device from each material population. Compare the assigned policies, actual state and documented business expectation. Expand the sample when it exposes systematic gaps; a convenient sample of healthy administrator laptops is rarely representative.
Compliance and Conditional Access must be reviewed together
Intune produces device-compliance information; Microsoft Entra Conditional Access can use it when deciding access to protected resources. An Intune compliance policy does not, on its own, establish that every Microsoft 365 access path is blocked for a noncompliant device. Review the corresponding Conditional Access policies, target resources, users, conditions, exclusions and enforcement state.
Check whether a policy is enabled or only in report-only mode. Review how its grant controls are combined rather than inferring enforcement from the policy name. Compare policy intent with relevant sign-in records and documented emergency-access arrangements. Microsoft describes prerequisites and exceptions in its device-compliance access guidance; account for those when defining the expected result.
Do not remove emergency exclusions or switch access policies to enforcement during an audit just to obtain a stronger-looking result. Record the exposure, propose a controlled rollout and agree testing and recovery arrangements. A useful recommendation reduces risk without unexpectedly locking out the workforce.
Microsoft: require device compliance with Conditional Access.
Endpoint security, baselines and configuration conflicts
Review the settings delivered through endpoint-security policies, configuration profiles, the settings catalog and security baselines. Look for overlapping assignments and conflicting values. Microsoft provides deployment reporting to help identify conflicts; an audit should investigate the affected settings and devices rather than merely count how many policies have been created.
For Windows devices, the agreed scope may include disk encryption, firewall configuration, antivirus, attack-surface reduction and endpoint detection and response integration. For other platforms, use the applicable platform capabilities and business requirements. Avoid issuing Windows-specific recommendations as if they apply unchanged to every endpoint.
Select a small number of high-impact settings and trace them end to end. Identify the policy intended to configure the setting, the population receiving it, any competing policy and the result on a representative device. If a report shows an error or conflict, preserve that uncertainty in the finding. “Assigned” and “successfully applied” are different observations.
Updates: check outcomes as well as deployment rings
An update ring is a deployment mechanism, not proof that endpoints are current. Review assignments, deferrals, deadlines, restart behaviour and exceptions against the organisation’s patching objectives. Then examine the reported outcome and the age of devices that are not progressing.
Build an exception view that distinguishes deliberately paused devices, deployment failures and devices that have not checked in. Those categories have different owners and remedies. A long-lived exception should have a business reason, an accountable owner, an expiry or review date and a compensating-control decision.
Microsoft’s update-ring reporting is a useful starting point. State which reports were examined and when. Where a device’s actual state cannot be confirmed, describe the evidence gap rather than converting missing information into a definitive claim that the endpoint is patched.
BYOD and app protection: separate device control from data control
Intune app protection policies can protect organisational data in supported applications, including scenarios without device enrollment. This is a different control model from managing the entire device. An audit should establish which model is intended for each population before classifying unenrolled devices as a failure.
Review the protected applications, user assignments, data-transfer restrictions, conditional launch settings and any exemptions. Investigate whether the applications and workflows employees actually use are covered. An approved mobile workflow may be well controlled while a different client or data-transfer path requires a separate policy decision.
For personal devices, document the boundary between corporate and personal data. Review the offboarding and selective-wipe procedure using records or an agreed test environment. Do not perform a destructive action on a user’s device merely to demonstrate that an audit check has been completed.
Administrative permissions and Intune audit logs
Review Intune RBAC roles, role assignments and scope tags alongside relevant Microsoft Entra roles. Ask who can change the controls being audited and whether their access extends beyond the devices or objects they need to manage. Scope tags affect visibility; evaluate the complete assignment rather than treating a tag name as proof of least privilege.
Include service principals, automation and delegated administration in the access discussion where they are part of the tenant’s operating model. Record ownership, business justification and review arrangements. An audit account should have only the access required for the agreed evidence collection, with temporary access removed at completion.
Microsoft: Intune role-based access control.
Intune audit logs record activities that generate changes. Use them to investigate selected policy, assignment or administrative changes and reconcile these with the organisation’s change records. Keep this distinct from endpoint security telemetry and Entra sign-in logs: each answers a different question.
Confirm the available evidence period and any export or downstream retention arrangement in the actual tenant. Avoid promising a universal retention period without checking the service and configuration. If the logs needed for the agreed review window are unavailable, record that limitation and its impact on the audit conclusion.
What a useful Intune audit finding looks like
Illustrative finding—not a result from a client tenant: the organisation expects corporate laptops to meet its device-compliance standard, but a recently introduced device group is excluded from the applicable assignment. The sample device has no assigned compliance policy. A related access path has not been demonstrated to enforce the intended restriction.
- Evidence: relevant policy and assignment identifiers, captured settings, sample-device state and collection timestamps.
- Impact: explain the access or management gap supported by the evidence; do not claim a breach occurred.
- Cause: determine whether the gap arose from group maintenance, filter logic, ownership or an approved exception.
- Recommendation: correct the intended coverage through a reviewed deployment and assess the connected access policies.
- Verification: recheck the device’s effective policy and compliance state, then validate the relevant access outcome under an agreed test plan.
Rate findings in business context. A policy conflict on a privileged workstation may deserve different treatment from the same observation on an isolated test device. Separate confirmed control failures, accepted exceptions and areas where evidence is insufficient.
What you should receive from an Intune audit
The report should give endpoint administrators a workable remediation queue and management an understandable account of risk. It should not be a raw export of every setting with the same priority attached to each row.
- Scope, evidence dates, sampled populations, access method and limitations.
- A coverage summary showing the relationship between expected devices, assignments and observed results.
- Prioritised findings with evidence, affected populations and likely business consequences.
- Recommendations that account for platform support, licences and operational dependencies.
- A remediation register with owners, proposed sequencing and verification criteria.
- A clear distinction between recommendations, changes completed and improvements subsequently verified.
The wider Office 365 security audit connects these endpoint findings with identity and collaboration exposure. An Intune-only review should explicitly state which of those adjacent controls remain outside its scope.
Intune audit: frequently asked questions
Is an Intune audit the same as reviewing Intune audit logs?
No. Audit logs are one source of evidence about changes. A security audit also reviews design, assignments, effective deployment, access dependencies and operating procedures.
Does an Intune audit require Global Administrator access?
Do not assume that broad permanent access is necessary. Define the evidence needed and agree appropriate read-only roles or supervised exports. Document where access limitations prevent a conclusion.
Can a device be enrolled without being adequately protected?
Yes. Enrollment establishes a management relationship; it does not prove that every intended security policy is assigned, applied or connected to access enforcement. Those relationships need review.
Can personal devices be included?
Yes, when they form part of the agreed scope. Evaluate their intended enrollment or app-protection model, supported applications and corporate-data controls without assuming the organisation should manage all personal content.
How often should we audit Intune?
Set a cadence based on risk and the rate of change. Major enrollment changes, acquisitions, new platforms, substantial policy redesign or an incident can justify an additional review. A periodic audit complements ongoing monitoring; it does not replace it.
Request an Intune audit for your Microsoft 365 environment
Atlant Security can scope an Intune review around your platforms, device populations, management model and business priorities. Start with approximate device numbers, the platforms you use, whether personal devices are allowed and the problems you want the audit to resolve.
Explore our Intune security audit service or wider Microsoft 365 security audit, build your audit RFP, or send your existing scope or NDA. Please use a business email address and keep credentials and sensitive device exports out of the initial enquiry.
Microsoft sources and further reading
- Microsoft: device compliance policies
- Microsoft: require device compliance with Conditional Access
- Microsoft: endpoint security policies and conflicts
- Microsoft: Intune reports
- Microsoft: app protection policies
- Microsoft: Intune role-based access control
- Microsoft: Intune audit logs
- Microsoft: Windows update ring reports
Reviewed 13 October 2026. Product capabilities, supported platforms and licence requirements can change. Confirm recommendations against the tenant and assessment date.
Published by Atlant Security. Sources, editorial policy and corrections.

