
Announcements
I’ve been trialling Android Kiosk Enrollment profiles for several projects, all of which have worked successfully using apps like Tulip, KT Pulse, etc.
I now have a new project that requires a device to be enrolled using a Kiosk Enrollment Profile, with Microsoft Power Apps set as the single allowed application.
When Power Apps attempts to authenticate the user, the sign‑in fails.
In Azure AD sign‑in logs, the attempt appears as Chrome Mobile, but after further investigation it looks like Power Apps relies on a WebView for authentication. Because Intune cannot properly detect or validate this WebView session, the Conditional Access policy treats the device as non‑compliant, resulting in a failed sign‑in.
To validate the behaviour, I tested the same device using the less restrictive Corporate-Owned, Fully Managed enrollment profile. In this mode, Power Apps authenticates successfully with no issues.
Has anyone encountered this before or know why Power Apps authentication might fail specifically under a Kiosk Enrollment Profile? Any guidance or recommendations would be greatly appreciated.
Thanks in advance!