Skip to content

Commit f5ac735

Browse files
committed
[AzureAD] Additional edits
1 parent 3aa69ad commit f5ac735

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

articles/active-directory/authentication/concept-authentication-methods.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -89,10 +89,10 @@ Users may have a combination of up to five OATH hardware tokens or authenticator
8989

9090
The FIDO (Fast IDentity Online) Alliance helps to promote open authentication standards and reduce the user of passwords as a form of authentication. FIDO2 is the latest standard that incorporates the web authentication (WebAuthn) standard.
9191

92-
Users can register and then select a FIDO2 security key at the sign-in interface as their main means of authentication. These FIDO2 security keys are typically USB devices, but could also use Bluetooth or NFC. With a hardware device that handles the authentication, the security of an account is increased as there's no password that could be exposed or guessed.
93-
9492
To use FIDO2 security keys at a sign-in prompt rather than a username and password combination, see [Enable passwordless FIDO2 security key sign-in (preview)](howto-authentication-passwordless-security-key.md).
9593

94+
Users can register and then select a FIDO2 security key at the sign-in interface as their main means of authentication. These FIDO2 security keys are typically USB devices, but could also use Bluetooth or NFC. With a hardware device that handles the authentication, the security of an account is increased as there's no password that could be exposed or guessed.
95+
9696
FIDO2 security keys in Azure AD are currently in preview. For more information about previews, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
9797

9898
## OATH hardware tokens

articles/active-directory/authentication/howto-mfa-mfasettings.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ Some of these settings apply to MFA Server, Azure MFA, or both.
3333
| [Block/unblock users](#block-and-unblock-users) | Used to block specific users from being able to receive Multi-Factor Authentication requests. Any authentication attempts for blocked users are automatically denied. Users remain blocked for 90 days from the time that they are blocked. |
3434
| [Fraud alert](#fraud-alert) | Configure settings related to users ability to report fraudulent verification requests |
3535
| [Notifications](#notifications) | Enable notifications of events from MFA Server. |
36-
| [OATH tokens](concept-authentication-methods.md#oath-hardware-tokens-preview) | Used in cloud-based Azure MFA environments to manage OATH tokens for users. |
36+
| [OATH tokens](concept-authentication-methods.md#oath-hardware-tokens) | Used in cloud-based Azure MFA environments to manage OATH tokens for users. |
3737
| [Phone call settings](#phone-call-settings) | Configure settings related to phone calls and greetings for cloud and on-premises environments. |
3838
| Providers | This will show any existing authentication providers that you may have associated with your account. New authentication providers may not be created as of September 1, 2018 |
3939

0 commit comments

Comments
 (0)