Set up BYOD self-service onboarding
BYOD (bring your own device) onboarding lets employees put their personal devices on the secure Wi-Fi network by themselves. They join an open onboarding SSID, sign in on the Airgate BYOD portal with their company account, and install a personal Wi-Fi profile. Each device gets its own certificate, which the user or IT can revoke at any time.
This guide sets up everything end to end: the directory, the portal, the onboarding SSID and the access rule for onboarded devices.
How it works
Section titled “How it works” 1. Device joins Corp-Onboard (open SSID, MAC authentication) └─ Airgate answers with a captive role → the controller redirects to the BYOD portal 2. User signs in on https://nac.contoso.com/byod/<tenant>/<portal> (Microsoft sign-in with Entra ID, or user name and password) 3. User picks the device type → Airgate issues a certificate from the Onboard CA and delivers a profile, a file or the AirEnroll app 4. Device joins Corp-WiFi with EAP-TLS └─ Airgate marks the endpoint BYOD = true → the rule "BYOD device = Yes" appliesWhat users install per platform:
| Platform | What they get |
|---|---|
| iPhone, iPad, Mac | A configuration profile (.mobileconfig) with the certificate and the Wi-Fi settings. See BYOD for Apple devices. |
| Android | The AirEnroll app (recommended) or a certificate file plus guided steps. See AirEnroll for Android. |
| Windows | The AirEnroll app (recommended) or a zip with a PowerShell installer. See AirEnroll for Windows. |
| Chromebook | An ONC file to import at chrome://network. |
| Linux | A NetworkManager script (sh install.sh). |
| Other | A certificate file and manual steps. |
Before you begin
Section titled “Before you begin”- Certificates: the tenant’s Onboard CA issues the BYOD certificates
(the same CA as Intune SCEP). Decide the RADIUS server name
(Certificates › Server certificates › Platform EAP certificate › Server
names), for example
radius.contoso.com; devices pin it. PUBLIC_URLis the HTTPS address users reach Airgate on, for examplehttps://nac.contoso.com. Portal links and the Microsoft redirect URI are built from it. Use a publicly trusted console certificate so phones open the portal without warnings (Certificates and trust).- A directory for sign-in: a Microsoft Entra ID directory with a client secret (for Microsoft sign-in), or Active Directory, LDAP, Entra ID or local users (for user name and password).
- Two SSIDs on your controller: the secure
Corp-WiFi(WPA2/WPA3-Enterprise, RADIUS to Airgate) and an open onboarding SSIDCorp-Onboardwith MAC authentication to Airgate and a captive portal. - An Airgate role with BYOD write access (Tenant Administrator or Network Administrator).
Step 1: Prepare Microsoft sign-in (Entra ID)
Section titled “Step 1: Prepare Microsoft sign-in (Entra ID)”Skip this step if users sign in with a user name and password.
- In the Microsoft Entra admin center, open Entra ID › App registrations and open the app used by your Entra ID directory in Airgate (Entra ID), or create one and add it as a directory.
- The app needs a client secret (Certificates & secrets). A certificate credential does not work for the portal.
- You add the redirect URI in step 2, once the portal has a slug.
- If you restrict the portal to groups (step 2), Airgate reads the user’s
groups through the directory (
GroupMember.Read.All, as for the directory itself). Alternatively enable thegroupsclaim under Token configuration and use group object IDs as allowed groups.
Step 2: Create the BYOD portal
Section titled “Step 2: Create the BYOD portal”- Open BYOD › BYOD portals and select New portal.
- General:
- Name:
Contoso BYOD. Slug:byod(part of the address). - Enabled: users can onboard devices stays on.
- Portal address: shows
https://nac.contoso.com/byod/<tenant>/byod. Copy it.
- Name:
- Sign-in:
- Sign-in method: Microsoft sign-in (Entra ID) or Username and password.
- Directory: the Entra ID directory (for Microsoft sign-in) or the directory to check passwords against.
- With Microsoft sign-in, the banner Add this redirect URI to the app
registration shows
https://nac.contoso.com/byod/<tenant>/byod/callback. In Entra, open the app › Authentication › Add a platform › Web, paste it and select Configure. Scopes used:openid,profile,email. - Allowed groups: empty lets every user of the directory onboard devices. Otherwise type group names (or Entra group object IDs) and press Enter.
- Devices & Wi-Fi:
- Wi-Fi network (SSID):
Corp-WiFi(the secure network). - RADIUS server name: empty uses the EAP server certificate name (shown in the hint).
- Devices per user: default
3. Active devices with an unexpired certificate count; revoked and expired devices free their slot. - Certificate validity (days): default
365(1 to 1825). - Platforms: tick the device types to offer.
- Wi-Fi network (SSID):
- Branding and Terms: optional, see BYOD portal branding. Users must accept the terms before signing in makes the Terms of use mandatory.
- Select Save. Use the eye icon (Preview) in the list to check the landing page.
Step 3: Set up the onboarding SSID
Section titled “Step 3: Set up the onboarding SSID”The onboarding SSID is open; devices on it reach only the portal and the identity provider.
Access policy in Airgate
- Open Access › Access policies and select Add a policy › Blank.
- Name
BYOD onboarding. Applies when: Connection MAC authentication, Wi-Fi networks (SSID)Corp-Onboard. - Sign-in › Which devices: Any device.
- Add a rule
Send to portalwithout conditions: Allow, RoleOnboard-Portal(an Aruba user role) or, for other vendors, Send › An enforcement profile with a redirect profile (for example a Cisco RADIUS Enforcement profile with the redirect URL and ACL under Access › Enforcement profiles). Select Done. - Move the policy above any catch-all policy and select Save changes.
On the controller
- Create the captive-portal role
Onboard-Portalthat redirects HTTP to the portal address from step 2. If the controller can, append the client MAC to the URL (mac=orclient_mac=). Airgate uses it only if RADIUS saw that MAC in the last 30 minutes. - Allow before login (walled garden): DNS, DHCP, the Airgate host, and for
Microsoft sign-in
login.microsoftonline.com,login.microsoft.com,login.live.com,aadcdn.msftauth.net,aadcdn.msauth.net,logincdn.msftauth.net,*.msauth.net,*.msftauth.net, plus your ADFS or MFA hosts if you use them. - Allow the operating systems’ captive-network checks (for example
captive.apple.com,connectivitycheck.gstatic.com) so phones open the portal by themselves. - On iPhone and iPad, profiles install only from Safari. If the portal opens in the captive sign-in window, users open it in Safari; the install page tells them so.
You can also hand out the portal address directly (email, QR code); users then open it on any network.
Step 4: Add the rule for onboarded devices
Section titled “Step 4: Add the rule for onboarded devices”When an onboarded device signs in on Corp-WiFi with its BYOD certificate,
Airgate marks its endpoint with Endpoint:BYOD = true, BYOD Owner, BYOD Device ID and BYOD Platform.
- Open Access › Access policies and open the policy for
Corp-WiFi(with EAP-TLS in Allowed methods). - Add a rule
BYOD: When › Add condition › BYOD device = Yes (onboarded via BYOD); Then › Allow, with a restricted VLAN or Role (for exampleBYOD). Select Done. - Move it above rules that would deny devices without Intune or SentinelOne (for example the rules from Device compliance policy).
- Select Save changes.
The first sign-in of a new device may be rejected, or get another rule’s access, before the endpoint is marked. Airgate marks it right away: after a reject, the device’s automatic retry matches the BYOD rule; after an accept, Airgate sends a CoA re-authentication so the session gets the BYOD rule.
Step 5: Make the AirEnroll apps available (Android, Windows)
Section titled “Step 5: Make the AirEnroll apps available (Android, Windows)”The Airgate server image ships the AirEnroll apps in
/usr/share/airgate/byod-apps (BYOD_APPS_DIR): airenroll.apk (Android),
AirEnroll.exe (Windows x64) and optionally AirEnroll-arm64.exe. When a file
is missing, the portal offers only manual setup for that platform. To use other
builds, mount a directory and set BYOD_APPS_DIR.
What users see
Section titled “What users see”- Join
Corp-Onboard; the portal opens (or open the link). - Sign in: Sign in with Microsoft, or Username and Password and Sign in.
- Choose your device: Airgate detects the device type and preselects its tile; the user can enter a Device name and selects Continue. The usage bar shows “You are using 1 of 3 devices.”
- On Android and Windows (with the app available): How do you want to set up? › Use the AirEnroll app (Recommended) or Set up manually.
- Install as shown for the platform.
- The Done page says You’re all set once Airgate sees the device on
Corp-WiFi, or Waiting for your device to join Corp-WiFi until then.
Users manage their devices on the portal’s My devices page (Manage BYOD devices).
Verify
Section titled “Verify”- BYOD › BYOD devices lists the device with Status active and Last connected.
- Certificates › Issued certificates lists its certificate (issued via
byod). - Monitor › Sign-in log: the EAP-TLS sign-in on
Corp-WiFimatched theBYODrule. The Computed attributes tab showsEndpoint:BYOD = true.
Troubleshooting
Section titled “Troubleshooting”| Symptom (portal message or log) | Cause | Fix |
|---|---|---|
Microsoft sign-in is not set up correctly for this portal. Please contact IT. |
The portal’s directory is not an Entra ID directory with tenant ID, client ID and client secret. | Fix the directory or pick another one. |
Microsoft shows AADSTS50011 (redirect URI mismatch) |
The redirect URI is not on the app registration. | Add the exact URI from the portal editor (step 2). |
Microsoft sign-in was cancelled or your account is not allowed to use this app. |
The user cancelled, or the enterprise app requires assignment. | Assign the users, or let them retry. |
We could not check your group membership right now. |
Airgate could not read the user’s groups. | Grant GroupMember.Read.All (with consent) or use the groups claim with object IDs. |
Your account is not allowed to set up devices here. Ask IT to add you to one of the allowed groups. |
The user is not in Allowed groups. | Add the user to a group, or change the list. |
You already have 3 devices, the most allowed. Remove one in My devices first. |
Devices per user reached. | The user removes a device on My devices, or raise the limit. |
This download link was already used or has expired. |
Each download link works once and for 10 minutes. | Sign in again and pick the device again. |
Device does not join Corp-WiFi; Sign-in log: The device didn’t trust Airgate’s RADIUS certificate |
The server name in the profile does not match the RADIUS certificate. | Check RADIUS server name and the EAP server certificate. |
| Sign-in log: Denied: no rule of the policy allowed this device for a BYOD device | The BYOD rule is below a deny rule, or missing. | Step 4. |
| No Use the AirEnroll app option | The app file is not in BYOD_APPS_DIR. |
Step 5; manual setup still works. |