Enabling BitLocker on non-HSTI devices with Intune


This is a post about enabling BitLocker on non-HSTI devices with Windows 10 version 1809 and standard user permissions.

First of all a little background on HSTI. HSTI is a Hardware Security Testability Interface. It is an interface to report the results of security-related self-tests. Its purpose is to provide high assurance validation of proper security configuration.

The enhancement with Windows 10 version 1809 is that we are able to activate BitLocker with a MDM policy (Intune), even for non-HSTI devices and on Windows 10 Pro Edition. This was not working with Windows 10 version 1803 or lower and the community came up with custom solutions to handle this like custom PowerShell scripts deployed via Intune Management Extension. If we wanted to use Intune native MDM policies via the BitLocker CSP we needed HSTI compliant devices like the Surface devices or newer hardware devices which are mostly delivered as HSTI compliant devices now. To successful start the encryption as a standard user, a Windows 10 version 1803 was the minimum as the feature was introduced with this version.

The prerequisites for Intune BitLocker configuration are:

  • Windows 10 version 1809 Enterprise and Pro
  • Azure Active Directory joined devices
  • Microsoft Intune
  • non-HSTI device

Older devices can be protected by Intune BitLocker policy now?

Yes, as long as they are running Windows 10 version 1809. The most common problem is that we do not replace all devices in every Windows 10 project to have only latest HSTI compliant devices in the environment. We have to support older devices purchased maybe not long ago but not HSTI compliant. These devices can now be managed by an Intune device configuration policy to turn on BitLocker silently without administrative permissions as long as the device is a Windows 10 version 1809 device.

What do we need to do?

Currently at the time of writing we need two configuration policies. One endpoint protection profile and a custom profile.

The endpoint protection profile configures the silent BitLocker enforcement and other parameters like encryption strength. Go to Microsoft Intune > Device configuration – Profiles > yourpolicyname – Properties > Endpoint protection > Windows Encryption

Set Encrypt devices to Require
Set Warning for other disk encryption to Block

Sure you can set other parameters like encryption methods as well, but for a functional test this is enough.

These two settings make sure the encryption starts and it starts silently as we block the warning dialog for other disk encryption software.

Example shown below:


The second profile is a custom profile (at time of writing it was not available in the UI) and it configures the ability to enforce the BitLocker encryption even when standard users are logging in. For example when the Windows 10 device is enrolled with an Autopilot profile where the user account type is set to standard user. AllowStandardUserEncryption is a new setting introduced with Windows 10 version 1809 BitLocker CSP and must be used in conjunction with the setting “Warning for other disk encryption set to Block” otherwise it is not functional!

The custom OMA-URI configuration must be configured like this:

OMA-URI: ./Vendor/MSFT/BitLocker/AllowStandardUserEncryption
Data type: integer
Value: 1

Example shown below:


See the Update section below for a new UI setting available in Intune 1901 release.

The two policies must be assigned to a user group or device group to test the new policies. To force the user type to a standard user after enrollment we need an Autopilot profile and assign it to our device.


If we now enroll a new Windows 10 version 1809 non-HSTI device it must be encrypted silently and the recovery key must be backed up to Azure AD.

How can I easily verify this?

I used a Hyper-V VM Generation 2 with an enabled TPM module:


To test if the VM is reporting as a non-HSTI compliant device I downloaded the Device Guard and Credential Guard hardware readiness tool and verified the HSTI status with the following PowerShell command:

.\DG_Readiness_Tool_v3.5.ps1 -Capable

The result is displayed like this:


During my test I had to make sure that after the first restart, the Windows 10 version 1809 ISO is ejected, otherwise silent BitLocker encryption will fail. This is because the system does not have the normal start parameters during the BitLocker and TPM provisioning. The platform would take into account the additional media as the normal platform verification parameter. Which means after ejecting the ISO it would have prompted us for the recovery key. Microsoft takes care of this situation and does not start the BitLocker provisioning process at all. So, the generation of the platform default configuration parameters for later verification to unlock the TPM is prevented, as long as a removable media is inserted. See the failure event here:


