Hi!
Thank you for the information. Based on what you describe, the key symptom is: no Event ID 10037, no password backup to Entra ID, and Get-LapsPolicy not showing settings applied. It means the policy is not actually taking effect on the devices, even though you deployed it.
I have two things in mind that might be the root cause of it.
- Windows version
- Windows LAPS (New LAPS integrates with Entra ID) was only introduceApril 2023 cumulative updates.
- Windows 10/11 20H2 is out of support and does not receive those patches anymore. The new LAPS client simply isn’t present there.
- Supported:
- Windows 10 21H2/22H2 (with April 2023 or later CU installed).
- Windows 11 21H2/22H2/23H2 (also patched April 2023+).
Policy delivery
- Intune will happily deploy the setting, but if the OS does not have the new LAPS CSP/engine, it just won’t apply (hence Get-LapsPolicy shows nothing).
- RBAC vs. backup target
- You’ve chosen Backup directory = Entra ID (which is correct for cloud-only). Since the device isn’t even generating a password, RBAC isn’t the blocker here.
You need to verify first.
a. On an affected endpoint, run PowerShell:
Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages" | Select-String "LAPS"
Note: If nothing is found, the built-in Windows LAPS isn’t present.
b. You need to update
- Upgrade Windows 10 20H2 endpoints → 22H2.
- Patch all Windows 10/11 devices with the latest cumulative updates so that C:\Windows\System32\laps.dll exists. c. Re-enforce the policy
- After upgrade and patch, trigger Intune sync + reboot.
- Run: (PowerShell)
- Get-LapsPolicy
- Get-LapsDiagnostics
Now you should see settings applied.
d. Confirm backup
After successful processing, Event Viewer → Applications and Services Logs → Microsoft → Windows → LAPS → Operational will show Event ID 10037.
In Intune / Entra → Device → Local administrator password, the password and expiration should appear.