Forum Discussion

Iron Contributor

Aug 27, 2021

Incorrect compliancy issue

We sometme have an issue with users where the signin logs show that they have in incompliant device which causing issue with logging in applications because of the conditional access policies. Wh...

MVP

Aug 27, 2021

RonaldvdMeer

Hi,

Did you check it out on the device itself in the company portal app?

ANd did you expand the compliance settings in the device in Intune to be 100% sure its not blocking. SOmetimes it looks green... but when opening the device properties and clicking on device compliance and clicking on each policy to unfold it. It could show you some more information

And maybe this blog helps you to get a good understanding about compliant devices and ca
https://call4cloud.nl/2021/08/the-death-of-compliance/

RonaldvdMeer

Iron Contributor

Aug 27, 2021

Another observation had that the signin log of one particular user showed that if he used Chrome as browser Compliant and Managed stated Yes. When using Edge (chromium based) Compliant en Managed stated No.

Rudy_Ooms_MVP
MVP
Aug 27, 2021
When using chrome normally you would need the account extension to pass/report the compliance status/prt otherwise they report as non compliant. Does chrome has the account extension active, as it is compliant etc?
- RonaldvdMeer
  Iron Contributor
  Aug 27, 2021
  Yes it has the extension. But that doesn't explain to me why Chrome shows compliant and Edge doesn't
  - Rudy_Ooms_MVP
    MVP
    Aug 27, 2021
    To be sure... is edge logged in with the same azure ad account?
    
    The explanation behind it
    
    Microsoft Edge has native support for PRT-based SSO, and you don't need an extension. On Windows 10 RS3 and above, if a user is signed into their browser profile, they will get SSO with the PRT mechanism to websites that support PRT-based SSO.