Devices
Laptops and phones
Encryption, device rules, malware protection
Measured score
56
Partial assessment · 1 left out of the score
Needs attention (5)
- SeriousNeeds fixingLaptops and phones
Fix noncompliant devices
What this means
2 of 5 devices (40%) are actively non-compliant. Each represents a control you've defined that's currently being violated.
What to do
Review each non-compliant device: address the specific failing setting (disk encryption, OS version, antivirus, etc.) or remove the device from Intune if it's no longer in use.
- Who does it
- Your IT person or provider
- How long
- About 1 hour
2 evidence rowsTechnical detailssetting, steps, evidence
The setting
Intune device compliance status
Intune admin center → Devices → All devices (filter by Compliance: Not compliant)
Now: 2 non-compliant, 0 in grace period, 0 not evaluated (of 5 enrolled)→Should be: 0 devices in noncompliant / conflict / error state
Open in the admin portal ↗Steps
- intune.microsoft.com → Reports → Device compliance → Noncompliant devices
- Drill into each device → see specific policy items failing
- Common fixes: re-encrypt disk, update OS, enable Defender, restart agent
PowerShell
# Trigger a sync from PowerShell on a Windows device: Get-ScheduledTask -TaskPath "\Microsoft\Windows\EnterpriseMgmt\*" | Where-Object {$_.TaskName -eq 'PushLaunch'} | Start-ScheduledTaskEvidence · 2 recorded items
- CONTOSO-LT-07 (Windows 10.0.19045) — (no user) · noncompliant · owner: company
- RECEPTION-PC (Windows 10.0.19045) — (no user) · noncompliant · owner: company
Learn more ↗How an attacker would use it
Non-compliant devices are precisely the devices you've identified as risky (unencrypted, outdated, missing AV). An attacker who lands on one has an easier time persisting and exfiltrating — exactly the scenario your compliance policy was designed to flag.
- SeriousNeeds fixingLaptops and phones
Require BitLocker on Windows
What this means
2 Windows devices report BitLocker disabled. Each unencrypted device is a data-breach incident waiting for a theft or loss.
What to do
Make BitLocker mandatory via a compliance policy setting. Devices that fail will be marked non-compliant and (with a CA policy) blocked from corp resources until encrypted.
- Who does it
- Your IT person or provider
- How long
- About 1.5 hours
- Before you change it
- Devices currently unencrypted will be marked non-compliant. Users will need to enable BitLocker (15-60 min per device depending on disk size). Push the policy with a grace period so users have time.
2 evidence rowsTechnical detailssetting, steps, evidence
The setting
BitLocker / disk encryption policy
Intune admin center → Endpoint security → Disk encryption
Now: 2 Windows devices with BitLocker disabled, 0 with unknown status (of 4 total)→Should be: BitLocker required by compliance policy and enabled on all Windows devices
Open in the admin portal ↗Steps
- intune.microsoft.com → Devices → Compliance policies
- Open your Windows compliance policy (or create one)
- System Security → Encryption → 'Require encryption of data storage' → Require
- Save
- Then: Devices → Configuration profiles → Create profile → Windows → Endpoint protection → BitLocker base settings → Enable
Evidence · 2 recorded items
- CONTOSO-LT-07 — (no user) · 10.0.19045 · BitLocker DISABLED
- RECEPTION-PC — (no user) · 10.0.19045 · BitLocker DISABLED
Learn more ↗How an attacker would use it
Laptop is stolen or lost. Without BitLocker, the attacker boots from USB or removes the disk and mounts it on another machine. All OneDrive sync content, cached Outlook items, saved attachments, and Teams data are readable as files. No password prompt, no audit signal — pure offline data theft.
- SeriousNeeds fixingLaptops and phones
Require compliant devices
What this means
No Conditional Access policy requires a compliant device for any application. Your compliance evaluation is purely descriptive — it tells you who's non-compliant but doesn't prevent non-compliant (or attacker-controlled, unenrolled) devices from accessing corp data.
What to do
Create a CA policy requiring 'Compliant device' (or 'Hybrid Azure AD joined device') for access to all cloud apps, or at minimum for sensitive apps (Exchange, SharePoint, finance apps).
- Who does it
- Your IT person or provider
- How long
- About 45 minutes
- Before you change it
- Users on non-Intune-enrolled devices will be blocked from sign-in. This is the intended behavior but will affect: BYOD users without Intune enrollment, kiosks, contractors with their own devices. Plan exceptions or alternative paths (MAM-only, App Protection Policies, etc.) before enforcing.
1 evidence rowTechnical detailssetting, steps, evidence
The setting
Conditional Access — require compliant device grant
Entra admin center → Protection → Conditional Access → Policies
Now: 1 CA policy enabled, none requiring compliant or hybrid-joined device→Should be: At least one enabled CA policy granting access only when the device is marked compliant or hybrid-joined
Open in the admin portal ↗Steps
- entra.microsoft.com → Protection → Conditional Access → New policy
- Name: 'Require compliant device — all apps'
- Users: All users; Exclude: break-glass account, service accounts that use modern auth from non-Intune systems
- Cloud apps: All cloud apps (or scope to Exchange/SharePoint first)
- Grant: Grant access → Require device to be marked as compliant (and/or Require Hybrid Azure AD joined device) → Require one of the selected controls
- Enable in Report-only for 2 weeks first, review impact, then switch On
Evidence · 1 recorded item
- No CA policy requires compliant device — 1 CA policies enabled, none make a compliant or hybrid-joined device mandatory for access
Learn more ↗How an attacker would use it
Attacker phishes a user's password. From their own laptop (unenrolled, unmanaged, perhaps compromised) they sign in and access mail, SharePoint, Teams. Your enrolled-device controls — compliance, BitLocker, Defender — protect zero data in this scenario because the access happens from a device they were never installed on.
- Should fixNeeds fixingLaptops and phones
Set compliance policies per platform
What this means
1 OS platform with enrolled devices has no assigned compliance policy: iOS. Devices on these platforms cannot be evaluated for compliance, so CA policies requiring 'compliant device' will treat them inconsistently.
What to do
Create a compliance policy for each missing platform. Start with the Intune compliance baseline as a template.
- Who does it
- Your IT person or provider
- How long
- About 30 minutes
- Before you change it
- Devices already enrolled that fail the new policy will be marked non-compliant. Use a grace period (Actions for noncompliance) so users have 7+ days to remediate before access is blocked.
4 evidence rowsTechnical detailssetting, steps, evidence
The setting
Intune compliance policies
Intune admin center → Devices → Compliance policies → Policies
Now: No assigned compliance policy for: iOS→Should be: At least one compliance policy assigned for every enrolled OS platform
Open in the admin portal ↗Steps
- intune.microsoft.com → Devices → Compliance policies → Create policy
- Platform: select the missing platform → Create
- Use the Microsoft baseline as a starting point
- Assign to All users / All devices
Evidence · 4 recorded items
- Windows — 4 devices enrolled · assigned policy exists
- iOS — 1 device enrolled · NO ASSIGNED POLICY
- Android — 0 devices enrolled · NO ASSIGNED POLICY
- macOS — 0 devices enrolled · NO ASSIGNED POLICY
Learn more ↗How an attacker would use it
An attacker who phishes a user and signs in from an attacker-controlled device should be blocked by a CA policy requiring a compliant device. With no compliance policy for the user's OS, the policy evaluates 'unknown' and the attacker's sign-in proceeds.
- Should fixNeeds a lookLaptops and phones
Onboard devices to Defender
What this means
4 Windows devices are enrolled in Intune but no Defender for Endpoint or Defender for Business license is detected on the tenant. Endpoints run with built-in AV only — no EDR signal feeds your security team.
What to do
Add Defender for Business (bundled with M365 Business Premium) or Defender for Endpoint Plan 1/2.
- Who does it
- Your IT person or provider
- How long
- Not estimated
1 evidence rowTechnical detailssetting, evidence
The setting
Defender for Endpoint / Business licensing
Microsoft 365 admin center → Billing → Purchase services (then onboard in Microsoft Defender portal → Settings → Endpoints)
Now: 4 Windows devices enrolled; no Defender for Endpoint or Defender for Business licence detected in the tenant→Should be: Defender for Business or Defender for Endpoint P1/P2 licensed and provisioned
Open in the admin portal ↗Learn more ↗Evidence · 1 recorded item
- Tenant Defender capability — No DefenderForBusiness / DefenderForEndpoint_P1 / DefenderForEndpoint_P2 detected
Not verified (1)
- Not verifiedLaptops and phones
Resolve high-severity alerts
What this means
The Defender alerts queue could not be read. Unresolved alerts and detection coverage are unknown; this does not establish whether Defender is provisioned or monitoring the tenant.
How to check it
Review the alerts queue in Microsoft Defender, then check product access and the scanner's existing consent before rescanning.
Technical detailssetting, evidence
The setting
Defender XDR alerts queue
Microsoft Defender portal → Incidents & alerts → Alerts
Now: Unknown — the scan could not read the queue→Should be: Readable alert evidence for the intended scope
Open in the admin portal ↗Evidence · 1 recorded item
- Alerts queue could not be assessed — Endpoint not captured in snapshot (collector reported: Insufficient privileges (Defender plan not licensed)): /security/alerts_v2
In good shape (2)
- In good shapeLaptops and phones
Remove stale devices
All 5 enrolled devices have synced in the last 30 days.
- In good shapeLaptops and phones
Protect apps on mobile devices
Assigned app-protection configuration was found for iOS and Android. Review other platforms and actual deployment before concluding that all mobile access is protected.
Technical detailssetting, evidence
The setting
Intune App Protection policies
Intune admin center → Apps → App protection policies
Now: Assignments found for iOS, Android→Should be: Required apps and users covered on the platforms in use, with deployment verified
Open in the admin portal ↗Learn more ↗Evidence · 2 recorded items
- iOS app-protection policies — 1 explicitly assigned; 1 policies returned; 0 assignment states unknown
- Android app-protection policies — 1 explicitly assigned; 1 policies returned; 0 assignment states unknown
Does not apply (1)
- Does not applyLaptops and phones
Require FileVault on Macs
No Macs enrolled in Intune.