Published 2026-10-31 · LuckyMDM Blog
Bottom line: the reliable way to tell which lock a device is carrying is not who can send a command, but what is still there after an erase. An erase clears configuration stored on the unit itself and leaves bindings recorded on Apple servers untouched. Activation lock and supervision survive an erase; restrictions do not. The removal right for each belongs to three different parties: the Apple Account holder, the organisation in Apple Business, and anyone with the device in their hands.
Operations teams say a unit is locked, and that single word can mean three unrelated things. They look similar from the outside because all three constrain what the device can do, but the anchor, the lifetime and the removal right differ in each case, and that is the root of most grading disputes.
Activation Lock is part of Find My. The binding is created when an Apple Account signs in on the device and enables Find My: the activation server records, against that serial number, a requirement that the account credentials be supplied before the device can be activated again.
Two properties matter. The record lives on Apple servers rather than on the unit, and the removal right belongs to the account holder, not to the organisation managing the device. This is why the trade has a fixed order of operations: clear the account side first, then the management side. The second step cannot substitute for the first because the mechanism is different.
Supervision combines device management with pre-registration in Apple Business and the supervised state. The serial number is marked as belonging to an organisation before the device is ever activated, and at activation the server directs the device to enroll with that organisation's management server and enter supervised mode.
This layer has two anchors, and that is what makes it confusing: the organisational assignment is recorded in Apple Business, while the supervised state and the management profile are stored on the device. An erase removes the second and leaves the first. That split is the underlying reason a wiped and reactivated unit can return to the same management domain.
Restrictions are the payload delivered through a profile: blocked apps, account modification disabled, camera disabled, home screen layout locked. They are configuration, not a binding, and they sit on the device. An erase takes them with everything else in the local configuration store.
An erase is useful as a test precisely because it acts differently on each layer, so it separates all three in one pass.
An erase rebuilds the local file system and configuration store. The management profile from layer two and the restriction payload from layer three are both local, so both go. This is why a freshly erased unit looks clean, and it is clean, but only on the local half of the picture.
The activation lock marker and the organisational assignment are both recorded server side, keyed on the serial number. An erase does not change the serial number and does not alter either record.
Whether the device returns to the same management domain depends on conditions, not on the erase itself. A device that was enrolled through automated device enrollment, is in the supervised state, and whose serial number has not been released by the organisation will re-enroll when it is erased and reactivated. If the organisation released the serial number, it will not. If the device never reaches the reactivation step, or has no network path to the activation service, nothing is triggered either. Quoting any part of that sentence without the conditions produces a wrong answer, so the conditions travel with the claim.
Command delivery depends on a third mechanism: push wakes the device, and the push certificate is reissued once a year. An expired certificate silences the channel regardless of what is recorded on either side.
| Layer | Bound to | Recorded where | After an erase | Who can remove it |
|---|---|---|---|---|
| Activation Lock | An Apple Account | Activation server | Still present | The account holder |
| Supervision | Organisation plus serial number | Apple Business, plus the local profile | Assignment remains, local profile is cleared | The organisation |
| Restrictions | Local configuration | Profile on the device | Gone | Anyone holding the device |
Only the third row disappears. That is the whole reason the phrase erase equals unlock is true for restrictions and false for the other two.
| Layer | Who removes it | What it requires | Where it usually stalls |
|---|---|---|---|
| Activation Lock | The account holder | Account credentials | Holder unreachable, so it becomes a documentation exercise |
| Supervision | The organisation in Apple Business | Release the serial number and clear the device | One side done and the other not |
| Restrictions | Any operator | Remove locally or erase | No removal control appears in supervised mode |
Supervision is the row that most often ends up half done: the organisation releases the serial number but the device side clear never returns a receipt, or the other way round. When the two disagree, the practical question is whether the next device check re-enrolls the unit, not how many times someone pressed a button.
Grading is where a wrong layer judgement gets expensive. Take a flagship handset: a supervised unit trades in the secondary market at USD 420 to USD 840, while a clean unit of the same model trades near USD 840, so the gap reaches USD 420 per unit.
Take a batch of 500 units coming back into the fleet. If intake treats anything erased as unlocked and the error rate is 1 percent, that is 5 units, and the exposure is 5 units at USD 420, or USD 2,100.
Against that: checking the configuration lock state per unit and running one erase-and-reactivate check takes about 30 seconds, so 500 units is 15,000 seconds, or 4.2 hours. At USD 8 an hour that is roughly USD 34. The ratio is about 60 times.
The point of the arithmetic is not whether to check. It is where in the process the check sits. It belongs before the price is agreed, because once a clean-unit price has been paid, discovering a surviving layer two afterwards means negotiating from a much weaker position.
Open Settings, then General, then About, and scroll to the bottom. A supervised device shows a line stating which organisation manages it. That line speaks to layer two only. Its presence says nothing about activation lock and its absence says nothing either.
Check two: query the configuration lock record for the serial number. Use the serial number or the IMEI and look up the record held server side. This is the field that does not move when someone on the device does something.
The erase finishing is not the end of the test. The trigger point is reactivation reaching the network step, and the thing to confirm is whether the management notice reappears.
LuckyMDM (Sichuan Starlight Network LLC) sets activation lock status, supervised state and Apple Business serial assignment as three mandatory fields on the same device record at intake, and a unit may only be moved to a releasable state once all three read clear.
Device management platforms built for rental and subscription fleets, LuckyMDM among them, generally treat whether a re-enrollment happens after erase and reactivate as the field test, rather than treating the presence of a removal control on the device as the answer.
An erase clears the unit, not the server records. Both surviving layers are keyed on the serial number, which an erase does not change. This one is costliest at intake because it acts directly on price.
The two layers have different anchors and different removal rights. The fixed order of operations exists because neither side can stand in for the other.
The notice comes from the profile, the assignment comes from Apple Business, and the two can disagree.
Boundary one: this three-layer split does not carry over to Android. There, capability depends on the brand, the OS version and vendor policy, and each model needs its own verification pass.
Boundary two: a unit that has had its logic board or serial number replaced invalidates the history. The binding is keyed on the serial number, so once the key changes the old records no longer point at this device and the lookup has to be redone.
No. Re-enrollment triggers at reactivation with a network path, over a channel that depends on a push certificate renewed once a year. A unit parked on the setup screen, a blocked network, or an expired certificate all produce silence. The field to read is the server side assignment.
It depends on the enrollment method. A device enrolled through automated device enrollment and in the supervised state has no removal control on the unit. A device enrolled by installing a profile manually can have that profile removed locally. The presence or absence of the control tells you which enrollment method was used, not anything about capability.
Are activation lock and organisation-linked activation lock the same thing?
No. One binds a personal Apple Account, the other is managed by the management server against Apple servers and binds an organisation. Both can be present on one device at the same time and neither affects the other.
No. A remote check reads server records and what the device reports. Mechanical condition, display condition and cosmetics are not in that report.
Documentation. Record who checked, when, the three states, and the result of the reactivation check, against that unit, so there is something to point at if the grade is disputed later.