Skip to content

Windows LAPS & BitLocker Escrow Gaps

The question it answers: Which Windows devices have no BitLocker recovery key or Windows LAPS password backed up in Entra ID?

Two secrets must be in Entra ID before something goes wrong: the BitLocker recovery key (or the device’s data is gone when it locks out) and the Windows LAPS local-administrator password (or support cannot log in when the device loses trust). Windows devices missing either are listed first.

Where in the appIntune › Endpoint Security & Readiness › LAPS & BitLocker Escrow
WorkloadIntune
KindTable
DataBuilt from the tenant data IntensiveReports keeps in memory and refreshes in the background, so it opens at once.
LicenceMicrosoft Intune; Windows LAPS enabled in Entra ID device settings.
Report id (API and MCP)intune.endpoint.recovery-escrow-gaps
ColumnKeyType
DeviceDeviceNameLink
UserUserPrincipalNameText
FindingFindingStatus
LAPSCategoryText
BitLocker keysValueText
OwnershipOwnerTypeText
Last syncLastSyncDateTimeDate
FilterKey (API)On when the page opens
Only devices with a gapgapsYes

Licence: Microsoft Intune; Windows LAPS enabled in Entra ID device settings.

Application permissions on the IntensiveReports app registration (all permissions):

PermissionAPIWhat it allowsNote
DeviceLocalCredential.ReadBasic.AllMicrosoft GraphRead device local credential properties
BitlockerKey.ReadBasic.AllMicrosoft GraphRead all BitLocker keys basic information
DeviceManagementManagedDevices.Read.AllMicrosoft GraphRead Microsoft Intune devices
Data sources it reads
  • GET /v1.0/directory/deviceLocalCredentials (no credentials)
  • GET /v1.0/informationProtection/bitlocker/recoveryKeys (no key material)
  • GET /beta/deviceManagement/managedDevices
GET /ir-api/v1/reports/intune.endpoint.recovery-escrow-gaps?size=100
GET /ir-api/v1/reports/intune.endpoint.recovery-escrow-gaps?filter=gaps

An AI assistant reads it with the MCP tool get_report and the id intune.endpoint.recovery-escrow-gaps. The client needs the Read grant for Intune. See Using the API.