Gladwin Johnson

@ashok672 can you please let us know once PCA changes are in? I can re-test the CCA after

**On a Windows Server 2016 machine, we see the follow error when invoking the new broker** ``` Exception: Microsoft.Identity.Client.NativeInterop.MsalRuntimeException: Status: Unexpected Context: Caught exception Tag: 0x2039c1cd ``` And subsequent calls...

@MSamWils shared all the info on chat. please let me know if you need more details

Adding notes so we know what works and what doesn't with WAM on Server 2016. | Authority | MSA-PT | ATS | ATI | |------------ |------ |---- |------------------------------------------- | |...

**Some more notes based on investigation :** - When you pass login hint then we bypass the accounts control logic and UI is then shown without the double prompt being...

@MSamWils please let me know what information you need to debug this

@localden this is what we show in the scenario you mentioned above, {"WAM Error \n Error Code: 3399614473 \n Error Message: ApiContractViolation \n WAM Error Message: (pii) \n Internal Error...

@localden checking on this one

that is thrown by MSALRuntime. We can discuss on how to best fix this

> @gladjohn I think in my case it was cut-off (see scroll bar). Things like `WAM Error Message: (pii)` should likely be updated to something more descriptive. > > Where...