This is an interesting issue indeed, we never tested it with AzureAdLogins and you are the first one to bring it up. The strange part here is that we do not use any specific mechanisms to enter the session except for native Windows ones and thus it is really strange to see those errors. As I understood you are also able to log in normally via physically entering the same credentials?