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/howto-mfa-reporting.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ This article shows you how to view the Azure AD sign-ins report in the Azure por
24
24
25
25
## View the Azure AD sign-ins report
26
26
27
-
The sign-ins report provides you with information about the usage of managed applications and user sign-in activities, which includes information about multi-factor authentication (MFA) usage. The MFA data gives you insights into how MFA is working in your organization. It lets you answer questions like the following:
27
+
The sign-ins report provides you with information about the usage of managed applications and user sign-in activities, which includes information about multi-factor authentication (MFA) usage. The MFA data gives you insights into how MFA is working in your organization. It answers questions like:
28
28
29
29
- Was the sign-in challenged with MFA?
30
30
- How did the user complete MFA?
@@ -59,7 +59,7 @@ This information allows admins to troubleshoot each step in a user’s sign-in,
59
59
- Volume of sign-ins protected by multi-factor authentication
60
60
- Usage and success rates for each authentication method
61
61
- Usage of passwordless authentication methods (such as Passwordless Phone Sign-in, FIDO2, and Windows Hello for Business)
62
-
- How frequently authentication requirements are satisfied by token claims (where users are not interactively prompted to enter a password, enter an SMS OTP, and so on)
62
+
- How frequently authentication requirements are satisfied by token claims (where users aren't interactively prompted to enter a password, enter an SMS OTP, and so on)
63
63
64
64
While viewing the sign-ins report, select the **Authentication Details** tab:
65
65
@@ -71,7 +71,7 @@ While viewing the sign-ins report, select the **Authentication Details** tab:
71
71
>[!IMPORTANT]
72
72
>The **Authentication details** tab can initially show incomplete or inaccurate data, until log information is fully aggregated. Known examples include:
73
73
>- A **satisfied by claim in the token** message is incorrectly displayed when sign-in events are initially logged.
74
-
>- The **Primary authentication** row is not initially logged.
74
+
>- The **Primary authentication** row isn't initially logged.
75
75
76
76
The following details are shown on the **Authentication Details** window for a sign-in event that show if the MFA request was satisfied or denied:
77
77
@@ -103,8 +103,8 @@ The following details are shown on the **Authentication Details** window for a s
103
103
* unable to send the mobile app notification to the device
104
104
* unable to send the mobile app notification
105
105
* user declined the authentication
106
-
* user did not respond to mobile app notification
107
-
* user does not have any verification methods registered
106
+
* user didn't respond to mobile app notification
107
+
* user doesn't have any verification methods registered
108
108
* user entered incorrect code
109
109
* user entered incorrect PIN
110
110
* user hung up the phone call without succeeding the authentication
@@ -117,13 +117,13 @@ The following details are shown on the **Authentication Details** window for a s
117
117
118
118
First, ensure that you have the [MSOnline V1 PowerShell module](/powershell/azure/active-directory/overview) installed.
119
119
120
-
Identify users who have registered for MFA using the PowerShell that follows. This set of commands excludes disabled users since these accounts cannot authenticate against Azure AD:
120
+
Identify users who have registered for MFA using the PowerShell that follows. This set of commands excludes disabled users since these accounts can't authenticate against Azure AD:
Identify users who have not registered for MFA using the PowerShell that follows. This set of commands excludes disabled users since these accounts cannot authenticate against Azure AD:
126
+
Identify users who aren't registered for MFA by running the following PowerShell commands. This set of commands excludes disabled users since these accounts can't authenticate against Azure AD:
0 commit comments