Match devices by Intune device ID
Phones and laptops increasingly join Wi-Fi with a private (random) MAC address. Airgate’s device syncs (Intune, SentinelOne, CrowdStrike) know devices by their hardware MAC addresses, so a managed, compliant laptop on a private address looks unknown and rules that require Intune managed deny it.
This guide fixes that by adding the Intune device ID to the SCEP certificate. At sign-in, Airgate reads the ID from the certificate and looks the device up by its ID instead of its MAC.
How it works
Section titled “How it works” SCEP profile SAN: URI = IntuneDeviceId://{{DeviceId}} │ ▼ certificate SAN: URI:IntuneDeviceId://1f2e3d4c-… │ EAP-TLS sign-in (any Wi-Fi address) ▼ Airgate: Certificate:Intune-Device-Id = 1f2e3d4c-… │ ├── Intune sync record with that device ID → Intune Managed, Intune Compliance State, … └── SentinelOne / CrowdStrike agent found by the device's hardware MACs (as Intune reports them) or its serial number → SentinelOne System Found, … ▼ Endpoint attributes for this sign-in → access policy rules- The lookup runs for EAP-TLS sign-ins whose certificate has a URI SAN
IntuneDeviceId://<id>(any letter case; a trailing/is ignored). - Airgate sets the attribute
Certificate:Intune-Device-Idto the ID. - The facts found by device ID override the facts found by the session’s MAC address for that sign-in.
- Devices without the SAN keep being matched by MAC address as before.
Before you begin
Section titled “Before you begin”- Intune SCEP is set up and devices already get Airgate certificates.
- Integrations › Microsoft Intune is connected and syncing (see Device compliance policy). The lookup searches the devices of this sync.
- Optional: Integrations › SentinelOne or CrowdStrike Falcon connected.
Step 1: Add the device ID to every SCEP profile
Section titled “Step 1: Add the device ID to every SCEP profile”For each platform’s SCEP certificate profile in Intune:
- Open Devices › Manage devices › Configuration, select the SCEP certificate profile and open Properties › Configuration settings › Edit.
- Under Subject alternative name, add a row: Attribute
URI, ValueIntuneDeviceId://{{DeviceId}}. Keep the existing UPN row. - Select Review + save › Save.
Windows, macOS and iOS/iPadOS offer the URI attribute. For Android Enterprise, add it where your tenant offers it.
{{DeviceId}} is the Intune device ID, the same ID Airgate’s Intune sync
stores for the device (Graph managedDevice.id).
Step 2: Roll out the new certificates
Section titled “Step 2: Roll out the new certificates”Intune deploys the changed profile at the next device check-in, and devices request a certificate with the new SAN. A device that keeps its old certificate gets the new one at renewal (the Renewal threshold (%)).
During the rollout:
- Old certificates (without the device ID) keep working and keep being matched by MAC address. They stay valid until they expire.
- New certificates are matched by device ID.
- To move a device at once, revoke its old certificate: Certificates › Issued certificates, search by owner or device, select Revoke. Then sync the device so Intune requests a new one. Do this only after the new certificate is on the device, or the device is offline until it gets one.
Until a device has the new certificate, turning off the private address for the corporate SSID also works (macOS: System Settings › Wi-Fi › Details… › Private Wi-Fi address › Off; iOS: Settings › Wi-Fi › (i) › Private Wi-Fi Address; Windows: Settings › Network & internet › Wi-Fi › Random hardware addresses).
Step 3: Use the facts in rules
Section titled “Step 3: Use the facts in rules”Nothing changes in your rules. Intune managed, Intune compliance, SentinelOne agent and SentinelOne threats now also match devices on private addresses (Device compliance policy).
Verify
Section titled “Verify”- On a device with a new certificate, check the SAN (Windows:
certmgr.msc› Personal › the certificate › Details › Subject Alternative Name showsURL=IntuneDeviceId://…). - Connect, then open the entry in Monitor › Sign-in log:
- Trace tab: a line such as
Intune device ID 1f2e3d4c-…: "ALICE-LAPTOP" (MAC a4:83:e7:11:22:33); facts from intune, sentinelone. - Computed attributes tab:
Certificate:Intune-Device-Idand theEndpointattributes from Intune (and SentinelOne or CrowdStrike).
- Trace tab: a line such as
Other trace lines:
| Trace line | Meaning |
|---|---|
Intune device ID <id>: not in the Intune sync |
The ID is not among the synced Intune devices: the device was not synced yet, was removed, or reports no MAC address to Intune (such devices are not stored by the sync). |
Intune device ID <id>: lookup failed: … |
A database error; the decision was made without the device facts. |
Troubleshooting
Section titled “Troubleshooting”| Symptom | Cause | Fix |
|---|---|---|
Sign-in log: Denied: managed by Intune check failed, fact not found in Intune: the device uses a private Wi-Fi address and its certificate has no Intune device ID |
The device’s certificate predates step 1. | Sync the device to get a new certificate, or revoke the old one; meanwhile turn off the private address. |
Same denial with not found in Intune (device MAC not in the Intune sync) |
No device ID in the certificate and the MAC is not in the sync. | Add the SAN; check the device under Integrations › Microsoft Intune. |
Trace: not in the Intune sync although the certificate has the ID |
The device is not in the sync (new device, no MAC reported, or the sync failed). | Select Sync now on Integrations › Microsoft Intune; check the last sync. |
| Intune facts found, SentinelOne missing | The agent’s MAC and serial do not match what Intune reports. | Check the device on Integrations › SentinelOne; select Sync now. |
| No trace line about the device ID | The sign-in is not EAP-TLS, or the certificate has no IntuneDeviceId:// URI. |
Check the certificate’s SAN. |