User Profile
Drogon1635
Copper Contributor
Joined 4 years ago
User Widgets
Recent Discussions
Re: Microsoft Entra ID (Azure AD) support for Passkeys
mcoombe, Thanks for these. Since adding those AAGUIDs I now see this: I got all excited by the new screens only to be left disappointed at the end when the Microsoft Authenticator app on my iPhone tells me Passkeys is not yet supported. Couldn't get a screenshot as its not on the screen long enough. maybe not yet enabled on our Tenant or in Australia.Re: Microsoft Entra ID (Azure AD) support for Passkeys
March has come and gone, still no passkeys. We contacted MS support about this and they said that the feature would appear in the "Preview features" area of Entra ID: But I am skeptical that it will appear here. We have followed the instructions to configure the following in our test tenant, the AAGUID's are not easy to find. We believe reading this that the only way to opt in is to do the part in red? " In the Entra admin portal, we will be renaming “FIDO2 security keys” to “Passkeys (FIDO2)” within the authentication methods policy and Conditional Access authentication strengths policy. For your organization to opt-in to this preview, you will need to enforce key restrictions to allow specified passkey providers in your FIDO2 policy. Here are the possible configuration states for FIDO2 key restrictions during the preview: No key restrictions (FIDO2 policy default): Tenant allows all security key models. Device-bound passkey providers on computers and mobile devices are not allowed. Key restrictions set to "Allow": Tenant only allows the explicitly added AAGUIDs. To enable a device-bound passkey provider, add their AAGUID(s) to the key restrictions list. Key restrictions set to "Block": Tenant blocks the explicitly added AAGUIDs and allows all other security key models. Device-bound passkey providers on computers and mobile devices are not allowed." Still not working, same error when naming the passkey that you guys are seeing. I do not understand how Microsoft can have this is an error state for so long and now that "Passkey (Preview)" is now also showing for us when configuring Authentication methods it makes it even worse. Microsoft, if it is not ready for production don't show us enticing setup wizards that are made to fail until release, its been months!
