Kandji vs Jamf Pro for Mac Activation Lock: Where Each Keeps the Bypass Code
How Kandji (Iru) and Jamf Pro prevent, allow and clear Mac Activation Lock, where each keeps the bypass code, who can read it and when Apple Business is needed.

On a Mac, Jamf Pro and Kandji (now Iru Endpoint) handle Activation Lock in much the same way. Apple disallows it by default on supervised devices; Iru keeps it disallowed for Macs that enrol through Automated Device Enrollment, and Jamf Pro has a PreStage setting that prevents it. Both can allow the user-based kind tied to a personal Apple Account, and both keep the bypass code that clears it. Neither turns on organisation-based Activation Lock for a Mac: Jamf documents that for mobile devices only, and Iru for iOS, iPadOS and visionOS only. The differences are in the operational detail. Jamf Pro has a Set Activation Lock remote command, which can also go out as a mass action, and it shows codes on the computer’s Management tab behind its own privileges. Iru sets the behaviour in its Automated Device Enrollment configuration before the Mac enrols and shows the code from the device record’s action menu to roles that can read Activation Lock secrets. One limit applies to both: a lock the user turned on before enrolment can’t be cleared with a code the MDM collected later, so Apple Business is where you check, and sometimes where you clear it.
#The usual workaround when a returned Mac asks for an Apple Account
A leaver hands back a MacBook. The service desk erases it, and on restart the Mac shows the Activation Lock screen asking for the Apple Account that used to be signed in to Find My. The person has gone, nobody knows the password, and the laptop sits in a drawer while someone searches the MDM for a code or emails the former employee.
When Kandji and Jamf Pro are compared, Activation Lock usually gets one line: both support bypass codes. That’s true, but it doesn’t help the technician with the locked Mac. What decides the outcome is whether the lock was allowed in the first place, whether a code was collected before it was needed, who is allowed to read that code, and whether the Mac is in Apple Business so it can be cleared there.
Apple sets the rules both products follow. There are two kinds of lock. Organisation-linked Activation Lock needs Apple School Manager or Apple Business and is controlled by the device management service on Apple’s servers. User-linked Activation Lock needs an unmanaged, personal Apple Account with Find My turned on. Activation Lock is disallowed by default on supervised devices, and to allow the user-linked kind safely the service has to fetch and store a bypass code that the device creates. A Mac needs Apple silicon or the Apple T2 Security Chip to use Activation Lock at all.
#What to do instead: decide the policy before the Mac enrols
Treat Activation Lock as a setting you choose before enrolment, then check that the code and the access rules are in place before the first device comes back. The table compares the two products at each point, as each vendor documents it.
| Point in the life cycle | Jamf Pro | Kandji (Iru Endpoint) |
|---|---|---|
| Default at enrolment | The computer PreStage General payload has “Prevent users from enabling activation lock”, which Jamf lists as a commonly recommended setting. | Macs enrolling through Automated Device Enrollment get the Activation Lock Allowed While Supervised option set to false. |
| Allowing user-based Activation Lock | Set Activation Lock remote command, “Allow user to enable Activation Lock on the device”. Can be sent as a mass action. Needs a supervised Mac with Apple silicon or a T2 chip. | Change the Automated Device Enrollment configuration before the Mac enrols. |
| Organisation-based Activation Lock on a Mac | Not available: Jamf documents it for mobile devices only. | Not available: Iru supports device-based Activation Lock on iOS, iPadOS and visionOS only. |
| Where the bypass code is shown | Computer record, Management tab, Activation Lock bypass category. Separate fields for a lock enabled on the device and a lock enabled by the user. | Device record, Device Action Menu (ellipsis, upper right). Copy the user-based code. |
| Who can read it | Privileges under Settings > System > User accounts & groups > Jamf Pro Server Actions. | A role that can read Activation Lock secrets, for example Secrets Auditor. |
| Status shown | Inventory tab, Security category. Jamf says Apple Business or Apple School Manager is the source of truth. | Activation Lock status fields on the device record Details tab. |
| Lock turned on before enrolment | Can’t be cleared with stored codes; the user signs out of Find My. | Stays on; a later code can’t clear it until the user turns Find My off and on again. |
Jamf collects the code after Activation Lock is enabled and inventory updates, deletes it from the Mac and keeps it in the management record, replacing it with a new one each time the Mac is wiped and re-enrolled. Iru says codes can be retrieved only within 30 days after the device is supervised, which matters most when Macs arrive from another MDM.
The flowchart shows what the service desk does when a returned Mac stops at the Activation Lock screen, whichever product manages it.
Rendering diagram...
#Step by step on one pilot Mac per product
Run this on one supervised pilot Mac with Apple silicon or a T2 chip in each product, both registered in Apple Business. The aim is to prove three things before relying on either console: the setting you chose is in force, the code is there when it should be, and only the right people can see it.
- Record the starting state. In Apple Business, go to Devices > Inventory, select the pilot Mac and note the Activation Lock state under Details. In Jamf Pro, note the computer’s Inventory > Security status and whatever the Management > Activation Lock bypass category shows. In Iru, note the Activation Lock fields on the Details tab. Stop if Apple Business shows Activation Lock already on for a Mac where your MDM says it’s prevented: that’s a lock from before enrolment, and neither product can clear it with a stored code.
- Confirm the Mac came through Automated Device Enrollment. Run
sudo profiles show -type enrollmentin Terminal. It shows the Automated Device Enrollment configuration the Mac is assigned to. If nothing comes back, the PreStage or Iru enrolment setting never applied to this Mac. Check its assignment in Apple Business before going further. - Restrict who can read codes, before anything else changes. In Jamf Pro, set the privileges under Settings > System > User accounts & groups > Jamf Pro Server Actions so only the approved administrators can view the code. In Iru, give Activation Lock secret access only to the roles that need it, such as Secrets Auditor. Write down the old settings so you can put them back.
- Choose the policy. For most organisation-owned Macs, keep the default: prevented in the PreStage in Jamf Pro and false in Iru’s enrolment configuration. Only allow user-based Activation Lock if you have a reason, such as staff who carry Macs in places where theft is likely.
- If you allow it in Jamf Pro (state change). Precondition: the pilot Mac is supervised, has Apple silicon or a T2 chip, and step 3 is done. Open the computer, go to the Management tab, choose Set Activation Lock, select “Allow user to enable Activation Lock on the device” and send it. The user then signs in to iCloud with a personal Apple Account, not a Managed Apple Account, and turns on Find My. After the next inventory update the status shows Enabled. Expected evidence: a code under “Bypass Code to Use When Activation Lock is Enabled by the User”. Stop condition: if the status shows Enabled but no code appears, send Set Activation Lock with “Disable and prevent Activation Lock”, confirm the state in Apple Business, and if it is still on, turn it off there before going further. Rollback: the same “Disable and prevent” command. Jamf notes that any Set Activation Lock command also attempts to clear an existing lock with Apple’s servers.
- If you allow it in Iru (state change). Precondition: the pilot Mac has not enrolled yet. Iru documents this as a change to its Automated Device Enrollment configuration before enrolment, not a per-device switch, so expect it to apply to other Macs that enrol with that configuration afterwards as well as the pilot. Change it, enrol the pilot, have the user turn on Find My, then open the Device Action Menu and check that a user-based bypass code is there. Rollback: set the configuration back to not allowed before any other Mac enrols, and record which Macs enrolled while it was allowed.
- Test the code in a controlled reassignment. Only on the pilot Mac, after you’ve confirmed a code is stored for it, and with the user’s data backed up and their agreement, erase it as you would for a leaver. At the Activation Lock screen, click Recovery Assistant in the menu bar, choose “Activate with MDM key” and enter the code. Erasing is destructive and can’t be undone, so don’t use a production user’s Mac for this test.
A small number of steps change state here: the Set Activation Lock command, the Iru enrolment configuration and the test erase. Everything else is a lookup.

