Deploy Wi-Fi certificates to macOS with Intune SCEP
This guide creates the three Intune profiles for macOS. At the end, every Mac in the assigned group has a user certificate from Airgate in its keychain and joins your secure SSID with EAP-TLS, without a 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 (Intune SCEP overview,
steps 1 to 3) and you have the SCEP URL, for example
https://nac.contoso.com/scep/contoso. - The Airgate root CA as a
.cerfile (Certificates › Certificate authorities › Platform Root CA › Certificate › DER). - The RADIUS server name (Certificates › Server certificates › Platform EAP
certificate › Server names), for example
radius.contoso.com. - Macs enrolled in Intune with user affinity (user-approved enrollment, automated device enrollment with a user, or Company Portal enrollment). User certificates need a user.
- An Entra group to assign, for example
Mac Wi-Fi Users.
Step 1: Trusted certificate profile (macOS)
Section titled “Step 1: Trusted certificate profile (macOS)”- In the Microsoft Intune admin center, open Devices › Manage devices › Configuration and select Create › New Policy.
- Platform macOS, Profile type Templates, template Trusted certificate, Create.
- Basics: Name
Airgate Root CA - macOS. Next. - Configuration settings: Deployment channel User channel (the
same as the SCEP profile), Certificate file: the Airgate root
.cer. - Assignments:
Mac Wi-Fi Users. Review + create › Create.
Step 2: SCEP certificate profile (macOS)
Section titled “Step 2: SCEP certificate profile (macOS)”-
Create › New Policy, Platform macOS, Profile type Templates, template SCEP certificate, Create.
-
Basics: Name
Airgate Wi-Fi certificate - macOS. Next. -
Configuration settings:
Setting Value Deployment channel User channel Certificate type User Subject name format CN={{UserPrincipalName}}Subject alternative name Attribute User principal name (UPN), Value{{UserPrincipalName}}; and AttributeURI, ValueIntuneDeviceId://{{DeviceId}}Certificate validity period 1Years (Airgate applies its own lifetime)Key usage Digital signature and Key encipherment Key size (bits) 2048Root Certificate Airgate Root CA - macOSExtended key usage Name Client Authentication, Object Identifier1.3.6.1.5.5.7.3.2Allow all apps access to private key Enable Renewal threshold (%) 20SCEP Server URLs your SCEP URL -
Assignments:
Mac Wi-Fi Users. Review + create › Create.
Allow all apps access to private key lets the macOS Wi-Fi service
(eapolclient) use the key without asking the user for keychain access.
Without it, the Mac may prompt or fail to connect.
Step 3: Wi-Fi profile (macOS)
Section titled “Step 3: Wi-Fi profile (macOS)”-
Create › New Policy, Platform macOS, Profile type Templates, template Wi-Fi, Create.
-
Basics: Name
Corp-WiFi - macOS. Next. -
Configuration settings:
Setting Value Deployment channel User channel (the same as the SCEP profile) Wi-Fi type Enterprise Network name Corp-WiFiSSID Corp-WiFi(exact, case-sensitive)Connect automatically Enable Hidden network only for a hidden SSID Security type WPA2-Enterprise (or the WPA3-Enterprise option that matches your SSID) EAP type EAP-TLS Certificate server names radius.contoso.comRoot certificate for server validation Airgate Root CA - macOSAuthentication method Certificates Certificates (client certificate) Airgate Wi-Fi certificate - macOSIdentity privacy (outer identity) anonymous(optional) -
Assignments:
Mac Wi-Fi Users. Review + create › Create.
Step 4: Allow the certificate in Airgate
Section titled “Step 4: Allow the certificate in Airgate”Use the same access policy as for Windows: Access › Access policies, Allowed methods EAP-TLS, rules by Entra group and Intune compliance, Save changes (see Windows SCEP, step 4).
Private Wi-Fi address
Section titled “Private Wi-Fi address”Since macOS 15, a Mac can use a private (random) Wi-Fi address per network. The address Intune reports for the Mac is then not the one Airgate sees, so rules that check Intune managed or SentinelOne agent would not find the Mac by its MAC address.
The IntuneDeviceId://{{DeviceId}} SAN from step 2 solves this: Airgate finds
the Mac by its Intune device ID, whatever address it uses. See
Match devices by Intune device ID.
Until the Mac has a certificate with the device ID, the user can set
System Settings › Wi-Fi › Details… (next to Corp-WiFi) › Private Wi-Fi
address to Off.
Verify
Section titled “Verify”On the Mac
- Open System Settings › General › Device Management (on macOS 13: System Settings › Privacy & Security › Profiles). The three profiles are listed under the management profile.
- Open Keychain Access. In the login keychain (user channel) under
My Certificates, find
alice@contoso.com, issued by your tenant’s Onboard CA, with its private key. Open it: Subject Alternative Name lists the UPN andIntuneDeviceId://…. - In the menu bar Wi-Fi menu,
Corp-WiFiconnects without a prompt.
To force a check-in, open Company Portal and select Check settings, or in Intune select Sync on the device.
In Intune: each profile › Device status / User status: Succeeded.
In Airgate: Certificates › Issued certificates lists the certificate
with SCEP (Intune); Monitor › Sign-in log shows the EAP-TLS sign-in and
the rule. The Trace tab shows Intune device ID … facts from intune.
Troubleshooting
Section titled “Troubleshooting”| Symptom | Cause | Fix |
|---|---|---|
| Wi-Fi profile fails to install: certificate not found | The SCEP and Wi-Fi profiles use different deployment channels, or the SCEP profile is not installed yet. | Use User channel in all three profiles; sync again. |
The Mac asks to allow eapolclient to use a key |
Allow all apps access to private key is off. | Enable it and let the profile re-deploy. |
| SCEP profile Error | Intune refused the request or the Mac cannot reach the SCEP URL. | Check Monitor › Logs for SCEP request refused by Intune; test …?operation=GetCACaps from outside. |
| Sign-in log: The device didn’t trust Airgate’s RADIUS certificate | Server name or root mismatch. | Fix Certificate server names; check the root profile. |
Sign-in log: Denied: managed by Intune check failed with not found in Intune: the device uses a private Wi-Fi address and its certificate has no Intune device ID |
The certificate was issued before the URI SAN was added. | Let Intune renew the certificate (or revoke the old one in Airgate and sync); meanwhile turn Private Wi-Fi address off. |
| Sign-in log: No account named “…” | The CN is not a UPN. | Use CN={{UserPrincipalName}}. |
Related
Section titled “Related”- Intune SCEP overview
- Windows SCEP
- Match devices by Intune device ID
- BYOD for Apple devices (Macs without Intune)