Skip to main content
The Azure DevOps credential type stores the Personal Access Token and configuration associated with the Azure DevOps Organization(s) from which you’re migrating data with Warp. To configure an Azure DevOps credential, you’ll need:
  • A Personal Access Token (Global or Single Organization),
  • Your Organization Slug (if you’re not using a Global token), and
  • The number of days until your token expires (from the day of issue)

​
Configuration

Search for the 🛠️ emoji if you’d like to skim through this content while focusing on the steps you need to follow.

​
Get the Organization Slug

🛠️ Sign in to Azure DevOps and navigate to the page for the organization containing the projects whose repositories you want to migrate:
The organization page in Azure DevOps. The "Projects" tab is on display, and it contains 3 projects: "Parts Unlimited," "Tailwind Traders," and "First Project."

The organization page in Azure DevOps.

The example Azure DevOps organization for this quickstart is joey-ado-testing.
Make a note of the URL in your browser’s address bar. The URL contains the organization slug, which is the part of the URL that uniquely identifies the organization. It’s the part of the URL after dev.azure.com/:
Close-up of the browser's address bar, which displays the URL "dev.azure.com/joey-ado-testing".

The browser's address bar, while on the organization page in Azure Devops.

In this example, the URL for the organization’s page is:
The organization slug is the part that comes after dev.azure.com/, which means that this example’s organization slug is:
🛠️ Copy the organization slug from your browser’s address bar and paste it someplace safe — you’ll use it when you create the vault file.

​
Generate a Personal Access Token for Your Organization

It’s time to get a Personal Access Token. 🛠️ Near the top right corner of the page, you’ll see the (User Settings) icon. Click it to reveal its menu:
The menu that appears when you click the User Settings icon. The key item in the menu is the "Personal access tokens" item.

The menu that appears when you click the User Settings icon.

🛠️ Select Personal access tokens from the menu. You will see the Personal Access Tokens page:
The Personal Access Tokens page. It is empty and displays the text "You do not have any personal access tokens yet." There are two identical "New Token" buttons on the page; one near the top right corner, and one in the middle.

The Personal Access Tokens page.

🛠️ Click any of the New Token buttons on the page. A panel will appear, prompting you to create a new personal access token:
The "Create a new personal access token" panel, which is a form. The "Name" field contains "Warp migration 1", the "Organization" field contains "joey-ado-testing", the "Expiration (UTC)" field contains "30 days" and the selected "Scopes" radio button is "Full access".

The Create a new personal access token panel.

🛠️ In the Name field, enter a name for the token. To make it easier to identify, we suggest you include “Warp” in the name. 🛠️ Under Scopes, change the option to Full access.
For the purposes of this Quickstart, we’ll leave the Expiration field at the default value of 30 days.
🛠️ Click the Create button. You should now see the Success! panel, which will display the personal access token you just created:
The "Success!" panel, which is a form. There is a text field containing the Personal Access Token. There are instructions to copy the token now because Azure DevOps does not store it and the user will never be able to access its value again.

The Success! panel.

🛠️ Copy the token and save it in a safe place — preferably a password manager.
This will be the only time that this Personal Access Token will be presented to you.Make sure you’ve copied it someplace safe before clicking the Close button!
🛠️ Click the Close button. When you close the Success! panel, you will be taken back to the Personal Access Tokens page. You will see the personal access token you just created listed there:
The Personal Access Tokens page, with the newly-created Personal Access Token. The page now has a list, containing one token: "Warp migration 1", the token that was created just now.

The Personal Access Tokens page, with the newly-created Personal Access Token.