Skip to content

Commit d01c0b5

Browse files
authored
Merge pull request #98825 from MicrosoftGuyJFlo/SecurityDefaultsClarification
[Azure AD] Fundamentals - Security defaults method clarification
2 parents e25642f + b12b1b3 commit d01c0b5

File tree

1 file changed

+14
-0
lines changed

1 file changed

+14
-0
lines changed

articles/active-directory/fundamentals/concept-fundamentals-security-defaults.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -90,6 +90,20 @@ If the user isn't registered for Multi-Factor Authentication, the user will be r
9090

9191
The following additional considerations are related to deployment of security defaults for your tenant.
9292

93+
### Authentication methods
94+
95+
Security defaults allow registration and use of Azure Multi-Factor Authentication **using only the Microsoft Authenticator app using notifications**. Conditional Access allows the use of any authentication method the administrator chooses to enable.
96+
97+
| | Security defaults | Conditional Access |
98+
| --- | --- | --- |
99+
| Notification through mobile app | X | X |
100+
| Verification code from mobile app or hardware token | | X |
101+
| Text message to phone | | X |
102+
| Call to phone | | X |
103+
| App passwords | | X** |
104+
105+
** App passwords are only available in per-user MFA with legacy authentication scenarios only if enabled by administrators.
106+
93107
### Older protocols
94108

95109
Mail clients use older authentication protocols (like IMAP, SMTP, and POP3) to make authentication requests. These protocols don't support Multi-Factor Authentication. Most of the account compromises that Microsoft sees are from attacks against older protocols that are trying to bypass Multi-Factor Authentication.

0 commit comments

Comments
 (0)