Skip to content

How Intune SCEP works with Airgate

With Microsoft Intune, managed laptops and phones get a Wi-Fi certificate from Airgate’s own CA and join the network with EAP-TLS. Nobody types a password, there is nothing to phish, and a lost device loses access when its certificate is revoked. Airgate acts as a third-party SCEP CA for Intune: no NDES server and no on-premises connector are needed.

This page explains how the pieces fit and sets up the Airgate side once. Then follow the guide for each platform:

Intune ──3 profiles──▶ device
│ 1. SCEP request with Intune's one-time challenge
▼
https://nac.contoso.com/scep/<tenant slug> (Airgate)
│ 2. "Is this request genuine?"
▼
Intune SCEP validation service ──▶ "Success"
│ 3. Airgate's Onboard CA issues the certificate
│ 4. Airgate reports the certificate to Intune
▼
device ──EAP-TLS──▶ AP / controller ──RADIUS──▶ Airgate ──▶ access policy ──▶ VLAN / role
  1. Intune pushes three profiles to the device: a Trusted certificate profile (the Airgate root), a SCEP certificate profile and a Wi-Fi profile.
  2. The device sends a SCEP request to Airgate’s SCEP URL. The request carries a one-time challenge that Intune created for this device and profile.
  3. Airgate asks Intune to validate the request. Only when Intune answers “Success” does Airgate issue the certificate from the tenant’s Onboard CA.
  4. Airgate tells Intune that the certificate was issued (or that it failed), so the certificate shows in the Intune admin center.
  5. The device joins Wi-Fi with EAP-TLS. Airgate checks the certificate against its own CA and applies your access policy.
Intune profile Contains References
Trusted certificate The Airgate Platform Root CA (.cer) Nothing
SCEP certificate Subject, SAN, key settings, Airgate’s SCEP Server URL Root Certificate = the trusted certificate profile
Wi-Fi (Enterprise, EAP-TLS) SSID, RADIUS server name Server trust: Root certificate = the trusted certificate profile. Client authentication: Client certificate = the SCEP certificate profile

Assign all three profiles to the same group (users or devices). A profile that references another one only works on devices that also receive the referenced profile.

  • Owner: the UPN in the subject alternative name, else the email SAN, else the CN. It shows as Owner under Certificates › Issued certificates.
  • Subject and SAN: Airgate keeps the CN from the request and copies the UPN, email, DNS and URI SANs, including IntuneDeviceId://{{DeviceId}} (see Match devices by Intune device ID). The certificate gets OU=Intune.
  • Lifetime: set by Airgate (Certificate lifetime (days) in the SCEP settings), not by the Intune profile’s validity period.
  • Keys: RSA 2048 to 8192 bits, or ECDSA P-256, P-384 or P-521. Other keys are refused.
  • User name at sign-in: for EAP-TLS, Airgate uses the certificate’s CN as the user name. With CN={{UserPrincipalName}}, the Sign-in log shows alice@contoso.com and group rules can look the user up in Entra ID.
  • Microsoft Intune with enrolled devices, and an Intune Administrator.
  • A Microsoft Entra role that can register an app and grant admin consent.
  • Airgate reachable from the internet over HTTPS. Devices request and renew certificates from wherever they are. PUBLIC_URL must be that address, because the SCEP URL is built from it (see Certificates and trust).
  • The RADIUS server name decided (Certificates › Server certificates › Platform EAP certificate › Server names).
  • Access points or a controller that use Airgate as their RADIUS server (Network › Switches and APs).

Step 1: Register an app in Entra ID for SCEP validation

Section titled “Step 1: Register an app in Entra ID for SCEP validation”

Airgate uses this app to ask Intune whether a SCEP request is genuine.

  1. In the Microsoft Entra admin center, open Entra ID › App registrations and select New registration.
  2. Name it Airgate SCEP, choose Accounts in this organizational directory only (Single tenant), leave Redirect URI empty and select Register.
  3. Open API permissions › Add a permission and add both:
    • APIs my organization uses › search Intune (the Microsoft Intune API) › Application permissions › scep_challenge_provider (SCEP challenge validation).
    • Microsoft Graph › Application permissions › Application.Read.All. Airgate uses it to find your tenant’s Intune SCEP validation service.
  4. Select Grant admin consent for . Both permissions must show Granted.
  5. Open Certificates & secrets › New client secret, and copy the Value (shown once). Note the expiry date.
  6. On Overview, copy the Application (client) ID and Directory (tenant) ID.

You may use one app for SCEP validation, the Intune device sync and the Entra ID directory, as long as it has all the permissions each one needs.

Step 2: Turn on SCEP and Intune validation in Airgate

