SCCM Tips. Fixes and Guides

Keep it Simple with Intune – #3 Disk Encryption

In the third entry in the Keep it Simple with Intune series, I show you how to enforce BitLocker disk encryption on your Windows 10 device and store the recovery key in Azure AD.

Encrypting the device via Intune with BitLocker is very simple to set up. As with our start menu from #2 in the series, you will need to configure a device configuration profile in the Azure Portal and assign this to your devices.

In the portal, navigate to Intune>Device Configuration>Profiles. Click Create Profile.

Enter a Name for the profile, a Description choose Windows 10 and later for the Platform and select Endpoint Protection for the Profile type. Scroll down the Endpoint Protection blade and select Windows Encryption.

From here you can select the BitLocker encryption settings you wish to applying to your devices. Encrypt devices needs to be set to Require. I recommend that XTS-AES 265-bit is set for the operating system drive.

A choice of start up type is available, TPM only, TPM + PIN, for example.

Also the ability to block user choice on recovery key save options, forcing the key to be saved into Azure AD.

With the relevant settings configured click OK, OK and Save.

After creating the profile, assign this to the relevant set of devices.

When your device syncs you can see that the BitLocker policy has been applied under Settings>Accounts>Access work or school on the Windows 10 device and by clicking the connected accounts details and selecting Info.

The end user will be notified that Encryption is needed on the device.

The user can choose to encrypt used space or the entire drive.

The options which appear in the wizard are determined by the configuration of the BitLocker profile. For my settings, I have not given the user an option of where to save the recovery key, opting instead to save this immediately into Azure AD.

The user is given the choice of running a BitLocker system check before beginning the encryption.

By running manage-bde -status I can see that the XTS-AES 256 algorithm I selected in the profile is being enforced.

and by issuing the command manage-bde -protectors -get c: I can take a look at the recovery key which, if this has all worked, should be stored in the Azure AD.