Skip to content

Commit 4a06317

Browse files
committed
acrolinx fixes
1 parent f0338b1 commit 4a06317

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

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

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ This article shows you how to view the Azure AD sign-ins report in the Azure por
2424

2525
## View the Azure AD sign-ins report
2626

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:
2828

2929
- Was the sign-in challenged with MFA?
3030
- How did the user complete MFA?
@@ -59,7 +59,7 @@ This information allows admins to troubleshoot each step in a user’s sign-in,
5959
- Volume of sign-ins protected by multi-factor authentication
6060
- Usage and success rates for each authentication method
6161
- 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)
6363

6464
While viewing the sign-ins report, select the **Authentication Details** tab:
6565

@@ -71,7 +71,7 @@ While viewing the sign-ins report, select the **Authentication Details** tab:
7171
>[!IMPORTANT]
7272
>The **Authentication details** tab can initially show incomplete or inaccurate data, until log information is fully aggregated. Known examples include:
7373
>- 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.
7575
7676
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:
7777

@@ -103,8 +103,8 @@ The following details are shown on the **Authentication Details** window for a s
103103
* unable to send the mobile app notification to the device
104104
* unable to send the mobile app notification
105105
* 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
108108
* user entered incorrect code
109109
* user entered incorrect PIN
110110
* 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
117117

118118
First, ensure that you have the [MSOnline V1 PowerShell module](/powershell/azure/active-directory/overview) installed.
119119

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:
121121

122122
```powershell
123123
Get-MsolUser -All | Where-Object {$_.StrongAuthenticationMethods -ne $null -and $_.BlockCredential -eq $False} | Select-Object -Property UserPrincipalName
124124
```
125125

126-
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:
127127

128128
```powershell
129129
Get-MsolUser -All | Where-Object {$_.StrongAuthenticationMethods.Count -eq 0 -and $_.BlockCredential -eq $False} | Select-Object -Property UserPrincipalName

0 commit comments

Comments
 (0)