@Djordje Novakovic , For "not configured" value, it means we don't want to use Intune to control Windows Hello for Business settings. Any existing Windows Hello for Business settings on 10/11 devices isn't changed. If we don't want to enable Windows Hello for Business during device enrollment, we can change the value to disable to see if it is there. Here is a link for the reference:
https://learn.microsoft.com/en-us/mem/intune/protect/windows-hello#create-a-windows-hello-for-business-policy
For the Windows Hello for Business policy under Windows enrollment, It supports the Windows AutoPilot out-of-box-experience (OOBE) and is applied when a device enrolls. It will not affect the device in on premise environment which is not enrolling into Intune.
If this is a Hybrid Azure AD joined device and enroll into Intune and we deployed Windows Hello for Business configuration using both Group Policy and Microsoft Intune, Group Policy settings will take precedence and Intune settings will be ignored. Here is an article for the reference:
https://learn.microsoft.com/en-us/windows/security/identity-protection/hello-for-business/hello-hybrid-key-whfb-settings-policy
Hope it can help.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.