unauthorized_client

Question

unauthorized_client: The client does not exist or is not enabled for consumers. If you are the application developer, configure a new application through the App Registrations in the Azure Portal at https://go.microsoft.com/fwlink/?linkid=2083908.

I am not a developer and don’t have a work or study email.

Answer 1

Hello JodieSummers-1541 •,

It looks like you’re running into an Azure AD/OAuth error that basically means the application you’re trying to sign into either isn’t registered in Azure AD or is only configured for work/school accounts—not personal Microsoft accounts. Since you don’t have a work or school email, your MSA (personal account) is being rejected as “unauthorized_client.”

Here are a couple of paths you can take:

Sign up for a free Azure AD–backed account

• Create a free Azure Account with a personal Microsoft account (Outlook.com, Hotmail.com, etc.).
  • When you go through the Azure sign-up flow, it will automatically register you in a new Azure AD tenant.
    • You’ll end up with an Azure AD “home” directory that trusts your MSA, so this error goes away.
    Register a new Azure AD application that allows personal MSAs If you ever need to use a custom app (CLI, script, web app, etc.), you’d:

    - Go to the Azure Portal > Azure Active Directory > App Registrations > New Registration
    
       - Under “Supported account types,” pick “Accounts in any organizational directory and personal Microsoft accounts”
    
          - Use that app’s client ID/redirect URI in your calls—now personal MSAs can sign in.
    
          Invite your personal account as a guest into an existing Azure AD tenant If you have access to any work/school tenant, an admin can add your MSA as a B2B guest. Once accepted, you can sign in via that tenant and avoid the unauthorized_client error.
    

Next steps for you: • Let us know which Azure service or app you’re actually trying to access (Portal? CLI? DevOps? REST API?) • Confirm whether you already have any Azure AD tenant (even a free trial) • Share the exact sign-in flow or command you’re using

With that info we can tailor the guidance.

Reference docs: • Troubleshoot unauthorized_client for VMs (similar OAuth errors): https://learn.microsoft.com/azure/virtual-machines/troubleshoot-rdp-connection#unauthorized_client • OAuth 2.0 authentication for Azure DevOps REST APIs (account types, scopes): https://learn.microsoft.com/azure/devops/integrate/get-started/authentication/oauth • Troubleshoot connection/authentication errors in Azure DevOps: https://learn.microsoft.com/azure/devops/user-guide/troubleshoot-connection#troubleshoot-authentication-errors