diff --git a/windows/security/identity-protection/hello-for-business/microsoft-compatible-security-key.md b/windows/security/identity-protection/hello-for-business/microsoft-compatible-security-key.md index cc059702b7..fb9afb773b 100644 --- a/windows/security/identity-protection/hello-for-business/microsoft-compatible-security-key.md +++ b/windows/security/identity-protection/hello-for-business/microsoft-compatible-security-key.md @@ -1,22 +1,26 @@ --- -title: Microsoft compatible security key -description: Windows 10 enables users to sign in to their device using a security key. How is a microsoft compatible security key different (and better) than any other FIDO2 security key +title: Microsoft-compatible security key +description: Windows 10 enables users to sign in to their device using a security key. How is a Microsoft-compatible security key different (and better) than any other FIDO2 security key keywords: FIDO2, security key, CTAP, Hello, WHFB ms.prod: w10 ms.mktglfcycl: deploy ms.sitesec: library ms.pagetype: security, mobile -author: aabhathipsay-MS +author: aabhathipsay ms.author: aathipsa ms.localizationpriority: medium -ms.date: 10/25/2018 +ms.date: 11/14/2018 --- -# What is a Microsoft compatible security key? +# What is a Microsoft-compatible security key? +> [!Warning] +> Some information relates to pre-released product that may change before it is commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here. + + Microsoft has been aligned with the [FIDO Alliance](https://fidoalliance.org/) with a mission to replace passwords with an easy to use, strong 2FA credential. We have been working with our partners to extensively test and deliver a seamless and secure authentication experience to end users. The [FIDO2 CTAP specification](https://fidoalliance.org/specs/fido-v2.0-id-20180227/fido-client-to-authenticator-protocol-v2.0-id-20180227.html) contains a few optional features and extensions which are crucial to provide that seamless and secure experience. -A security key **MUST** implement the following features and extensions from the FIDO2 CTAP protocol to be Microsoft compatible: +A security key **MUST** implement the following features and extensions from the FIDO2 CTAP protocol to be Microsoft-compatible: | #
| Feature / Extension trust
| Why is this required?
| | --- | --- | --- |