nuget-exe.md

title	description	ms.assetid	ms.technology	ms.topic	ms.date	monikerRange
Use NuGet with Azure DevOps Services feeds	Authenticating to feeds with NuGet in Azure DevOps Services	10665DBC-846E-4192-8CAB-D5A4C6E40C65	devops-artifacts	conceptual	03/24/2020	>= tfs-2018

Use NuGet with Azure DevOps Services feeds

Azure DevOps Services

[!INCLUDE nuget-recommended-version]

Add a feed to NuGet 4.8.2 or later

NuGet 4.8.2 and later supports the Azure Artifacts Credential Provider, which automatically acquires feed credentials when needed. For more information on using credential providers with NuGet, see Creating a NuGet credential provider.

1. Navigate to your feed (or create a feed if you haven't).

2. Select Connect to feed:

::: moniker range=">= azure-devops-2019"

[!div class="mx-imgBorder"]

3. Select NuGet.exe under the NuGet header

4. Select Get the tools in the top-right corner

5. Follow steps 1 and 2 to download the latest NuGet version and the credential provider.

6. Follow the instructions in the Project setup, Restore packages, and Publish packages sections to publish.

   [!div class="mx-imgBorder"]

   [!NOTE] You can also paste the Project setup XML snippet in your default nuget.config file to use outside of a project.

::: moniker-end

::: moniker range="<= tfs-2018"

3. Follow steps 1, 2, and 3 to get the tools, add the feed to your local NuGet configuration, and push the package.

   

   ::: moniker-end

::: moniker range="<= tfs-2018 || azure-devops"

Add a feed to NuGet 2

::: moniker-end

::: moniker range="azure-devops"

NuGet 2 uses Personal Access Tokens to access feeds.

To use a 2.x client, first get the v3 feed URL:

1. Navigate to your feed (or create a feed if you haven't).

2. Select Connect to feed:

   [!div class="mx-imgBorder"]

3. Copy the NuGet package source URL:

   [!div class="mx-imgBorder"]

Then replace /v3/index.json with /v2.

[!INCLUDE generate-pat]

Run the following command in an elevated command prompt window to add a NuGet package source:

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

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> 

::: moniker-end

::: moniker range="<= tfs-2018"

NuGet 2 uses Personal Access Tokens to access feeds.

To use a 2.x client, first get the v3 feed URL:

1. Navigate to your feed (or create a feed if you haven't).

2. Select Connect to feed:

   

3. Copy the NuGet package source URL:

   

Then replace /v3/index.json with /v2.

[!INCLUDE generate-pat]

Run the following command in an elevated command prompt window to add a NuGet package source:

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

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> 

::: moniker-end