BYOD
BYOD (bring your own device) onboarding lets employees connect their own phones, tablets and laptops to your EAP-TLS network without an MDM and without IT. They open a portal, sign in with their company account, and install a personal Wi-Fi profile with a certificate for that device. This page explains how it works. The pages are under BYOD in the console.
How it works
Section titled “How it works” 1. Device joins an open onboarding SSID ─▶ MAC authentication ─▶ captive role that redirects to the BYOD portal 2. User signs in on the portal: Microsoft (Entra ID) or user name and password 3. Airgate checks allowed groups and the user's device limit 4. User picks the device type ─▶ Airgate issues a certificate from the tenant's Onboard CA and builds the Wi-Fi profile 5. User installs the profile (or the AirEnroll app does it) ─▶ the device moves to the secure SSID and signs in with EAP-TLS 6. Airgate marks the endpoint: BYOD = true, BYOD Owner, BYOD Device ID, BYOD Platform ─▶ the BYOD rule appliesA portal lives at https://<console address>/byod/<tenant>/<portal>. You create it on BYOD › BYOD portals.
Portal settings
Section titled “Portal settings”| Section | Settings |
|---|---|
| General | Name, Slug, Description; the Portal address is shown. |
| Sign-in | Sign-in method: Microsoft sign-in (Entra ID) or Username and password; the Directory that checks it; optional Allowed groups. |
| Devices & Wi-Fi | Wi-Fi network (SSID) of the secure network; RADIUS server name (empty uses the EAP server certificate’s name); Devices per user; Certificate validity (days); Platforms to offer. |
| Branding | Browser title, Heading, Message, Logo, colours and Footer. |
| Terms | Terms of use, and whether Users must accept the terms before signing in. |
Microsoft sign-in needs an Entra ID directory with an app registration and a client secret, and the portal’s redirect URI registered in that app.
Platforms
Section titled “Platforms”| Platform | How the device is set up |
|---|---|
| iPhone, iPad, Mac | A configuration profile with the certificate and the Wi-Fi network, installed from Safari. |
| Android | The AirEnroll app, which fetches the certificate and Wi-Fi settings itself, or manual setup with the certificate file. |
| Windows | The AirEnroll app, or a script package that installs the certificate and Wi-Fi profile. |
| Chromebook | An ONC file to import. |
| Linux | An install script. |
The AirEnroll option appears only when the app files are installed on the Airgate server; otherwise users get the manual steps.
Devices, limits and revocation
Section titled “Devices, limits and revocation”- Each device gets its own certificate. The certificate appears under Certificates › Issued certificates, and the device under BYOD › BYOD devices with its user, platform, MAC address, status and when it last connected.
- Devices per user counts active devices with an unexpired certificate. Revoked and expired devices free their slot.
- Revoke on BYOD › BYOD devices ends the device’s access at once: the certificate is revoked (CRL and OCSP), the device is disconnected with CoA, and its endpoint gets
BYOD = false.
Policies for BYOD devices
Section titled “Policies for BYOD devices”When an onboarded device signs in with its certificate, Airgate marks its endpoint with Endpoint:BYOD = true, BYOD Owner, BYOD Device ID and BYOD Platform. In the access policy of the secure SSID, add a rule with the condition BYOD device Yes (onboarded via BYOD), above any rule that would refuse devices that are not managed by Intune or protected by SentinelOne. Give BYOD devices a restricted role or VLAN.
The very first sign-in may be decided before the endpoint is marked. Airgate then marks it straight away: after a reject, the device’s automatic retry matches the BYOD rule; after an accept, Airgate sends a CoA to re-authenticate it.
The BYOD certificates come from the same Onboard CA as Intune SCEP certificates. Airgate tells them apart by its BYOD device registry and the BYOD endpoint attributes.