timetobail
My stack

Azure DevOps · Forced move · Tracked since October 13, 2026 · Sources checked Oct 13

Time to bail on Azure DevOps global personal access tokens?

Time to Bail · Boarding pass

FromAzure DevOps global personal access tokens
ToYour pick

Act. You can stay.

All global PATs stop working on December 1, 2026. Switch scripts to other tokens first.[1]

Act means: change a setting or plan before the date. You can stay.

Gate closes
Global PATs stop working
Time left
46days
Status
Act

Azure DevOps global personal access tokens stop December 1, 2026

Global personal access tokens (PATs) in Azure DevOps stop working on December 1, 2026. Scripts and tools that use them need a new kind of token or sign-in.

How it is winding down

  1. Dec 12, 2025AnnouncedDone
  2. Dec 1Global PATs stop workingNext

What to do before December 1

Tick steps as you go. Your progress stays in this browser.

  1. Find your global PATs

    In Azure DevOps, open Personal access tokens and look for tokens set to all organizations.

  2. Replace them

    Make a new token for one organization, or move the tool to Entra sign-in.

  3. Update pipelines and scripts

    Swap the token in CI, scripts and tools. Test each one before December 1.

Facts we checked

Facts and their sources
Global PATs stop workingDecember 1, 2026[1]
Can you still create them?Yes, until December 1, 2026; the earlier March 15, 2026 block was called off[1]
Azure DevOps ServerNot affected[1]
What to use insteadTokens for one Azure DevOps organization, or short-lived Entra-based sign-in[1]
AnnouncedDecember 12, 2025[1]
Scripts and tools with global PATsStop working on December 1, 2026[1]

Sources

Check it yourself. Every fact above links here.

  1. Retirement of Global Personal Access Tokens in Azure DevOps Microsoft · primary · checked Oct 13
Read the published editorial report

What changed

Time to bail on Azure DevOps global personal access tokens? Act. You can stay. All global PATs stop working on December 1, 2026. Switch scripts to other tokens first.

On our scale this is Act: change a setting or plan before the date. You can stay.

Global personal access tokens (PATs) in Azure DevOps stop working on December 1, 2026. Scripts and tools that use them need a new kind of token or sign-in.

Here are the facts we checked:

  • Global PATs stop working: December 1, 2026 (Microsoft)
  • Can you still create them?: Yes, until December 1, 2026; the earlier March 15, 2026 block was called off (Microsoft)
  • Azure DevOps Server: Not affected (Microsoft)
  • What to use instead: Tokens for one Azure DevOps organization, or short-lived Entra-based sign-in (Microsoft)
  • Announced: December 12, 2025 (Microsoft)
  • Scripts and tools with global PATs: Stop working on December 1, 2026 (Microsoft)

You can stay on Azure DevOps. You have to change a setting or plan before the date.

Leaving is a choice here, not a must.

Microsoft is the main source for this page. Azure DevOps has not said more than what is listed here. If a fact is not on this page, we do not know it yet.

Who is affected

Scripts and tools with global PATs: Stop working on December 1, 2026.

The date to remember is December 1, 2026. Make the change before then.

What to do before December 1

  1. Find your global PATs. In Azure DevOps, open Personal access tokens and look for tokens set to all organizations.
  2. Replace them. Make a new token for one organization, or move the tool to Entra sign-in.
  3. Update pipelines and scripts. Swap the token in CI, scripts and tools. Test each one before December 1.

A few tips:

  • Make the change yourself before the date. Do not wait for the last reminder email.
  • Write down your current plan or settings first, so you can compare after the change.
  • After the change, open your settings again and check that it worked.

How to tell your users

If the change affects your members or team, send one short email. Say what changes for them and when. Put the most important line first.

If there is a date, send a short reminder a few days before it. Keep a copy of the list you sent it to.

Options people mention

Listed for convenience. Not ranked. Not paid. These names come up in threads and reviews; that does not show where people moved.

Before you pay, check the price page of each tool yourself. Prices change, and we only list what our sources say.

Questions people ask

No questions collected yet.

Sources

Thanks.

Did this answer your question?

Run SaaS spend at work? Get these changes before the invoice

Arrivals · for builders

Building where they land?

People on Azure DevOps global personal access tokens can stay if they make the change. Some would rather leave. Get the playbook for this change, and list your product here.

Listing is free. An editor checks it. Not ranked. Not paid.

Open the playbookList your product