Skip to content

Commit a2566c5

Browse files
Update memdocs/intune/protect/device-compliance-get-started.md
Co-authored-by: JohanFreelancer9 <[email protected]>
1 parent 3f4a9e6 commit a2566c5

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

memdocs/intune/protect/device-compliance-get-started.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -173,7 +173,7 @@ The following table describes how noncompliant settings are managed when a compl
173173

174174

175175
> [!NOTE]
176-
> The Company Portal enters the enrollment remediation flow when the user logs into CP and the device has not successfully checked in with Intune in 30+ days (or the device is noncompliant due to a "Lost contact" compliance reason). In this flow, we attempt to initiate a checkin one more time. If that still does not succeed, then we issue a retire command to allow the user to re-enroll the device manually.
176+
> The Company Portal app enters the enrollment remediation flow when the user signs into the app and the device has not successfully checked in with Intune for 30 days or more (or the device is non-compliant due to a _Lost contact_ compliance reason). In this flow, we attempt to initiate a check-in one more time. If that still does not succeed, we issue a retire command to allow the user to re-enroll the device manually.
177177
178178
---------------------------
179179

0 commit comments

Comments
 (0)