How to create an Azure DevOps personal access token
Updated 13 October 2026 · 2 min read
Tools that read from Azure DevOps on your behalf sign in with a personal access token (PAT) instead of your password. Give each tool its own token with only the access it needs.
What a personal access token is
A personal access token is a password for software. It belongs to you, works for one organization (or all of yours), has an expiry date, and is limited to the scopes you choose — for example read access to work items and nothing else.
Create the token
- Sign in to your organization at
https://dev.azure.com/your-organization. - Open User settings (the icon next to your profile picture, top right) and choose Personal access tokens.
- Click New Token.
- Give it a name, for example IssueRadar – MacBook, pick the organization and an expiration date.
- Under Scopes, choose Custom defined and tick only what the tool needs (see below). Click Show all scopes if a scope isn’t listed.
- Click Create and copy the token. Azure DevOps shows it only once.
Which scopes to choose
Pick the smallest set that works. For a tool that only reads work items — such as IssueRadar — that is:
- Work Items: Read — to search and read work items, their types and states, and area and iteration paths.
- Project and Team: Read — to list the projects in the organization.
Avoid Full access. A read-only token can’t change anything, even if it ends up in the wrong place.
Test it
From Terminal, list the projects the token can see (the username stays empty, the token is the password):
curl -u :YOUR_TOKEN \\n "https://dev.azure.com/your-organization/_apis/projects?api-version=7.1"A JSON list of projects means the token and the Project and Team scope work.
Renew it before it expires
Personal access tokens always expire. Azure DevOps emails you shortly before, and on the Personal access tokens page you can edit a token to extend it or regenerate it to get a new value. After regenerating, paste the new value into every tool that used the old one — in IssueRadar under Settings → Connections, Edit….
Questions and answers
Why can’t I create a token, or choose a longer expiry?
Organization administrators can restrict personal access tokens — for example their maximum lifetime or who may create them. Ask your Azure DevOps administrator.
Should the token cover all my organizations?
Only if the tool needs that. A token for a single organization is the safer default; create one per organization you add.
Does this work with Azure DevOps Server?
Azure DevOps Server has personal access tokens too, created the same way in its web interface. IssueRadar itself only supports Azure DevOps Services at dev.azure.com.