Section titled “Step 2: Turn on SCEP and Intune validation in Airgate”
  1. Open Certificates › Certificate authorities.
  2. Select the Onboard CA row whose status is Active. The drawer Certificate authority opens.
  3. In the SCEP section, select Issue certificates from this CA over SCEP.
  4. Copy the SCEP URL with the copy button. It has the form https://<console host>/scep/<tenant slug>, for example https://nac.contoso.com/scep/contoso.
  5. Set Certificate lifetime (days) (1 to 3650; for example 365).
  6. Leave Static challenge empty. It is for MDMs with a fixed SCEP password (Jamf, Workspace ONE), not for Intune.
  7. Select Check SCEP requests with Microsoft Intune and enter the Directory (tenant) ID, Application (client) ID and Client secret from step 1.
  8. Select Save SCEP settings.
  9. Select Test Intune connection. It shows Connected. Validation service: followed by your tenant’s Intune SCEP service address.

Step 3: Check that devices can reach the SCEP URL

Section titled “Step 3: Check that devices can reach the SCEP URL”

From a network outside your office, open:

https://nac.contoso.com/scep/contoso?operation=GetCACaps

It must answer with a list that includes POSTPKIOperation, SHA-256 and SCEPStandard. A browser warning means the console certificate is not trusted publicly; devices need to trust it too (upload a public certificate for the console, or push the Airgate root first).

  1. Open Certificates › Certificate authorities.
  2. Select the Platform Root CA row. In the drawer, under Certificate, select DER. You get a .cer file for the Intune Trusted certificate profile.

Follow the platform guide:

Step 6: Allow certificates in the access policy

Section titled “Step 6: Allow certificates in the access policy”
  1. Open Access › Access policies and open (or Add a policy › Employees) the policy for the SSID, for example Corp-WiFi.
  2. Under Allowed methods, select EAP-TLS.
  3. To use Entra ID groups, add the Entra ID directory under Check accounts in (Entra ID).
  4. Add rules, for example User is in group › Entra ID › Staff › Allow, VLAN 20; or require a managed, compliant device (Device compliance policy).
  5. Select Save changes.
  1. On the device: sync it (Windows: Settings › Accounts › Access work or school › your account › Info › Sync; Company Portal: Sync). The certificate arrives within a few minutes.
  2. In Intune: open the SCEP profile › Device status or User status: the device shows Succeeded.
  3. In Airgate: Certificates › Issued certificates lists the certificate; under Issued by it shows the Onboard CA and SCEP (Intune).
  4. Connect to the SSID. Monitor › Sign-in log shows the sign-in with EAP-TLS, the matched rule and the VLAN.
  • One device: open Certificates › Issued certificates, find the certificate (search by owner, device, MAC or serial), select Revoke, choose a Reason and keep Disconnect active sessions on. The device cannot sign in again with that certificate.
  • Leavers: remove the user from the Intune assignment group, then revoke their certificates as above.

Airgate does not pick up revocations from Intune when a device is wiped or retired. Revoke in Airgate as part of your offboarding.

Symptom Cause Fix
Test Intune connection: intune: invalid_client: AADSTS7000215 … Wrong or expired client secret. Create a new secret, paste it, Save SCEP settings.
Test Intune connection: intune: unauthorized_client: AADSTS700016 … Wrong application ID or tenant. Check both IDs.
Test Intune connection: intune: ServiceDiscoveryFailed: … Application.Read.All not consented, or the tenant has no Intune licence. Grant admin consent (step 1.4).
Intune shows the SCEP profile as Failed; Monitor › Logs shows SCEP request refused by Intune Intune rejected the request, for example ChallengeExpired, SubjectNameMismatch, SubjectAltNameMismatch; or scep_challenge_provider is not consented (Forbidden). Sync the device again; check the profile; grant consent.
Monitor › Logs shows SCEP CSR key refused Key type or size not accepted. Use RSA 2048 (or larger) in the SCEP profile.
GetCACaps does not answer from outside Airgate is not reachable from the internet, or PUBLIC_URL is wrong. Publish Airgate over HTTPS and set PUBLIC_URL.
Sign-in log: The device didn’t trust Airgate’s RADIUS certificate Root profile missing, or the Wi-Fi profile’s server name differs from the RADIUS certificate. Check the trusted certificate profile and Certificate server names.
Sign-in log: The device’s certificate isn’t from a CA Airgate trusts The Wi-Fi profile uses another certificate (an old PKI). Point the Wi-Fi profile’s client certificate at the Airgate SCEP profile.
Sign-in log: The device’s certificate has expired The certificate was not renewed. Sync the device; check the renewal threshold.
Sign-in log: The device’s certificate was revoked Revoked in Airgate. Expected for retired devices; otherwise sync to get a new one.
© 2026 Airowire Networks Pvt. Ltd. Airgate is a product of Airowire.Product · Release notes · Security