#Who can change the setting and read bypass codes
A bypass code unlocks a Mac someone else locked. Treat it like a FileVault recovery key: only a small named group should be able to read it. Apple tells you to secure the bypass codes and back them up on a regular basis. In Jamf Pro that means the Jamf Pro Server Actions privileges. In Iru it means keeping the Activation Lock secrets permission to roles such as Secrets Auditor and away from general help desk roles.
Changing the policy is a separate right from reading a code. In Jamf Pro the setting is the Set Activation Lock remote command, and because it can be sent as a mass action, one mistake can allow user-based Activation Lock on many Macs at once. Limit who can send it, and send it to the pilot Mac only. In Iru the setting lives in the Automated Device Enrollment configuration, so the people who can edit that configuration decide it for every future enrolment. In Apple Business, turning off Activation Lock needs a role with permission to remove it, and Apple’s dialog warns that it can’t be undone.
#Check it worked before the first leaver returns a Mac
- Apple Business shows the pilot Mac’s Activation Lock state under Details, and it matches what you expect from the policy.
- Where user-based Activation Lock is allowed and turned on, Jamf Pro shows a code in the user field of the Activation Lock bypass category, and Iru shows a user-based code in the Device Action Menu.
- An account without the code privilege or role can’t see the code in either console. Sign in as a test help desk account to check.
- The pilot Mac activated with “Activate with MDM key” after the test erase.
Don’t trust a single status field. Jamf says the status a Mac reports can be wrong, for example when the user turned on Activation Lock before enrolment, and recommends Apple Business or Apple School Manager as the source of truth for user-based status.
#Where it goes wrong with Activation Lock on Macs
The most common case is a lock that predates enrolment. A user who set up a Mac with their own Apple Account and Find My before it reached the MDM has a lock that no stored code clears. Apple says a Mac supervised through Device Enrollment on macOS 11 or later can’t have Activation Lock managed until it enrols, and if the lock was already on, the service can’t turn it off. Jamf says the user has to sign out of Find My. Iru says the user has to turn Find My off and on again before its code works. Ask the user to do it while they still work for you.
Codes from the old MDM are left behind in a migration. Apple says to get a copy of the bypass codes, or have the old service clear Activation Lock for every enrolled device, when you change device management service. Iru adds that a code can be retrieved only within 30 days after the device is supervised. If you’re moving between the two products, as in the Kandji to Iru deadline decision, export the codes before you move any Macs.
Some teams expect organisation-based Activation Lock on Macs and don’t get it. Neither product enables it on a Mac today, so a Mac’s protection against theft depends on the user-based kind, and on Find My being turned on.
The wrong code goes into the wrong field. Jamf stores two codes: one for a lock enabled on the device and one for a lock enabled by the user. On a Mac the lock is user-based, so use the code in the user field.
A Mac that was never added to Apple Business, or was released from it, can’t be cleared there. Apple says the device has to be in Apple Business and not released before Activation Lock is enabled.

