I have just installed Windows Configuration Designer from the store.
This key seems to be missing:
Runtime settings > WindowsHelloForBusiness > SecurityKeys > UseSecurityKeyForSignIn
Will there be updates to Windows Configuration Designer necessary to support UseSecurityKeyForSignIn?
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@pmeuser Thanks for your comment. We are actively investigating and will get back to you shortly.
Ensure you selected All Windows desktop editions when creating your new project.
@MicrosoftGuyJFlo I checked this again, but still version 2019.625.0.0 seems not to include this setting.
I just re-downloaded from the store and have the options available to me. I would suggest you open a support case.
I have the same issue. I just downloaded Windows Configuration Designer Version: 2019.625.0.0 on Windows Version 1809 and OS Buid 17763.557. I dont even see the "Security Keys" category under WindowsHelloforBusiness
I can confirm that the Windows version 1903 has that project setting " Runtime settings > WindowsHelloForBusiness > SecurityKeys > UseSecurityKeyForSignIn " and can be configured .
Also as per my research , it seems that the settings which you get within the Windows Configuration Designer are as per the settings which can be configured on your local machine where you are trying to use Windows Configuration Designer . I believe if you try it on Win 10 v1903 , you must be able to see the setting. Yet if you do not see the setting , please let us know .
Struggling to find this setting as the original poster mentions. am running 1903 or a Surface Laptop 2 and same version of Config Designer I get HelloForBusiness but don't get the Security Key option.
Hey @mattwhite-itl I would suggest filing a support ticket for further assistance on your issue if it's urgent.
If not please, submit a new github issue with a screen shot of your issue. Thanks!
Really selecting "All Windows desktop editions" and NOT "All Windows editions" does the trick for me ...
Will try that when I get to work today
You cannot create a provisioning package with the requirements given at the top of this doc. Requirements need to have added
a) Windows Configuration Designer required for creating a provisioning package
b) Windows Designer needs to be installed on Windows 10 1903 or later.
Without these - wont work.
Most helpful comment
Really selecting "All Windows desktop editions" and NOT "All Windows editions" does the trick for me ...