MSamWils

@gladjohn , thanks for testing it. Can you please enable MSALRuntime log for this issue? Exception: Microsoft.Identity.Client.NativeInterop.MsalRuntimeException: Status: Unexpected Context: Caught exception Tag: 0x2039c1cd And also please collect fiddler trace...

Hi @myokeeh, it's by design that the WAM windows (the bottom screenshot) stays open even the underlayer application got terminated. It's because that WAM windows is running in a different...

Hi @myokeeh , the WAM UX should be parented to the application where user won't be able to interact with unless the WAM dialog is resolved. If user can interact...

Hi @Camios, Apologize for the inconvenience. Unfortunately, "run as" is not supported in the broker flow. It's not related to MSAL but the issue is on the windows operating system...

Hi @Camios, can you please help explain in detail on your scenario why using "run as" is required? We would like to understand about the scenario better in order to...

Hi @common-tasks , the broker path required windows OS inbox apps to run which has dependency on the explorer.exe. Is your scenario running in the remote session like Azure Virtual...

Hi @common-tasks, in order to exercise the broker flow on windows, it required the explorer.exe to be activated. If the explorer.exe didn't get started due to any reason, calling WAM...