Forum Discussion
App Access Blocked: Your Organization requires confirmation that you are clocked in
Thats indeed very odd... as stated before it looks very much like app protection policies applying.. But (until now?) it never mentioned the "clocked" part... did you already opened a support ticket ?
Could you let us know if it fixes the issue when you decide to disable/remove the mam policies?
I know there is something wrong with app protection and teams .. maybe they are trying to fix that... and creating a new issue?
Hello Rudy_Ooms_MVP,
When I am checking the App protection status logs(Under Troubleshooting + support) during login process into iOS(outlook app), It's showing checked-in successfully.
But issue remains the same, outlook app access blocked with same error message.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Error message: App Access Blocked: To Access your data associated with Account Email address removed, your Organization requires confirmation that you are clocked in. We are unable to verify this. Please try again later or Contact your Admin.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Attaching screenshot for your reference.
Regards,
- Feb 14, 2022Okay so app protection works.. and the device could check in...it's such a strange error/warning as it is mentioning clocked in instead of checked in 🙂
- admin1735Feb 14, 2022Copper ContributorNo Idea! 🙂
There might be some communication delay between Mobile device and Intune platform while Device is syncing with intune to update app protection policy.
If possible, Can you pls assist me to capture the device logs?
Regards.- Dana_RamosFeb 15, 2022Copper Contributorhttps://docs.microsoft.com/en-us/mem/intune/apps/app-protection-policy-settings-log
Uses Edge mobile app.
- Dana_RamosFeb 15, 2022Copper ContributorAh you're probably right. That's more likely a typo than an access requirement. Threw me bc I had just talked about Shifts, Approvals, Bulletins in Teams with the org before this happened. I also think there was some kind of lag in the policy retrieval. It started working fine on my Android phone on Sunday. The iPhone users were still having issues as of yesterday. They may be today as well and I just haven't heard from them yet.