Skip to content

Device compliance

Device compliance lets an access policy check more than who signs in: is the device managed by Intune and compliant, is the SentinelOne agent installed and clean, is CrowdStrike Falcon running. This page explains how those facts reach Airgate, how Airgate matches them to the device that signs in, and what happens with private (randomised) Wi-Fi addresses.

Intune / Jamf Pro / CrowdStrike / SentinelOne (cloud APIs)
│ periodic device sync (default every hour, or Sync now)
▼
Airgate device store ── matched by MAC address ──▶ Devices (endpoint attributes)
│ │
│ EAP-TLS certificate with IntuneDeviceId://<id> │
└──────────── matched by Intune device ID ─────────▶ Endpoint:* at sign-in
│
▼
rule conditions, for example
Endpoint:Intune Compliance State EQUALS compliant

Airgate does not ask the device sources at sign-in time. It syncs them in the background and stores what it learns, so sign-ins are fast and keep working if a source is briefly unreachable.

Source Where What it syncs
Microsoft Intune Integrations › Microsoft Intune Intune managed devices from Microsoft Graph: compliance state, ownership, OS, encryption, user and more. Needs an app registration with the Graph application permission DeviceManagementManagedDevices.Read.All.
CrowdStrike Falcon Integrations › CrowdStrike Falcon Hosts running the Falcon sensor: status (including containment), provisioning, reduced functionality mode, platform, tags and, optionally, Zero Trust Assessment scores.
SentinelOne Integrations › SentinelOne Agents: active, up to date, infected, active threats, network status and quarantine, mitigation mode, site and group. Needs an API token with viewer access.
Jamf Pro API only (context server type jamf) Computers and mobile devices: managed state, OS, model, serial number, owner, FileVault state. There is no console page for it.

Each page shows the number of devices synced, the Last sync, the Next sync and the Connection state, and offers Test connection and Sync now. The Sync interval can be Every 15 minutes, Every 30 minutes, Every hour (default), Every 4 hours or Once a day.

  • Connection enabled off pauses the sync and keeps the attributes already written.
  • Turning the sync off removes the source’s attributes from every endpoint.

Every sync matches the source’s devices to Airgate endpoints by MAC address:

Source MAC addresses used
Intune The Wi-Fi and Ethernet MAC addresses Intune reports. Intune does not report a MAC address for every platform (for example Android work profiles); those devices are skipped.
Jamf Pro The computer’s MAC and alternate MAC; the mobile device’s Wi-Fi and Bluetooth MAC.
CrowdStrike Falcon The host’s MAC address and connection MAC address.
SentinelOne The physical MAC addresses of the agent’s network interfaces, without virtual interfaces (VPN, AirDrop and similar) that never sign in to the network.

Airgate writes a device’s facts to the endpoint only when they changed since the previous sync. When a device leaves the source, its endpoint gets a “gone” marker instead: Intune Managed, MDM Enabled and MDM Compliant become false for Intune; SentinelOne System Found or CrowdStrike System Found becomes false for those sources. If two devices report the same MAC address, the one that checked in most recently wins.

The attributes appear under Devices on the endpoint and in the Endpoint namespace for rules. The policy attributes reference lists them all.

Phones and laptops join Wi-Fi with a private (randomised) MAC address. That address matches none of the hardware MAC addresses the sources report, so a managed, compliant device would look unknown.

For devices that sign in with an Intune SCEP certificate, Airgate solves this with the Intune device ID:

  1. In the Intune SCEP certificate profile, add a Subject alternative name of type URI with the value IntuneDeviceId://{{DeviceId}}. Intune replaces {{DeviceId}} with the device’s Intune ID.
  2. At an EAP-TLS sign-in, Airgate reads the ID from the certificate into Certificate:Intune-Device-Id.
  3. It looks up the Intune record with that ID, and adds its facts to the Endpoint namespace for this sign-in.
  4. It then finds the device’s SentinelOne and CrowdStrike agents by the hardware MAC addresses Intune reports for the device, or by its serial number, and adds their facts too.
  5. These facts take precedence over whatever was matched by the sign-in’s MAC address. The trace shows Intune device ID <id>: "<name>" (MAC …); facts from intune, sentinelone.

Without the URI in the certificate, a device on a private address is matched by MAC only. When such a sign-in is denied by an Intune or SentinelOne condition, the Sign-in log says so: not found in Intune: the device uses a private Wi-Fi address and its certificate has no Intune device ID. Until the device has the new certificate, turning Private Wi-Fi address off for that network on the device also works.

On Access › Access policies, a rule can test Intune managed, Intune compliance, SentinelOne agent, SentinelOne threats, CrowdStrike sensor, CrowdStrike containment, Managed by an MDM (MDM Enabled, written by Intune and Jamf Pro) and MDM compliance (MDM Compliant) directly. Any other synced attribute can be tested with a condition on the Endpoint namespace through the API, for example Endpoint:CrowdStrike Assessment Overall GREATER_THAN 70.

Typical rules for a Wi-Fi network for company laptops:

Order When Then
1 Intune managed Yes and Intune compliance Compliant and SentinelOne threats None (clean) Allow, corporate VLAN or role
2 Intune managed Yes Allow, quarantine VLAN or role
Default Deny
© 2026 Airowire Networks Pvt. Ltd. Airgate is a product of Airowire.Product · Release notes · Security