Skip to content

Allow only managed, compliant and protected devices

This guide builds an access policy that lets a laptop onto the corporate network only when it is managed by Intune, compliant, and has a SentinelOne agent without active threats. Everything else is denied or sent to a restricted VLAN.

Airgate pulls the device lists from Intune, SentinelOne and CrowdStrike on a schedule and stores their facts as Endpoint attributes. Access rules check those attributes at every sign-in.

Sign-in How Airgate finds the device’s facts
Any sign-in By the MAC address of the session: the Wi-Fi and Ethernet MACs Intune reports, the interface MACs SentinelOne and CrowdStrike report.
EAP-TLS with an IntuneDeviceId:// SAN in the certificate By the Intune device ID, whatever MAC the device uses. SentinelOne and CrowdStrike agents are then found by the device’s hardware MACs (as Intune reports them) or its serial number. See Intune device ID matching.

Devices that report no MAC address to a sync are skipped by that sync.

  • An Entra role that can register an app and grant admin consent (for Intune).
  • A SentinelOne console administrator (for SentinelOne), or a Falcon administrator who can create API clients (for CrowdStrike).
  • In Airgate: Tenant Administrator (integrations need admin access) and a role that can change access policies.
  • Devices sign in with certificates (Intune SCEP), ideally with the Intune device ID in the certificate.

In Entra ID

  1. In the Microsoft Entra admin center, open Entra ID › App registrations › New registration. Name it Airgate Intune sync, single tenant, no redirect URI.
  2. API permissions › Add a permission › Microsoft Graph › Application permissions › DeviceManagementManagedDevices.Read.All. Select Grant admin consent.
  3. Certificates & secrets › New client secret; copy the Value.
  4. From Overview, copy the Directory (tenant) ID and Application (client) ID.

In Airgate

  1. Open Integrations › Microsoft Intune.
  2. Under Connect Microsoft Intune, enter the Directory (tenant) ID, Application (client) ID and Client secret.
  3. Leave Sync devices on and choose the interval (Every 15 minutes to Once a day; default Every hour).
  4. Select Connect, then Test connection. The first sync starts within a minute; Devices synced, Last sync and the device list fill in.

Synced attributes include Intune Managed (true while Intune manages the device, false once it leaves Intune), Intune Compliance State (compliant, noncompliant, inGracePeriod, conflict, error, unknown), MDM Compliant, Intune Managed Device Owner Type, Intune Operating System and Intune Is Encrypted.

In SentinelOne

  1. In the SentinelOne management console, open Settings › Users › Service Users and create a service user with the Viewer role on the account or sites to sync.
  2. Generate its API token and copy it (shown once). A console user’s token also works: My User › Options › Generate API token.

In Airgate

  1. Open Integrations › SentinelOne.
  2. Enter the Management console URL (for example https://usea1-partners.sentinelone.net) and the API token.
  3. Select Connect, then Test connection.

API tokens expire. Replace the token on this page before it expires, or the sync starts failing. Decommissioned agents are synced too (SentinelOne Is Decommissioned = true).

Step 3 (optional): Connect CrowdStrike Falcon

Section titled “Step 3 (optional): Connect CrowdStrike Falcon”
  1. In the Falcon console, open Support and resources › API clients and keys › Create API client. Give it the Hosts: Read scope (add Zero Trust Assessment: Read for scores). No write scopes are needed.
  2. Copy the client ID and secret, and note the cloud shown as the base URL.
  3. In Airgate, open Integrations › CrowdStrike Falcon. Choose the Cloud (US-1, US-2, EU-1 or US-GOV-1), enter the Client ID and Client secret, turn on Fetch Zero Trust Assessment scores if you added that scope, select Connect, then Test connection.
  1. Open Access › Access policies and open the policy for the corporate SSID (or Add a policy › Employees).

  2. Applies when: Connection 802.1X, Wi-Fi networks (SSID) Corp-WiFi.

  3. Sign-in: Allowed methods EAP-TLS; Check accounts in your Entra ID directory.

  4. Add the rules (Add a rule, then Add condition for each line):

    Order Rule name When (all must be true) Then
    1 Managed and protected Intune managed = Yes (managed by Intune); Intune compliance = Compliant; SentinelOne agent = Installed (found in SentinelOne); SentinelOne threats = None (clean) Allow, VLAN 20
    2 Managed, needs attention Intune managed = Yes (managed by Intune) Allow, VLAN 99 (remediation), or Deny
    Default no rule above matches Deny
  5. Select Done for each rule, then Save changes.

The first matching rule wins. A device that was never in Intune or SentinelOne has no such attribute, so a condition that requires Yes does not match it and the device falls through to the next rule.

  1. On Integrations › Microsoft Intune, the device list shows the laptop with Compliance, OS, Ownership and User. Select a row for all attributes.
  2. Devices: open the laptop’s MAC; the same attributes are on the endpoint.
  3. Access › Test access › A device (MAC address) with the MAC shows which rule matches.
  4. After a real sign-in, open the entry in Monitor › Sign-in log. A denied device shows, for example, Denied: intune compliance check failed with the facts that failed (Intune compliance: noncompliant (needs compliant)).
Symptom Cause Fix
Test connection fails for Intune with HTTP 403 DeviceManagementManagedDevices.Read.All is not consented. Grant admin consent.
Banner The last sync failed Expired secret or token, or permissions changed. Update the credential and select Save, then Sync now.
Sign-in log: Denied: managed by Intune check failed, not found in Intune (device MAC not in the Intune sync) The device’s MAC is not among the synced MACs. Check the device on Integrations › Microsoft Intune; add the Intune device ID to the certificate.
Same denial with … the device uses a private Wi-Fi address and its certificate has no Intune device ID Private Wi-Fi address and an old certificate. Intune device ID matching.
Sign-in log: Denied: intune compliance check failed The device is not compliant in Intune. Fix the device in Intune, then Sync now on Integrations › Microsoft Intune.
Sign-in log: Denied: sentinelOne agent check failed, not found in SentinelOne No agent, or the agent’s MAC does not match. Install or re-register the agent; Sync now on Integrations › SentinelOne.
Sign-in log: Denied: sentinelOne threats check failed, infected SentinelOne reports an active threat. Resolve the threat in SentinelOne; Sync now.
Attributes disappeared The sync was turned off or the connection deleted (this removes the attributes it wrote). Turn the sync back on. Connection enabled off only pauses the sync and keeps the attributes.
© 2026 Airowire Networks Pvt. Ltd. Airgate is a product of Airowire.Product · Release notes · Security