Deploy Wi-Fi certificates to Windows with Intune SCEP
This guide creates the three Intune profiles for Windows 10 and Windows 11. At the end, every PC in the assigned group has a user certificate from Airgate and joins your secure SSID with EAP-TLS, without any prompt.
The setting names below are those of the Intune admin center at the time of writing. Microsoft renames settings from time to time; the values stay the same.
Before you begin
Section titled “Before you begin”- The Airgate side is done: SCEP on, Intune validation on, Test Intune
connection says
Connected(Intune SCEP overview, steps 1 to 3). - You have the SCEP URL, for example
https://nac.contoso.com/scep/contoso. - You have the Airgate root CA as a
.cerfile (Certificates › Certificate authorities › Platform Root CA › Certificate › DER). - You know the RADIUS server name (Certificates › Server certificates ›
Platform EAP certificate › Server names), for example
radius.contoso.com. - Windows devices are enrolled in Intune (Entra joined or hybrid joined) with a primary user.
- An Entra group of users or devices to assign, for example
Wi-Fi Users. - Intune role: Policy and Profile Manager or Intune Administrator.
Step 1: Trusted certificate profile (the Airgate root)
Section titled “Step 1: Trusted certificate profile (the Airgate root)”- In the Microsoft Intune admin center (
https://intune.microsoft.com), open Devices › Manage devices › Configuration and select Create › New Policy. - Set Platform to Windows 10 and later and Profile type to Templates. Under Template name, select Trusted certificate, then Create.
- Basics: Name
Airgate Root CA - Windows. Select Next. - Configuration settings:
- Certificate file: select the Airgate root
.cerfile. - Destination store: Computer certificate store - Root.
- Certificate file: select the Airgate root
- Assignments: under Included groups, add
Wi-Fi Users. - Review + create › Create.
Step 2: SCEP certificate profile
Section titled “Step 2: SCEP certificate profile”-
Devices › Manage devices › Configuration › Create › New Policy. Platform Windows 10 and later, Profile type Templates, template SCEP certificate, Create.
-
Basics: Name
Airgate Wi-Fi certificate - Windows. Next. -
Configuration settings:
Setting Value Certificate type User Subject name format CN={{UserPrincipalName}}Subject alternative name Two entries: Attribute User principal name (UPN), Value{{UserPrincipalName}}; and AttributeURI, ValueIntuneDeviceId://{{DeviceId}}Certificate validity period 1Years (Airgate applies its own Certificate lifetime (days))Key storage provider (KSP) Enroll to Trusted Platform Module (TPM) KSP if present, otherwise Software KSP Key usage Digital signature and Key encipherment Key size (bits) 2048Hash algorithm SHA-2 Root Certificate select Airgate Root CA - Windows(step 1)Extended key usage Name Client Authentication, Object Identifier1.3.6.1.5.5.7.3.2(or pick Client Authentication under Predefined values)Renewal threshold (%) 20SCEP Server URLs https://nac.contoso.com/scep/contoso(your SCEP URL) -
Assignments:
Wi-Fi Users(the same group as step 1). -
Review + create › Create.
Why these values:
CN={{UserPrincipalName}}makes the UPN the user name Airgate sees at sign-in, so the Sign-in log showsalice@contoso.comand Entra ID group rules work.- The UPN SAN makes the user the certificate’s Owner in Airgate.
IntuneDeviceId://{{DeviceId}}lets Airgate find the device in the Intune sync even when it uses a private (random) Wi-Fi address. See Match devices by Intune device ID.- Device certificates (Certificate type
Device, subjectCN={{AAD_Device_ID}}) also work, for shared PCs or Wi-Fi before user sign-in. Use a separate profile and a device group, and rules that do not depend on user groups.
Step 3: Wi-Fi profile
Section titled “Step 3: Wi-Fi profile”-
Devices › Manage devices › Configuration › Create › New Policy. Platform Windows 10 and later, Profile type Templates, template Wi-Fi, Create.
-
Basics: Name
Corp-WiFi - Windows. Next. -
Configuration settings:
Setting Value Wi-Fi type Enterprise Wi-Fi name (SSID) Corp-WiFi(exact, case-sensitive)Connection name Corp-WiFiConnect automatically when in range Yes Connect to this network, even when it is not broadcasting its SSID Yes only for a hidden SSID Wireless security type WPA2-Enterprise (or the WPA3-Enterprise option that matches your SSID) EAP type EAP - TLS Certificate server names radius.contoso.com(the RADIUS server name; add each name if there are several)Root certificates for server validation Airgate Root CA - WindowsAuthentication method SCEP certificate Client certificate for client authentication Airgate Wi-Fi certificate - WindowsIdentity privacy (outer identity) anonymous(optional) -
Assignments:
Wi-Fi Users. -
Review + create › Create.
Step 4: Allow the certificate in Airgate
Section titled “Step 4: Allow the certificate in Airgate”-
In Airgate, open Access › Access policies and open the policy for
Corp-WiFi(or Add a policy › Employees). -
Applies when: Connection
802.1X, Wi-Fi networks (SSID)Corp-WiFi. -
Allowed methods: EAP-TLS.
-
Check accounts in: your Entra ID directory if rules use Entra groups.
-
Add rules, for example:
Order Rule When Then 1 Managed staff laptops Intune managed = Yes, Intune compliance = Compliant, User is in group › Entra › StaffAllow, VLAN 20Default no rule above matches Deny -
Save changes.
For compliance conditions, connect Integrations › Microsoft Intune first (Device compliance policy).
Verify
Section titled “Verify”On the PC
-
Sync: Settings › Accounts › Access work or school, select the work account, Info, then Sync.
-
Run
certlm.msc(the computer’s certificates). Under Trusted Root Certification Authorities › Certificates you find the Airgate root. -
Run
certmgr.msc(the current user’s certificates). Under Personal › Certificates you find a certificate:- Issued To:
alice@contoso.com; - Issued By: your tenant’s Onboard CA;
- Intended Purposes: Client Authentication.
Open it › Details › Subject Alternative Name: it lists
Other Name: Principal Name=alice@contoso.comandURL=IntuneDeviceId://<device id>. - Issued To:
-
Run
netsh wlan show profiles(the profileCorp-WiFiis listed) and connect.
In Intune
- Open each profile › Device status / User status: Succeeded.
- For a single device: Devices › Windows › the device › Device configuration.
In Airgate
- Certificates › Issued certificates: the certificate with Owner
alice@contoso.comand SCEP (Intune) under Issued by. - Monitor › Sign-in log: the sign-in with EAP-TLS, the matched rule and the
VLAN. On the Trace tab, a line
Intune device ID … facts from intuneconfirms the device-ID match.
Troubleshooting
Section titled “Troubleshooting”| Symptom | Cause | Fix |
|---|---|---|
| SCEP profile Error or Pending, no certificate | Intune refused the request, the device cannot reach the SCEP URL, or the root profile is not on the device. | Check Monitor › Logs in Airgate for SCEP request refused by Intune; open …/scep/<slug>?operation=GetCACaps from outside; assign the root profile to the same group. |
| SCEP profile fails with a TPM error | The TPM cannot create the key. | Keep Enroll to Trusted Platform Module (TPM) KSP if present, otherwise Software KSP, or update the TPM firmware. |
| Wi-Fi profile Error | The referenced SCEP or root profile is not assigned to the device. | Assign all three profiles to the same group. |
| Windows asks for a user name and password | The Wi-Fi profile does not use the SCEP certificate, or the certificate is missing. | Check Client certificate for client authentication; sync. |
| Sign-in log: The device didn’t trust Airgate’s RADIUS certificate | Certificate server names does not match the RADIUS certificate, or the root profile is missing. | Fix the server name; check the root in certlm.msc. |
| Sign-in log: The device’s certificate isn’t from a CA Airgate trusts | Windows used another client certificate (old PKI). | Remove the old Wi-Fi profile; check the Wi-Fi profile’s client certificate. |
| Sign-in log: The device’s certificate has expired | No renewal. | Sync the device (Access work or school › Info › Sync); delete the old certificate in certmgr.msc if it stays. |
| Sign-in log: No account named “…” | The CN is not a UPN Entra ID knows. | Use CN={{UserPrincipalName}}. |
Sign-in log: Denied: managed by Intune check failed with not found in Intune |
The device is not in the Intune sync, or the certificate has no device ID and the PC uses a random address. | Add the URI SAN; check Integrations › Microsoft Intune. |