2.3.5. Windows LAPS and Local Group Membership
💡 First Principle: A local administrator password that is the same on every device is a master key: steal it once and you own the fleet. Windows LAPS gives each device its own random local admin password, backs it up to a directory, and rotates it on a schedule and after it's used — so a leaked password is worth one device for a short time. Local group membership policies do the complementary job of controlling who is an administrator in the first place.
Windows LAPS is built into Windows — it shipped in the April 2023 updates and is native in Windows 11 23H2 and later — and Windows LAPS with Microsoft Entra ID and Intune has been generally available since October 2023. The older legacy Microsoft LAPS is deprecated on Windows 11 23H2 and later, where its MSI installer is blocked. Windows LAPS itself needs only Intune Plan 1 and Entra ID Free.
Where the password is backed up depends on the join type:
- Entra joined devices back up only to Microsoft Entra ID. Turn on Enable Microsoft Entra Local Administrator Password Solution (LAPS) in Entra device settings first (a Cloud Device Administrator task).
- Hybrid joined devices can back up to Entra ID or on-premises AD, never both.
- Entra registered devices aren't supported.
You configure LAPS at Endpoint security > Account protection > Create policy > Windows > Local admin password solution (Windows LAPS). The Backup Directory choice drives which other settings appear, and it must match the join type — backing up to AD from a device that isn't domain joined fails silently. Assign one LAPS policy per device through device groups; user-group assignment can change the configuration every time a different user signs in, and two policies naming different accounts conflict.
| Setting | Default | Range and notes |
|---|---|---|
| Backup Directory | Disabled | Entra ID only, or AD only. While Disabled, every other setting is ignored |
| Password Age Days | 30 | Up to 365. Minimum 1, or 7 when backing up to Entra ID |
| Password Length | 14 | 8–64 characters |
| Password Complexity | Large + small letters, numbers and special characters | Passphrase options need Windows 11 24H2 |
| Post-authentication actions | Reset the password and sign out | Other choices: reset only, reset and reboot |
| Post-authentication reset delay | 24 hours | 0–24; 0 turns post-authentication actions off |
LAPS manages one account per device. By default that's the built-in Administrator, and LAPS manages an account that already exists rather than creating one — except with automatic account management, which needs Windows 11 24H2 (or Windows Server 2025). That feature can create and manage a custom account (named with the WLapsAdmin prefix by default, and disabled unless you enable it) or take over the built-in Administrator. On Windows 11 23H2 and earlier, naming an account that doesn't exist simply does nothing, with no error.
Operating LAPS. An authorized admin views the password at Devices > All devices > device > Monitor > Local admin password, which shows the account, password and last and next rotation — but only when it's backed up to Entra ID. Reading the password requires the Entra permission deviceLocalCredentials/password/read, held for example by Cloud Device Administrator, and every view is audited. The Rotate local admin password device action works one device at a time, needs Entra joined devices to be online, and resets the age clock: with Password Age Days at 30, a manual rotation on November 3 moves the next scheduled rotation to December 3. Changing Password Age Days in the policy, by contrast, doesn't trigger a rotation. LAPS doesn't rotate passwords for devices that are disabled in Entra ID, and deleting a device from Entra ID loses its stored password for good. When several LAPS sources exist, the Intune (CSP) policy takes precedence over Group Policy, local configuration and legacy LAPS, and settings are never merged across them.
Local group membership. The Account protection Local user group membership profile (Windows 10 20H2 or later) manages the six built-in groups evaluated at sign-in: Administrators, Users, Guests, Power Users, Remote Desktop Users and Remote Management Users. Each rule uses one of three actions:
- Add (Update) adds the listed members and leaves everyone else alone.
- Remove (Update) removes the listed members and leaves everyone else alone.
- Add (Replace) makes the group contain exactly the listed members, like Restricted Groups, removing anyone else.
If the same group receives both Replace and Update, Replace wins and no conflict is reported. Members are picked as Entra users and groups (supported on Entra joined devices only) or entered manually as a SID (preferred), domain\username or username. Entra groups deployed this way don't grant Remote Desktop rights, so add individual user SIDs for RDP. Conflicting memberships across policies aren't sent and are reported as conflicts.
⚠️ Exam Trap: The built-in Help Desk Operator role can wipe and retire devices, so it's natural to assume it can rotate local administrator passwords too. It can't. The Rotate Local Admin Password permission isn't included in any built-in Intune role, nor in the Entra Intune Administrator role. To delegate rotation, create a custom Intune role with Managed devices Read, Organization Read and Remote tasks Rotate Local Admin Password.
Reflection Question: A security review finds that every laptop shares one local admin password and that ten former contractors are still local administrators. Which two Account protection profiles fix each finding, and why would assigning the LAPS profile to user groups make the fix unreliable?