To check LAPS password backups in Microsoft Intune, list the Windows devices joined to Microsoft Entra ID and the local administrator passwords backed up there, then keep the devices with none. Windows LAPS backs a password up to Entra ID only when the tenant setting is on and a policy on the device sends it there. The list says when each password was backed up and is next due to change, never the password itself.
| Method | Best fit |
|---|---|
| PowerShell | A CSV of joined Windows devices with whether a password is backed up and when it next changes. |
| Admin centre | Reading the devices that have a password backed up, and the tenant setting. |
| Altivane | Recommended for recurring reviews, with each device's password and BitLocker key backups side by side. |
Before you start
Use an account with a role Microsoft lists for reading LAPS details without the password: Cloud Device Administrator, Intune Administrator, Helpdesk Administrator, Security Administrator, Security Reader or Global Reader. LAPS works with Microsoft Entra ID Free or higher. The PowerShell example requests DeviceLocalCredential., which lists backups without their passwords, and Device.; your organisation may require administrator consent.
LAPS covers Windows devices joined or hybrid joined to Microsoft Entra ID, not registered devices. The backups are read as Entra ID holds them now. Recovering a password is recorded in the audit log, and none of the steps here recover one. The examples read and export; they change nothing and reveal no password.
Option 1
Check LAPS password backups with PowerShell
Install the modules once, then connect, read the devices and the backups and match them by device ID.
# Install once, if the modules are not already installed.
Install-Module Microsoft.Graph.Authentication,
Microsoft.Graph.Identity.DirectoryManagement -Scope CurrentUser$ErrorActionPreference = 'Stop'
Connect-MgGraph -Scopes 'DeviceLocalCredential.ReadBasic.All', 'Device.Read.All' -NoWelcome
try {
$properties = 'deviceId', 'displayName', 'operatingSystem', 'trustType', 'accountEnabled'
# Entra joined (AzureAd) and hybrid joined (ServerAd), not registered personal devices.
$filter = "trustType in ('AzureAd', 'ServerAd')"
$devices = @(Get-MgDevice -All -Filter $filter -Property $properties |
Where-Object { $_.OperatingSystem -like 'Windows*' })
$backups = @{}
# Each backup's ID is the device ID of the device it came from.
foreach ($backup in Get-MgDirectoryDeviceLocalCredential -All) {
$backups[$backup.Id] = $backup
}
$report = foreach ($device in $devices) {
$backup = $backups[$device.DeviceId]
[pscustomobject]@{
Device = $device.DisplayName
TrustType = $device.TrustType
Enabled = $device.AccountEnabled
BackedUp = $null -ne $backup
LastBackup = $backup.LastBackupDateTime
NextRotation = $backup.RefreshDateTime
}
}
$report = @($report | Sort-Object BackedUp, Device)
$missing = @($report | Where-Object { -not $_.BackedUp }).Count
if ($report.Count -eq 0) {
Write-Output 'No Windows device is joined to Microsoft Entra ID.'
} else {
$report | Export-Csv -Path './laps-backups.csv' -NoTypeInformation -Encoding utf8
Write-Output "$missing of $($report.Count) Windows devices have no LAPS password."
}
} finally {
Disconnect-MgGraph | Out-Null
}The CSV has 1 row for each joined Windows device, those with no backup first, with when its password was last backed up and when it's next due to change. A next rotation well in the past points to a device that hasn't been online to change it. To keep disabled devices out, add -and $_. after the operating system test.
Option 2
Check LAPS backups in the Entra admin centre
- Sign in to the Microsoft Entra admin centre for the correct tenant.
- Go to Entra ID > Devices > Overview > Device settings and read whether Enable Local Administrator Password Solution (LAPS) is set to Yes. Leave the page without selecting Save.
- Go to Entra ID > Devices > Overview > Local administrator password recovery to list the devices with a password backed up.
- Compare that list with your Windows devices. Leave the passwords hidden: recovering one is recorded in the audit log.
This suits confirming the tenant setting and looking up a device. The list shows the devices that have a backup, not the ones without, so for the gaps use PowerShell or a report.
Option 3 ยท Recommended for recurring reviews
Check LAPS backups with Altivane
- Open Altivane and choose the tenant.
- Run the BitLocker Keys and LAPS Passwords report.
- Open the tenant's Excel workbook and find Recovery backup by device: each Windows device joined to Entra ID, those that need a look first, with LAPS Password, Last LAPS Backup, Next LAPS Rotation and Needs a Look saying No LAPS password or LAPS rotation overdue.
- Read Recovery backup summary for how many devices have no LAPS password or a password change overdue.
Altivane reads only when each password was backed up and is next due to change, never the password itself, and marks a password more than 7 days past its next rotation as overdue. The same row shows how many BitLocker recovery keys the device has and when the last was backed up. Where the passwords couldn't be read, their columns are blank rather than every device counted as without. The report needs a tenant signed in with a certificate.
Contact usCommon questions
Why does a device have no password backed up?
Check both halves of the setup. Microsoft says the tenant setting must be on and a policy on the device must set its backup directory to Microsoft Entra ID, through Intune or, for hybrid joined devices, Group Policy. The device also needs a Windows version with the April 2023 update or later.
What happens to the password when a device is deleted?
It's lost. Microsoft says deleting a device in Entra ID deletes the password stored with it, and there's no way to recover it there afterwards.
Are BitLocker recovery keys backed up the same way?
They're kept with the device in Entra ID too, and a device can have one without the other. See how to find missing BitLocker recovery keys in Intune.
Microsoft references
Technical references checked on 7 November 2026. The example scripts have been reviewed and syntax checked; they have not been run against a live tenant.