BitLocker enablement via Intune: a practical checklist

Last reviewed: November 21, 2026 · 12 min read

Encrypting the disk is only half of the job. If the recovery password is not stored where your help desk can retrieve it, the first firmware prompt or forgotten PIN becomes a device you cannot unlock. This checklist walks through enabling BitLocker with Intune so encryption and key escrow happen in the right order.

Choose the policy type and the encryption path

Microsoft's current guidance is to use an Endpoint security > Disk encryption policy with the BitLocker profile, rather than burying BitLocker inside a broader device-configuration profile. The official walkthrough is Encrypt Windows devices with BitLocker using Intune.

Intune supports two approaches:

For silent encryption, Microsoft lists these device requirements: Windows 10 version 1803 or later (or Windows 11) if the user is a local administrator, or Windows 10 version 1809 or later (or Windows 11) if the user is a standard user; Microsoft Entra joined or Microsoft Entra hybrid joined; TPM 1.2 or later; native UEFI BIOS mode; Secure Boot enabled; and a configured Windows Recovery Environment (WinRE). Silent encryption also picks the encryption type for you (full disk on non-modern-standby devices, used-space only on modern standby devices), so you cannot customize that part.

Before you assign a silent policy, inventory third-party encryption (and any existing BitLocker that was turned on by hand). Microsoft warns you to identify other encryption software and plan a safe removal or migration. Two encryption stacks on one disk is how you lose data, not how you get a green compliance report.

Escrow the recovery password before BitLocker turns on

Configure the policy so recovery information is stored in Microsoft Entra ID, and so BitLocker does not finish enabling until that store succeeds. Microsoft's BitLocker recovery documentation is explicit that backup of the recovery password to Entra ID or Active Directory may not happen automatically unless policy requires it. See BitLocker recovery overview and the recovery process article.

Also enable client-driven recovery password rotation for Entra joined devices (and hybrid joined, if that is your join type), so a password that has been used for recovery is replaced. Admins can also start a rotation from Intune: select the device and use the BitLocker key rotation action, documented in BitLocker key rotation.

Limit who can read recovery keys. Treat a key retrieval as a privileged action: record who requested it, rotate the password afterwards, and do not paste keys into tickets that live forever.

Roll it out in this order

  1. Confirm licenses, join type, TPM, UEFI, Secure Boot and WinRE on a pilot set of hardware models.
  2. Create the Endpoint security disk-encryption policy. Require Entra ID escrow before BitLocker is enabled, set recovery-password rotation, and assign the policy only to the pilot group.
  3. Watch the Intune Encryption report and, for each pilot device, confirm a recovery key is visible on the device object in Microsoft Entra ID. Device objects and recovery-key access are covered in Manage device identities.
  4. Practice a recovery on a spare device: use the stored key, unlock, confirm the password rotates (or rotate it yourself), and write the help-desk procedure.
  5. Expand assignment in waves. Encryption can take time and may briefly affect disk performance; do not target every device on a Friday afternoon.
  6. Only after keys are present and encryption has completed (and the device has rebooted) should a compliance policy Require BitLocker. That compliance setting is measured at boot. The starter policy is in our Windows compliance policy guide.

If you are also enrolling new PCs with Autopilot, include BitLocker in the baseline that applies to the pilot group, as described in the Autopilot checklist, and schedule the wider assignment with your wave rollout plan.

What usually goes wrong

The Device Rollout Planner helps you put encryption and compliance on the same wave schedule as enrollment, with a readiness checklist and device tracker so you can see which devices are still outstanding.

BitLocker policy names, silent prerequisites and recovery-key permissions change. Confirm each setting against the current Intune BitLocker article, and test recovery on a spare device, before you encrypt the estate.

Sources (Microsoft Learn, reviewed November 2026): Encrypt Windows devices with BitLocker using Intune; BitLocker recovery overview; BitLocker recovery process; BitLocker key rotation; Monitor device encryption with Intune; Manage device identities in Microsoft Entra ID; Windows compliance settings. Always follow the current version of those articles.

This guide was drafted with AI assistance and checked against public Microsoft documentation. How we use AI. Spotted an error? Email [email protected].