#How to roll back the pilot
- Jamf Pro: send Set Activation Lock with “Disable and prevent Activation Lock” to the pilot Mac, then compare the Inventory > Security status with Apple Business after the next inventory update.
- Iru: return the Automated Device Enrollment configuration to not allowed. The Iru page fetched for this article doesn’t say what happens to Macs that already enrolled while it was allowed, so check each of them in Apple Business.
- Put back the code-viewing privileges and roles you recorded in step 3, unless the tighter settings are what you want to keep.
- If a pilot Mac is locked with no usable code, turn off Activation Lock in Apple Business: Devices > Inventory, select the Mac, More, Turn Off Activation Lock, tick “I understand that this cannot be undone”, then Confirm, and wait for the activity to complete. If the Mac isn’t in Apple Business, Iru points to AppleCare Enterprise Support and Apple to its article on removing Activation Lock.
#What to track each month
Count the Macs returned in the month, and how many stopped at the Activation Lock screen. For each one, note whether a stored code cleared it, whether it was cleared in Apple Business, or whether it had to go to the former user or Apple. The target is that every lock is cleared by a stored code or Apple Business, with none sent to a former employee. Also compare Macs that Apple Business shows as locked with what your MDM reports. One cause Jamf names for a mismatch is a lock the user turned on before enrolment, and that is easier to fix while the user can still sign out of Find My. Review who can read codes in each console once a quarter.
If you’re scoring the two products side by side, add these results to the pilot sheet from piloting both MDMs on real Macs.
#Before you go live with either MDM
- Every Mac is in Apple Business, and none has been released.
- PreStage (Jamf Pro) or the enrolment configuration (Iru) is set to the Activation Lock policy you chose.
- Code access is limited to named administrators or roles, and the last review is recorded.
- You’ve confirmed a code is stored for every Mac where user-based Activation Lock is allowed and turned on.
- Leavers turn off Find My before their last day, and that step is in the offboarding checklist.
- Before any MDM migration, codes are exported, or the old service has cleared Activation Lock.
- The service desk knows the Recovery Assistant “Activate with MDM key” route and the Apple Business fallback.
About this page
Credited to
Dates
Published
Sources
Corrections
No corrections are listed for this page. Some review sweeps corrected pages without naming each one; those are in the corrections log.
Related articles
Device Management
Choosing Miradore, Jamf Pro or Kandji for Mixed Fleets
Compare Miradore, Jamf Pro and Kandji for Mac, Windows, iPhone and Android fleets, then choose with a scoped pilot and a clear pass/fail checklist.
ReadEnterprise IT Management
Part 3: Create a Windows Autopilot Deployment Profile and Dynamic Device Group in Intune
Build a dynamic device group on the AP-Pilot group tag, assign a user-driven Microsoft Entra join profile with a standard user account and a name template, and wait for Assigned before deploying.
ReadEnterprise IT Management
Part 2: Register Devices in Windows Autopilot: Import Hardware Hashes into Intune
Capture a pilot laptop's hardware hash with Get-WindowsAutopilotInfo, tag it AP-Pilot, import the CSV into Intune, and leave the Entra device object that registration creates alone.
ReadDiscover more
Ops Playbook
- PlaybookKandji vs Jamf Pro for FileVault: How Each Escrows, Shows and Rotates Mac Recovery Keys
- PlaybookKandji vs Jamf Pro for Automated Device Enrollment: PreStages and ADE Library Items Compared
- PlaybookKandji Managed OS vs Jamf Pro Blueprints: Comparing macOS Update Enforcement
- PlaybookKandji Auto Apps vs Jamf Pro App Installers for Third-Party Mac App Patching
Lexicon Definitions
Was this useful?
Reports go to the site owner and are used to correct pages. Corrections are listed at /corrections.
Operate smarter, with fewer recurring tickets.
Receive new operational playbooks, incident-prevention guidance, automation scripts and recovery runbooks.
Comments
Add a thoughtful note on Kandji vs Jamf Pro for Mac Activation Lock: Where Each Keeps the Bypass Code. Comments are checked for spam and held for moderation before appearing.