Edit

Connect to Azure Artifacts feeds (NuGet.exe)

  • Article
  • 2 minutes to read

Azure DevOps Services | Azure DevOps Server 2022 - Azure DevOps Server 2019 | TFS 2018

Project setup

  1. Select Artifacts and then select your feed.

  2. Select Connect to feed.

    Screenshot showing the connect to feed button

  3. Select NuGet.exe from the left panel.

  4. If this is your first time using Azure Artifacts with NuGet.exe, select Get the tools in the top-right corner and follow the instructions to download and install NuGet and Azure Artifacts Credential Provider.

  5. Follow the instructions in the Project setup to set up your nuget.config file.

    Screenshot showing how to set up your project's config file

  1. Select Build and Release > Packages.

  2. Select your feed from the dropdown menu.

  3. Select Connect to feed.

    Screenshot showing the connect to feed button in TFS

  4. Select NuGet from the left panel.

  5. If this is your first time using Azure Artifacts with NuGet, select the link under Get the tools to download and install NuGet and the Credential Provider.

  6. Run the command highlighted in step number two to add your feed URL to your nuget.config file.

    Screenshot showing how to push your package using NuGet.exe in TFS

  7. Run the command highlighted in step number three if you want to publish your NuGet package.

Note

Azure Artifacts Credential Provider is supported with NuGet 4.8.2 or later. See Azure Artifacts Credential Provider for more information.

Legacy project setup (NuGet v2)

  1. Select Artifacts and then select your feed.

  2. Select Connect to feed.

    Screenshot showing the connect to feed button

  3. Select NuGet.exe from the left panel.

  4. Copy your source URL, and then replace /v3/index.json with /v2.

    Screenshot showing the source URL

  5. Create a Personal Access Token. Scope your PAT to the organization(s) you want to access and to one of the following scopes: Packaging (read), Packaging (read and write), or Packaging (read, write, and manage).

  6. Run the following command in an elevated command prompt window to add your package source:

    nuget sources add -name <Feed_Name> -source <Feed_URL> -username <Any_String_But_Not_Null> -password <Personal_Access_Token>

  7. If your organization is connected to Azure Active Directory, you must first authenticate with your AD credentials and then add your personal access token using the setapikey command:

    nuget sources add -name <Feed_Name> -source <Feed_URL> -username <Azure_Active_Directory_UserName> -password <Azure_Active_Directory_Password>

nuget setapikey <Personal_Access_Token> -source <Feed_URL>

Legacy project setup (NuGet v2)

  1. Select Build and Release > Packages.

  2. Select your feed from the dropdown menu.

  3. Select Connect to feed.

    Screenshot of the connect to feed button in TFS

  4. Select NuGet and then copy your source URL. Replace /v3/index.json with /v2.

    Screenshot showing how to get the source URL

  5. Create a Personal Access Token. Scope your PAT to the organization(s) you want to access and to one of the following scopes: Packaging (read), Packaging (read and write), or Packaging (read, write, and manage).

  6. Run the following command in an elevated command prompt window to add your package source:

    nuget sources add -name <Feed_Name> -source <Feed_URL> -username <Any_String_But_Not_Null> -password <Personal_Access_Token>

  7. If your organization is connected to Azure Active Directory, you must first authenticate with your AD credentials and then add your personal access token using the setapikey command:

    nuget sources add -name <Feed_Name> -source <Feed_URL> -username <Azure_Active_Directory_UserName> -password <Azure_Active_Directory_Password>

nuget setapikey <Personal_Access_Token> -source <Feed_URL>