Hi,

A while ago I‘ve written an article about BitLocker and PIN with Intune. See here:

https://oliverkieselbach.com/2019/08/02/how-to-enable-pre-boot-bitlocker-startup-pin-on-windows-with-intune/

Best,
Oliver

Hey anonymous user,

have a look at the documentation, your devices must be registered in Autopilot by a Cloud Solution Provider (CSP). The CSP here is not referencing the Configuration Service Provider (CSP) which is mostly used in regards to Intune topics especially for configuration profiles.

https://docs.microsoft.com/en-us/mem/autopilot/dfci-management > section Requirements

best,

---

Oliver Kieselbach | Twitter | Blog
Mark useful answers by clicking "Accept Answer", many thanks!

Hey,

The "FakePolicy" can be ignored safely, see this clarification post from the Intune Support team:

best,

---

Oliver Kieselbach | Twitter | Blog
Mark useful answers by clicking "Accept Answer", many thanks!

Reimage will not alter the hash but certain hardware changes will, see here: https://docs.microsoft.com/en-us/windows/deployment/windows-autopilot/autopilot-mbr
If you just look at the gathered hash you will notice a different value, don't get confused the hash is constructed with different parameters internally and there is also a timestamp included, so calling the script will create different hashes every time, but the internal hash will stay the same.

Yes import a device hash and as long as the hardware does not change significantly you can just reset and re-enroll as often as you want it will always do Autopilot.