Forum Discussion
Andrew Matthews
Nov 09, 2018Iron Contributor
CSP Policy for BitLocker Encryption on AutoPilot Devices
According to the What's new in Windows 10 1809 the following functionality is available. You can choose which encryption algorithm to apply automatic BitLocker encryption to capable devices, rath...
- Nov 26, 2018
After a great deal of experimentation and a blog post from Per Larson; I tracked down the cause of the issue.
The encryption section of the EndPoint Protection policy does not correctly apply to AAD Joined devices capable of HSTI if the policy is set to Encrypt Device: Require.
I was able to successfully encrypt a device during AutoPilot with AES 256 under the following circumstances.
- Create a brand new Endpoint Protection policy (Important!)
- Apply the encryption settings that you want to set
- Make sure the Encrypt Device setting is set to Not Configured
- Apply the policy to a group containing Azure AD Joined windows devices
- Do not target the policy at user accounts
The policy settings that I used are attached.
smukherjee
Copper Contributor
How to force user to set pre boot bitlocker pin for autopilot devices?
Andrew Matthews
Jun 01, 2021Iron Contributor
You cannot silently enable BitLocker when the policy requires a startup PIN. I would suggest that you write a PowerShell script to set the PIN after the device reaches the desktop. I do not personally have that script but I have seen examples using XAML forms.
https://docs.microsoft.com/en-us/mem/intune/protect/encrypt-devices
https://docs.microsoft.com/en-us/mem/intune/protect/encrypt-devices