AADSTS90023: Couldn't get valid user code about azure-docs-cli HOT 8 CLOSED

I found that this was because our corp uses a Netskope client to route all traffic, and traffic not going through that client (i.e. if the client is disabled) would interfere with the ability to login to our SAML single sign-on process. The solution was to enable the Netskope client, and then the AZ login was able to succeed.

from azure-docs-cli.

@derekbekoe - This looks like an OAuth2 infrastructure error. Is there any indication of a bug somewhere or what can be done?

@yogevh - This is an older ticket. Can you still not log in, and if you can't, can you provide some more details about your account? Such as if you're using a different cloud than Azure Public, or have 2FA enabled.

from azure-docs-cli.

@yugangw-msft may be able to help?

from azure-docs-cli.

@yogevh are you using corporate @microsoft.com account?

from azure-docs-cli.

I ran into this error as well using an Azure Private cloud using the configuration for authenticating with active directory into a kubernetes cluster. I've followed the steps in Azure Active Directory plugin for client authentication. I'm authenticating with my corporate credentials for my company.

from azure-docs-cli.

@bganapa , assume Azure Private == Azure Stack, then I don't think device code has ever worked there. Can you clarify? As till last month, we were still prototyping for the support

from azure-docs-cli.

Azure Private cloud is the same as public cloud, but with private network and express route to your on prem network.

from azure-docs-cli.

Closing this issue - looks like it's resolved and also there has been a lack of activity.

from azure-docs-cli.