BitLocker policy is enabled by default?Solved

@finn I don’t think the Bitlocker policy or in fact, any Device Policy gets assigned to devices by default, once they are enrolled into Hexnode.

@ronnie , But I see that the Windows device I just enrolled into my portal is non-compliant due to no encryption – is it not because of the BitLocker policy?

@finn , I think you are talking about the “Default Windows Compliance policy” applied to Windows devices as soon as they are added to the portal.

@ronnie ,Yes, I see that such a policy has been applied automatically, so what should I do to make my device compliant again?

@finn , please note that the Default Windows Compliance Policy within the Hexnode UEM portal specifically mandates that device encryption must be active for a system to maintain a “Compliant” status. 

Enabling BitLocker on your device serves as the necessary signal to the UEM portal that this security requirement has been met. Once the encryption process is initiated, the device will automatically be marked as compliant upon completion of its next Device Scan. 

Regards,  
Elle Reed, 
Hexnode UEM. 

@elle_reed , if so, how do I turn on the BitLocker then?

Thanks @elle_reed! 

@finn , Additionally, it is worth noting that this compliance concern is largely mitigated in the latest iterations of the operating system. Starting with Windows 11 Version 24H2, BitLocker encryption is enabled by default across the Pro, Enterprise, and Education editions during Out-of-box (OOBE) experience. Because the encryption is active from the initial setup, the device should automatically meet the compliance requirements without any manual intervention or policy configuration. 

@elle_reed , is that so? Mine is probably in an older version. I will keep this in mind for future devices, thanks!