// troubleshooting guide · azure devops

Azure DevOps TF400813: The User Is Not Authorized to Access This Resource

Status
Ongoing
platforms:
Web, Visual Studio, integrations
updated:
November 16, 2026
reports:
4
Method
how we research
Share

RUNBOOK · azure-devops/tf400813-not-authorized4 FIXES

// quick answer

Azure DevOps doesn't recognize the account or token as having access. Check that the user is in the organization with a valid access level, signed into the right Entra tenant, and that the PAT has the needed scopes.

Most likely fix: Check membership and access level

How to fix it

// try these in order, the most common fix is first

  1. FIX 1Check membership and access level

    1. 01Organization settings > Users
    2. 02Make sure the account is listed with Basic or Stakeholder access
    3. 03Add it to the right project group
    Did this fix it?
  2. FIX 2Check the tenant

    1. 01Organization settings > Microsoft Entra to see the connected directory
    2. 02Sign in with an account from that tenant
    Did this fix it?
  3. FIX 3Fix tokens and app access

    1. 01Create a new PAT with the required scopes
    2. 02Organization settings > Policies > enable 'Third-party application access via OAuth' if the integration needs it
    3. 03Reconnect the integration
    Did this fix it?
  4. FIX 4Clear the cached session

    1. 01Sign out and back in, or restart the client (Visual Studio, SSMS)
    2. 02Clear cached credentials for dev.azure.com
    Did this fix it?

Symptoms

Visual Studio, a third-party integration (Zapier, Logic Apps, Fivetran) or the CLI fails with 'TF400813: The user ... is not authorized to access this resource'.

Why it happens

  • C-01The account isn't a member of the organization or has no access level
  • C-02The organization is connected to a different Entra ID tenant
  • C-03The PAT lacks scopes or expired
  • C-04Third-party OAuth access is disabled in organization policies
  • C-05A stale cached session in the client

// this guide also covers

  • tf400813 the user is not authorized to access this resource
  • azure devops not authorized
  • azure devops 401 unauthorized

Still not working?

If Azure DevOps keeps failing, you're not alone. See every Azure DevOps problem users report or the alternatives people switch to.

Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.

Talk to us

Watch Azure DevOps Get an email when its price changes, it has an outage, or we publish a new fix. No spam.

Fixed it? Share this guide

Other Azure DevOps errors

All 12 Azure DevOps errors and fixes →