4.1.2. Disk Encryption: BitLocker and FileVault
💡 First Principle: Encryption is the control that still works after every other one has failed — the device is in someone else's hands and switched off. But a drive whose recovery key you can't find is just a slower way to lose data. The real design problem has two halves: encrypt without asking users to do anything, and make sure the recovery key is escrowed somewhere you control before encryption begins.
The Disk encryption policy type has three profiles: BitLocker (Windows full-volume encryption), Personal Data Encryption (PDE) and macOS FileVault.
Choosing the policy type for BitLocker. Microsoft's recommended path is Endpoint security > Disk encryption > Create Policy > Platform: Windows > Profile: BitLocker; the alternative is a device configuration profile using the Endpoint protection template's Windows Encryption settings. What you should not use for silent enablement is the Settings Catalog on its own: it doesn't include the TPM startup authentication controls that reliable silent BitLocker needs.
Silent encryption. Silent encryption means the drive encrypts with no prompts and no user action. It needs a device that is Microsoft Entra joined or Entra hybrid joined, with TPM 1.2 or later, native UEFI, Secure Boot and the Windows Recovery Environment (WinRE) configured. If standard (non-admin) users sign in, the device must run Windows 10 1809 or later or Windows 11. The key endpoint security settings are:
- Require Device Encryption = Enabled.
- Allow Warning For Other Disk Encryption = Disabled. Only after you set this does Allow Standard User Encryption appear — set it to Enabled whenever standard users sign in.
- Require additional authentication at startup = Enabled, with the TPM startup PIN, startup key and key-and-PIN options all set to Do not allow, and TPM startup set to Allow TPM or Require TPM. A startup PIN needs a person at the keyboard, which is the opposite of silent.
Disabling the other-encryption warning tells BitLocker to proceed even when third-party encryption is present, which risks data loss and boot failures. Inventory devices for other encryption products first, and pilot.
The order in the diagram matters: for silent enablement, the recovery key backs up to Microsoft Entra ID automatically, and backup happens before encryption. That's why a device that has hit Entra ID's limit of 200 BitLocker recovery keys per device fails to encrypt — the backup fails first. Encryption type follows hardware: devices with modern standby get used space only encryption, others get full disk, unless you force a type with the Settings Catalog setting Enforce drive encryption type on operating system drives.
Recovery keys. Admins view a key at Devices > All devices > (device) > Monitor > Recovery keys > Show Recovery Key, which requires an Entra permission to read BitLocker keys; every view writes an audit entry under the KeyManagement activity. Key rotation — including the on-demand BitLocker key rotation remote action from Phase 3 — depends on three policy settings: Client-driven recovery password rotation enabled for Entra joined (or Entra and hybrid joined) devices, Save BitLocker recovery information to Microsoft Entra ID = Enabled, and Store recovery information in Microsoft Entra ID before enabling BitLocker = Required. Two deletions bite here: deleting the Intune object for an Entra joined BitLocker device leaves BitLocker suspended, and deleting a device in Microsoft Entra ID removes its BitLocker keys permanently. Wipe or retire before you delete.
Self-service recovery. Users can retrieve keys for their own devices through the Company Portal, the My Account portal or Microsoft Entra ID. A tenant-wide Entra device setting, Restrict non-admin users from recovering the BitLocker key(s) for their owned devices, governs this, and changing it requires at least Privileged Role Administrator. Because keys count as corporate resources, a Conditional Access policy requiring a compliant device can stop noncompliant devices from reaching them. Each retrieval lands in the Entra audit log as Read BitLocker key.
PDE adds file- and folder-level encryption on Windows 11 22H2 or later. It works alongside BitLocker, not instead of it: BitLocker releases keys at boot, while PDE releases them only when the user signs in with Windows Hello for Business.
FileVault is the macOS equivalent, with a few differences worth comparing:
| Aspect | BitLocker (Windows) | FileVault (macOS) |
|---|---|---|
| Policy | Endpoint security BitLocker profile | Endpoint security macOS FileVault profile, or Settings Catalog Full Disk Encryption |
| Key escrow | Recovery key to Microsoft Entra ID | Personal recovery key escrowed to Intune |
| Admin key view | Device > Monitor > Recovery keys | Same path, but only for devices marked Corporate |
| User key retrieval | Company Portal, My Account, Entra ID | Company Portal website (Get recovery key) |
| Rotation | Client-driven rotation settings or remote action | Automatic every 1–12 months, or manual for Corporate devices |
| Notable requirement | TPM, UEFI, Secure Boot, WinRE for silent | User-approved MDM enrollment; encryption starts only when the Mac is plugged in |
The FileVault profile needs Enable = On and Use Recovery Key = Enabled, and the personal recovery key is shown to the user once at encryption. Encryption is fixed at XTS-AES 128-bit. Enforcing FileVault during Setup Assistant (macOS 14 or later, Apple Business Manager or Apple School Manager enrollment) is possible only through the Settings Catalog.
Monitoring. The encryption report lives at Devices > Manage devices > Configuration > Monitor > Device encryption status. It shows TPM version, Encryption readiness and Encryption status, covers only the OS drive, can take up to 24 hours to reflect a change, and exports to CSV with per-device status details such as "WinRE not configured" or "recovery key backup failed". If you pair encryption with a compliance policy, remember that Require BitLocker is measured at boot, so a freshly encrypted device may need a restart before it reports compliant.
⚠️ Exam Trap: "Configure BitLocker silently with a Settings Catalog profile" sounds modern and right, but Microsoft says the Settings Catalog lacks the TPM startup authentication controls needed for reliable silent enablement. Choose the endpoint security BitLocker profile (or the Endpoint protection template). And if silent encryption still fails on devices that also get the security baseline for Microsoft Defender, check it: that baseline can enable a TPM startup PIN and key by default.
Reflection Question: Silent BitLocker succeeds on laptops used by IT staff but fails on identical laptops used by standard users. Which setting is probably missing, and why might the admin who built the policy never have seen it?