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/authentication/concept-system-preferred-multifactor-authentication.md
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Learn how to use system-preferred multifactor authentication
4
4
ms.service: active-directory
5
5
ms.subservice: authentication
6
6
ms.topic: conceptual
7
-
ms.date: 03/02/2023
7
+
ms.date: 03/16/2023
8
8
ms.author: justinha
9
9
author: justinha
10
10
manager: amycolannino
@@ -24,6 +24,9 @@ System-preferred MFA is a Microsoft managed setting, which is a [tristate policy
24
24
25
25
After system-preferred MFA is enabled, the authentication system does all the work. Users don't need to set any authentication method as their default because the system always determines and presents the most secure method they registered.
26
26
27
+
>[!NOTE]
28
+
>System-preferred MFA is a key security upgrade to traditional second factor notifications. We highly recommend enabling system-preferred MFA in the near term for improved sign-in security.
29
+
27
30
## Enable system-preferred MFA
28
31
29
32
To enable system-preferred MFA in advance, you need to choose a single target group for the schema configuration, as shown in the [Request](#request) example.
The following example excludes a sample target group and includes all users. For more information, see [Update authenticationMethodsPolicy](/graph/api/authenticationmethodspolicy-update?view=graph-rest-beta).
64
+
The following example excludes a sample target group and includes all users. For more information, see [Update authenticationMethodsPolicy](/graph/api/authenticationmethodspolicy-update).
@@ -106,21 +106,21 @@ When you install the extension, you need the *Tenant ID* and admin credentials f
106
106
107
107
The NPS server must be able to communicate with the following URLs over TCP port 443:
108
108
109
-
**https:\//strongauthenticationservice.auth.microsoft.com* (for Azure Public cloud customers).
110
-
**https:\//strongauthenticationservice.auth.microsoft.us* (for Azure Government customers).
111
-
**https:\//strongauthenticationservice.auth.microsoft.cn* (for Azure China 21Vianet customers).
112
-
**https:\//adnotifications.windowsazure.com*
113
-
**https:\//login.microsoftonline.com*
114
-
**https:\//credentials.azure.com*
109
+
*`https:\//strongauthenticationservice.auth.microsoft.com` (for Azure Public cloud customers).
110
+
*`https:\//strongauthenticationservice.auth.microsoft.us` (for Azure Government customers).
111
+
*`https:\//strongauthenticationservice.auth.microsoft.cn` (for Azure China 21Vianet customers).
112
+
*`https:\//adnotifications.windowsazure.com`
113
+
*`https:\//login.microsoftonline.com`
114
+
*`https:\//credentials.azure.com`
115
115
116
116
Additionally, connectivity to the following URLs is required to complete the [setup of the adapter using the provided PowerShell script](#run-the-powershell-script):
0 commit comments