// troubleshooting guide · azure devops
Azure DevOps Global PAT Retirement: What Breaks and How to Fix It
- Status
- Ongoing
- platforms:
- Azure DevOps Services (not Azure DevOps Server)
- updated:
- November 16, 2026
- reports:
- 3
- Method
- how we research
RUNBOOK · azure-devops/global-pat-retirement3 FIXES
// quick answer
PATs scoped to 'All accessible organizations' stop working on January 27, 2027 (postponed from December 1, 2026). Find them in User settings and replace them with organization-scoped PATs or Microsoft Entra tokens.
Most likely fix: Find your global PATs
How to fix it
// try these in order, the most common fix is first
FIX 1Find your global PATs
- 01User settings > Personal access tokens
- 02Filter Access scope to 'All accessible organizations' and Status to Active
- 03List every script or service that uses them
Did this fix it?FIX 2Replace with organization-scoped PATs
- 01Create one PAT per organization with only the scopes needed
- 02Update each script or secret store
- 03Revoke the old global PAT
Did this fix it?FIX 3Move to Microsoft Entra tokens
- 01Use Entra-based, short-lived authentication (service principals or managed identities) as Microsoft recommends
- 02Admins can enforce a maximum PAT lifespan under Organization settings > Microsoft Entra > Policies
Did this fix it?
Symptoms
Scripts, CLIs or tools that use one token for several organizations start failing with 401 errors once global PATs are decommissioned.
Why it happens
- C-01Microsoft is retiring global personal access tokens on Azure DevOps Services
- C-02Automation built on a single token across organizations
// this guide also covers
- azure devops global pat retirement
- azure devops pat all accessible organizations
- azure devops pat deprecated
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 usOther Azure DevOps errors
- Azure DevOps No Hosted Parallelism Has Been Purchased or Granted
- Azure DevOps Pipeline Stuck in Queue (Waiting for an Available Agent)
- Azure DevOps Pipeline Not Triggering on Push
- Azure DevOps Git Authentication Failed (PAT Not Working)
- Azure DevOps TF401027: You Need the Git 'GenericContribute' Permission
- Azure Pipelines Job Canceled After 60 Minutes
- Azure Artifacts Feed 401 Unauthorized (Unable to Load the Service Index)
- Azure DevOps Service Connection 'Failed to Obtain the JSON Web Token'