Azure DevOps Service Connection field in NuGet Authenticate task (v1.*) — No service connection type found and existing connections not appearing in dropdown

Question

Azure DevOps Service Connection field in NuGet Authenticate task (v1.*) — No service connection type found and existing connections not appearing in dropdown

Manojkumar Dhamodharan 25

Hello,

I am facing an issue with the 'Azure DevOps' Service Connection field in the NuGet Authenticate task (version 1.*) in Azure Pipelines.

Problem 1 — Cannot create 'Azure DevOps' Service Connection type:

When I navigate to Project Settings → Service Connections → New Service Connection and search for Azure DevOps, it returns 'No Service Endpoint Found'. There is no dedicated Azure DevOps connection type available in the list.

Problem 2 — Existing connections not appearing in dropdown:

I have already created both a NuGet service connection and a Generic service connection using a Personal Access Token (PAT) scoped to Packaging (Read). However, neither of these connections appear in the 'Azure DevOps' Service Connection dropdown inside the NuGet Authenticate task UI.

What I have already tried:

Created a NuGet service connection with Token Authentication
Created a Generic service connection with the Azure DevOps Artifacts feed URL
Verified 'Grant access permission to all pipelines' is enabled on both connections
Verified the service connections are created in the same project as the pipeline
Verified the PAT is valid and not expired

What exactly is the 'Azure DevOps' Service Connection type and how is it created?
Which service connection type does this dropdown field actually accept?
Is there a marketplace extension required to register this endpoint type?
If this field is deprecated or non-functional, what is the recommended alternative for cross-organization NuGet feed authentication?

Any guidance or official documentation pointing to this specific field would be greatly appreciated.

Thank you!

Praveen Kumar Gudipudi 1,880 Reputation points Microsoft External Staff Moderator

2026-03-04T11:52:44.2466667+00:00
Hello Manojkumar Dhamodharan ,

The issue arises from a misleading label in the Azure DevOps NuGet Authenticate task, not from a system failure or misconfiguration.

The task UI refers to an “Azure DevOps Service Connection,” but no such service connection type exists in Azure DevOps. As a result, users cannot create or select an “Azure DevOps” connection, and existing Generic service connections are not supported by this task.

This is expected product behavior. The NuGet Authenticate task is designed to:

Automatically authenticate when using feeds within the same organization

Accept only NuGet‑type service connections when accessing feeds in another organization

The recommended and fully supported approach is to reference the NuGet service connection directly in YAML, rather than relying on the Classic UI dropdown.

Key Takeaway

This is a UI/labeling limitation, not a defect or outage. Authentication works as designed when the correct NuGet service connection is used following Microsoft’s documented guidance.
https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/reference/nuget-authenticate-v1?view=azure-pipelines

https://learn.microsoft.com/en-us/azure/devops/pipelines/packages/nuget-restore?view=azure-devops&tabs=yaml
Praveen Kumar Gudipudi 1,880 Reputation points Microsoft External Staff Moderator

2026-03-09T08:25:32.6633333+00:00

Hello Manojkumar Dhamodharan ,
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Manojkumar Dhamodharan 25 Reputation points

2026-03-09T08:31:47.1966667+00:00

Hello @Praveen Kumar Gudipudi ,

We initially attempted to use the Azure DevOps service connection, but since it is not supported in this case, we proceeded with the NuGet service connection option in the NuGetAuthenticate task. This approach is working as expected.

Thanks for the input, mate!

Answer accepted by question author

0 additional answers

Your answer

Praveen Kumar Gudipudi 1,880 Reputation points Microsoft External Staff Moderator

2026-03-04T11:52:44.2466667+00:00

Hello Manojkumar Dhamodharan ,

The issue arises from a misleading label in the Azure DevOps NuGet Authenticate task, not from a system failure or misconfiguration.

The task UI refers to an “Azure DevOps Service Connection,” but no such service connection type exists in Azure DevOps. As a result, users cannot create or select an “Azure DevOps” connection, and existing Generic service connections are not supported by this task.

This is expected product behavior. The NuGet Authenticate task is designed to:

Automatically authenticate when using feeds within the same organization

Accept only NuGet‑type service connections when accessing feeds in another organization

The recommended and fully supported approach is to reference the NuGet service connection directly in YAML, rather than relying on the Classic UI dropdown.

Key Takeaway

This is a UI/labeling limitation, not a defect or outage. Authentication works as designed when the correct NuGet service connection is used following Microsoft’s documented guidance.
https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/reference/nuget-authenticate-v1?view=azure-pipelines

https://learn.microsoft.com/en-us/azure/devops/pipelines/packages/nuget-restore?view=azure-devops&tabs=yaml
Praveen Kumar Gudipudi 1,880 Reputation points Microsoft External Staff Moderator

2026-03-09T08:25:32.6633333+00:00

Hello Manojkumar Dhamodharan ,
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Manojkumar Dhamodharan 25 Reputation points

2026-03-09T08:31:47.1966667+00:00

Hello @Praveen Kumar Gudipudi ,

We initially attempted to use the Azure DevOps service connection, but since it is not supported in this case, we proceeded with the NuGet service connection option in the NuGetAuthenticate task. This approach is working as expected.

Thanks for the input, mate!

Answer 1

Keketso Mokgele 75

create a personal access token
create a generic service connection (serve URL your Azure DevOps NuGet feed URL)
Use the service connection in the NuGet authenticate task
verify pipeline permissions
test the pipeline

Share via

Azure DevOps Service Connection field in NuGet Authenticate task (v1.*) — No service connection type found and existing connections not appearing in dropdown

Key Takeaway

0 additional answers

Your answer