web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / Power Apps failing Sig...
Power Apps
Unanswered

Power Apps failing Sign-in on Kiosk Android Device

(0) ShareShare
ReportReport
Posted on by
Hi all,

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.

Issue

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.

Request

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!

I have the same question (0)
  • WarrenBelz Profile Picture
    153,731 Most Valuable Professional on at
    Some research suggests that when Power Apps asks the user to sign in, it opens an embedded WebView instead of using a brokered authentication flow. That WebView shows up as Chrome Mobile because it’s based on Chromium components from Google. Since the session isn’t brokered, Conditional Access can’t verify the device’s compliance or link it to a registered device record, so it flags the sign-in as non-compliant and blocks it.
     
    In Fully Managed mode, though, sign-in works because brokered authentication is supported, letting apps like Company Portal or Authenticator pass valid device compliance details to Microsoft, which satisfies Conditional Access.
     
    Please Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider answering Yes to Was this reply helpful? or give it a Like
    Visit my blog
    Practical Power Apps    LinkedIn  

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Leaderboard > Power Apps

#1
Kalathiya Profile Picture

Kalathiya 301 Super User 2026 Season 1

#2
WarrenBelz Profile Picture

WarrenBelz 297 Most Valuable Professional

#3
VASANTH KUMAR BALMADI Profile Picture

VASANTH KUMAR BALMADI 195

Last 30 days Overall leaderboard