โ† Windows & Intune
๐Ÿ“ฑ Intune

BitLocker Recovery Key Not Found in Azure AD

Walk through why BitLocker keys fail to escrow and the policy fixes needed to prevent it at scale across your Intune-managed devices.

โ„น๏ธ
What's happening: Intune requires a BitLocker policy to trigger key escrow. If the device encrypted before policy applied, or the policy is misconfigured, the key won't appear in Azure AD / Entra ID.
Check Current Encryption & Escrow Status
# Check if drive is encrypted:
manage-bde -status C:

# Check if key is backed up to Azure AD:
(Get-BitLockerVolume -MountPoint C).KeyProtector |
  Where-Object {$_.KeyProtectorType -eq 'RecoveryPassword'}

Force Escrow of Existing Key

If the drive is already encrypted but the key isn't in Azure AD, trigger escrow manually.

$KeyId = (Get-BitLockerVolume -MountPoint "C:").KeyProtector |
           Where-Object {$_.KeyProtectorType -eq 'RecoveryPassword'} |
           Select-Object -ExpandProperty KeyProtectorId
BackupToAAD-BitLockerKeyProtector -MountPoint "C:" -KeyProtectorId $KeyId

Create or Fix the Intune BitLocker Policy

Go to Endpoint security โ†’ Disk encryption โ†’ Create policy โ†’ Windows โ†’ BitLocker and verify these settings:

โ†’
Require device encryption
Yes
โ†’
BitLocker recovery information to Azure AD
Recovery passwords and key packages
โ†’
Enable recovery information storage in Azure AD before BitLocker
Yes (critical โ€” prevents encryption without escrow)