macOS LAPS account created but LAPS tab stays empty in HexnodeSolved

Hi @roger,

For Basic LAPS on macOS, tenant-side enablement is not required. If the LAPS account was created but does not appear in the LAPS tab, the account may not have registered correctly with the LAPS management layer.

A clean policy removal and re-association usually resolves this when the LAPS-created account is not showing password or rotation details:

1. Remove the macOS LAPS policy from the affected device.
2. Confirm in Action History that both Remove Device Policy and LAPS actions complete successfully.
3. Go to the device’s Local Accounts tab and verify that the LAPS-created admin account is removed.
4. Re-associate the LAPS policy with the device.
5. Confirm that Associate Device Policy and LAPS actions complete successfully.
6. Run Sync Local Accounts after the LAPS action succeeds.
7. Recheck Device Details > Local Accounts > LAPS.

The LAPS tab populates only after the local account sync succeeds, so it may remain empty immediately after the LAPS action completes.

Regards,
Sienna Carter
Hexnode UEM

One related question: does Basic LAPS adopt admin accounts that already exist on macOS devices, or does it only manage accounts it creates itself?

Basic LAPS is intended to create and manage the local admin account through the LAPS policy. To bring pre-existing local admin accounts under centralized LAPS management, Advanced LAPS for macOS is required. Advanced LAPS is available as an add-on and includes support for managing existing admin accounts.