You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory/standards/memo-22-09-multi-factor-authentication.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,7 +41,7 @@ Consider the following approach to evaluating phishing-resistant MFA methods:
41
41
42
42
* Device types and capabilities that you want to support. Examples include kiosks, laptops, mobile phones, biometric readers, USB, Bluetooth, and near-field communication devices.
43
43
44
-
* User personas within your organization. Examples include front-line workers, remote workers with and without company-owned hardware, administrators with privileged access workstation, and business-to-business guest users.
44
+
* User personas within your organization. Examples include front-line workers, remote workers with and without company-owned hardware, administrators with privileged access workstations, and business-to-business guest users.
45
45
46
46
* Logistics of distributing, configuring, and registering MFA methods such as FIDO2 security keys, smart cards, government-furnished equipment, or Windows devices with TPM chips.
47
47
@@ -51,7 +51,7 @@ Consider the following approach to evaluating phishing-resistant MFA methods:
51
51
52
52
The following sections describe support for implementing phishing-resistant methods for both application and virtual device sign-in scenarios.
53
53
54
-
### Application sign-in scenarios from different clients
54
+
### Application sign-in scenarios from various clients
55
55
56
56
The following table details the availability of phishing-resistant MFA scenarios, based on the device type that's used to sign in to the applications:
57
57
@@ -102,7 +102,7 @@ The memo requires organizations to change password policies that are proven inef
102
102
103
103
* Use [Azure AD Identity Protection](..//identity-protection/concept-identity-protection-risks.md) to be alerted about compromised credentials so you can take immediate action.
104
104
105
-
While the memo isn't specific on which policies to use with passwords, consider the standard from [NIST 800-63B](https://pages.nist.gov/800-63-3/sp800-63b.html).
105
+
Although the memo isn't specific on which policies to use with passwords, consider the standard from [NIST 800-63B](https://pages.nist.gov/800-63-3/sp800-63b.html).
0 commit comments