Without an ISO it will successfully starts the encryption and key backup to Azure AD. A success event is shown below:


The BitLocker state can be verified with the PowerShell command on the client:

Get-BitLockerVolume | fl

In the Intune portal we can see the recovery key appended to the AAD device object:



Since Intune January 21th 2019 Release (aka 1901) we are able to configure the BitLocker Allow Standard User setting via UI element:

Further information

What’s new in Windows 10, version 1809 for IT Pros

Device Guard and Credential Guard hardware readiness tool

Hardware Security Testability Specification

Go ahead and start encrypting all your Windows 10 devices to strengthen your security level 👍

12 thoughts on “Enabling BitLocker on non-HSTI devices with Intune”

  1. Great detailed blog once again sir Kieselbach. Questions i have. 1) did i read it correct we now also can use bitlocker csp for Windows 10 Pro ? 2) Silly question what about old devices without tpm ? PS is hsti like instantgo on surfaces ?

    1. Hi RKast,

      thank you sir :-).
      – Yes starting in Windows 10, version 1809, it is also supported in Windows 10 Pro.
      – BitLocker can be implemented without TPM for example with startup password but this is not supported with Intune. This must be scripted.
      – Yes HSTI is a bit like InstantGo. An InstantGo device should work.


  2. Hi Oliver,
    What i cannot find for bitlocker on Windows 10 pro is, can/do we also use the endpoint protection or use oma-uri? Thanks.

    1. Hi RKast,

      The endpoint protection profile does utilize the BitLocker CSP in the end. As long as you are using a Windows 10 version 1809 which has the latest BitLocker CSP you can use endpoint protection profile. But the endpoint protection profile also includes defender exploit guard which is a Windows 10 Enterprise feature (https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-defender-exploit-guard/windows-defender-exploit-guard) this can’t be managed on Pro then. So try it out and configure only the parts available for Pro editions. As fallback you can take the OMA-URIs of the BitLocker CSP directly and configure all the settings.


  3. Great blog post, thanks. Any idea when this new option might be available in the Portal alongside all the other Bitlocker settings?

  4. Hi oliver , is the /Vendor/MSFT/BitLocker/AllowStandardUserEncryption still necessary when using ‘Warning for other disk encryption’ option with win10 1809 ? On this blogpost only enabling the ‘Warning’ option enforces bitlocker when using a non administrative account (https://www.vroege.biz/?p=3998)

    1. Hi Tomothy,

      yes it is needed, the blog from Vroege is based on information of 1803 Insider Preview. It is needed with the final builds. The new setting was introduced with 1809 and you can see the info on the BitLocker CSP site: https://docs.microsoft.com/en-us/windows/client-management/mdm/bitlocker-csp

      In addition you can easily test it out, skip the setting and you will see encryption will not start, with the setting the encryption will start in a standard user scenario. It is expected that this setting will also soon appear in the Intune UI as well.


  5. Another great post. I do have a question, I can see the “Allow Standard User to enable encryption….: in the Intune UI but will that only work with 1809 devices? I’m spinning my wheels trying to get this to work with 1803 but the device never encrypts. I’ve tried both the CSP and the settings in the UI. Unless this just won’t work with 1803.

    1. Hi,

      Yes it is only available with 1809, it is written here in this paragraph
      AllowStandardUserEncryption is a new setting introduced with Windows 10 version 1809 BitLocker CSP and must be used in conjunction with the setting “Warning for other disk encryption set to Block” otherwise it is not functional!
      The official documentation is tricky but you can see it in the diagram in the beginning here:
      AllowStandardUserEncryption was added with 1809… https://docs.microsoft.com/en-us/windows/client-management/mdm/bitlocker-csp


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s