Skip to content

Commit 014f1d3

Browse files
authored
Merge pull request #613 from MicrosoftDocs/dougeby-patch-1
Fixed minor issue
2 parents 576d60f + 6d71bc5 commit 014f1d3

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

memdocs/intune/protect/compliance-policy-monitor.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -107,7 +107,7 @@ That action opens the **Device compliance** window, and displays devices in a **
107107
If you want to see all the devices owned by a specific user, you can also filter the chart report by typing the user's e-mail.
108108

109109
> [!TIP]
110-
> If no user is signed in the device, the device with the targeted device compliance policy will send a compliance report back to Intune showing up the **System Account** as the user principal name. This happens because a device compliance policy was targeted to either a group of users or devices, and no user was signed into the device at the time the compliance policy was evaluated.
110+
> If no user is signed in to the device, the device with the targeted device compliance policy will send a compliance report back to Intune showing **System Account** as the user principal name. This happens because a device compliance policy was targeted to either a group of users or devices, and no user was signed into the device at the time the compliance policy was evaluated.
111111
>
112112
> Additionally, if there are multiple users signed into the same device, and coincidentally the device is targeted with a compliance policy that is scoped to cover all users that are currently signed in the device, the compliance report might show the same device multiple times as every user signed into the device has to evaluate the device compliance policy and report it back to Intune.
113113

0 commit comments

Comments
 (0)