2.2.4. Knox Mobile Enrollment and Google Zero-Touch
💡 First Principle: Zero-touch provisioning moves the enrollment decision from the person unboxing the device to the supply chain. The reseller records the device against your account at purchase, so on first boot the device already knows it belongs to your organization and which enrollment token to use. The user never types a token or scans a QR code.
Both programs end the same way: the device boots, finds its configuration, and enrolls into one of the Android Enterprise corporate modes from 2.2.3 using an Intune enrollment token. Intune can export a token as JSON for zero-touch or Knox — the fully managed token, for example, offers Replace, Revoke and Export actions, none of which affects devices already enrolled. Both programs also mark the device as corporate automatically.
Google zero-touch enrollment works with devices bought from an authorized zero-touch reseller, who registers them against the Google account you gave them. Intune embeds the zero-touch portal in an iframe at Devices > By platform > Android > Device onboarding > Enrollment > Bulk enrollment methods > Zero-touch enrollment. To use it you need the Android Enterprise Update app sync permission and fully managed enrollment set up; a custom role needs the Manage zero touch enrollment permission to manage the connection.
The detail the exam is most likely to probe is what linking does. Linking your zero-touch account in Intune creates a default configuration whose token is for fully managed devices, and that configuration overrides the zero-touch portal's own default. So:
- For fully managed devices, link the account in Intune and you're largely done.
- For COPE or dedicated devices, don't link the account. Configure in the zero-touch portal instead: select Microsoft Intune as the EMM device policy controller, and paste the DPC extras JSON with
com.google.android.apps.work.clouddpc.EXTRA_ENROLLMENT_TOKENset to the token for the profile you want.
Samsung Knox Mobile Enrollment (KME) is Samsung's equivalent for Samsung devices and supports Android Enterprise dedicated, fully managed and COPE enrollment. You need a Samsung Knox account, which Samsung approves in one to two business days. In the Knox Admin Portal you create a profile with Microsoft Intune as the EMM, set the company name, and leave all system apps enabled. The Custom JSON data field looks optional in Knox but is required by Intune, carrying the same enrollment token key:
{"com.google.android.apps.work.clouddpc.EXTRA_ENROLLMENT_TOKEN": "<token>"}
Devices reach the Knox Admin Portal either from a Samsung-approved reseller or through the Knox Deployment App, which enrolls devices over Bluetooth or NFC without a reseller — useful for devices you already own.
| Google zero-touch | Samsung Knox Mobile Enrollment | |
|---|---|---|
| Devices | Devices bought from an authorized zero-touch reseller | Samsung devices |
| How devices get registered | Reseller assigns them to your Google account | Samsung-approved reseller, or Knox Deployment App (Bluetooth/NFC) |
| Where you configure | Intune iframe (fully managed) or the zero-touch portal (COPE, dedicated) | Knox Admin Portal profile with Intune as the EMM |
| Token delivery | DPC extras JSON with the enrollment token | Custom JSON data with the enrollment token (required) |
| Supported Intune modes | Fully managed by default when linked; COPE and dedicated via the portal | Dedicated, fully managed, COPE |
Which should you choose? Zero-touch is Google's program and depends on buying through an authorized zero-touch reseller. KME is Samsung's program for Samsung hardware, and its Knox Deployment App can bring in Samsung devices you already own without a reseller. Either way, enrollment time grouping (2.1.3) is supported for fully managed, COPE and dedicated enrollments, so a scanner can receive its line-of-business app on its first check-in.
⚠️ Exam Trap: Linking a zero-touch account in Intune isn't a neutral "connect" step. It creates a fully managed default configuration that overrides the portal's default. If a scenario's zero-touch devices must enroll as dedicated kiosks or COPE phones, the right answer configures the zero-touch portal with that profile's token and does not link the account in Intune.
Reflection Question: Your Samsung tablets enroll through KME but arrive at a normal Google sign-in screen instead of enrolling into Intune. The Knox profile names Microsoft Intune as the EMM. What did the Knox admin most likely leave blank, and why does Knox let them?