Replies: 3 comments
|
Hello, Try enable WAM in Settings and then use PowerShell 7. That should fix this. Cheers! |
0 replies
|
Hello, I'm just following up on this. Did you get it to work with WAM and PowerShell 7? I updated the Development branch and added support for System Browser login. You can download and try that as well. You need to enable this in Settings and restart it. Cheers! |
0 replies
|
Yes it did thanks.
Thank you,
Kevin Lordemann
Endpoint Administrator
R. D. Offutt Company
Cell - 701-212-5623
Service Desk - 701-239-8790 | Cisco - 118790 | ***@***.******@***.***>
Direct 701-551-5432 | Cisco - 125432 | ***@***.******@***.***>
…________________________________
From: Mikael Karlsson ***@***.***>
Sent: Friday, August 14, 2026 6:59 AM
To: Micke-K/IntuneManagement ***@***.***>
Cc: Lordemann, Kevin ***@***.***>; Author ***@***.***>
Subject: Re: [Micke-K/IntuneManagement] Allow system browser / Edge authentication instead of embedded login (Discussion #425)
CAUTION: This email originated from outside of R.D. Offutt Company. Do not click links, open attachments, or respond unless you recognize the sender and know the content is safe.
Hello,
I'm just following up on this. Did you get it to work with WAM and PowerShell 7?
I updated the Development<https://github.com/Micke-K/IntuneManagement/tree/Development> branch and added support for System Browser login. You can download and try that as well.
You need to enable this in Settings and restart it.
Cheers!
—
Reply to this email directly, view it on GitHub<#425?email_source=notifications&email_token=AUS3UZYIVQOAM3FXR2R66XL5J35JNA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBQGE3DQOBWUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-18016886>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AUS3UZ3B7KT4I2LBV5OXZOT5J35JNAVCNFSNUABIKJSXA33TNF2G64TZHMYTSMJQHAYDIOBXHNCGS43DOVZXG2LPNY5TCMBTGUZTGOBQUF3AE>.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS<https://github.com/notifications/mobile/ios/AUS3UZY7WG4WXN26U3UDI335J35JNA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBQGE3DQOBWUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVJTG633UMVZF62LPOM> and Android<https://github.com/notifications/mobile/android/AUS3UZ76CNSWRHMEGZHGQS35J35JNA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBQGE3DQOBWUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVZTG633UMVZF6YLOMRZG62LE>. Download it today!
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
We’re running into an issue with the current authentication experience using the embedded browser control.
In our environment (Intune + Conditional Access + MFA), the login window inside the app is being treated as an unsupported or outdated browser. We consistently see the “Update your browser / unsupported browser” message and are unable to complete authentication.
This seems to be caused by the embedded web view being used for MSAL authentication rather than the system browser.
What would help
It would be really helpful to have an option to choose how authentication is handled:
Option to use system browser (Edge/default browser) instead of embedded
Or enforce WithUseEmbeddedWebView($false) for MSAL
Ideally configurable in settings (e.g., checkbox like “Use system browser for authentication”)
Why this matters
Many enterprise environments now enforce:
Conditional Access policies
Modern authentication requirements
Browser compliance checks
These often block or degrade embedded browser sign-in flows, even when the device is compliant.
Using the system browser (Edge) or WAM aligns with how Microsoft tools handle authentication today and avoids these issues.
Current workaround attempts
We tried modifying the MSAL code to force system browser usage, but due to the UI relying on embedded auth, it breaks or fails to launch properly. So this would need to be handled internally by the tool.
All reactions