Forum Discussion
Intune iOS Jailbreak false positives (Resolved)
- May 07, 2021Got some additional information on this and it looks like its a client side detection bug and the issue should most likely be fixed by Monday. Until then its possible to give the policy a grace period or any turn off the detection etc, up to everyone to decide.
This might mean that there is good change of required update for the Company Portal app.
Hope this information helped.
We also saw this on a few devices starting Wednesday, May 5th. Un-enrolling and re-enrolling into Intune fixed the issue for us.
Microsoft has told us they have no idea why it's happening and have not heard of any other customers reporting this. Did you get any confirmation of how/when the bug was going to be fixed?
- Alo PressMay 08, 2021Iron Contributor
Hello JaimeH_TS
Thanks for replying!
Yeah, we luckily only had very few devices falsely reporting Jailbroken status and we also re-enrolled some of them where others reported Compliant after a Compliance check and a Sync. I can also confirm that the issues started around 4th of May (or at least our first detection), I would guess after some sort of update either on the server side or Intune app (4.16.0) even though it looks like the last change has been on the 30th of April, which could have led Jailbroken status pop up significantly sooner but who knows. It could also be related to some Apple security updates that were released on the 3rd of May.
I talked to a Support guy who was already familiar with the situation and the issue was being worked on. From what I could gather they actually had done a hotfix on the server side to avoid further false reporting and were actively working with the issue, hopefully getting it fixed by Monday. I would keep an eye on the App Store for updated client for "fixed" status but some of this is just guessing, since there is no notice in the Intune Service Health page.
As far as I could tell there is actually some sort of bug with a Jailbroken status detection but not sure if it was actually on Microsoft part or there was something funky with Apple, did not dig around too much after talking to support.
Hope this helps!