I have a custom library that's packaged and published as a nuget package to this server:

https://pkgs.dev.azure.com/my-project-feed/_packaging/my-project-feed/nuget/v3/index.json

To my knowledge that's a public url (with restricted access [and a fake, in this case]).

I can add my library as a nuget package to my client application, everything builds and runs as expected so at least locally everything is fine.

However on the azure devops pipeline the build fails with this exception:

##[error]The nuget command failed with exit code(1) and error(NU1101: Unable to find package My.Custom.Package. No packages exist with this id in source(s): {C path}\dotnet\library-packs, NuGetOrg
Errors in {D path}\My.Blazor.Client\My.Blazor.Client.csproj
    NU1101: Unable to find package My.Custom.Package. No packages exist with this id in source(s): {C path}\dotnet\library-packs, NuGetOrg)
##[error]Packages failed to restore

If I add the package as a project reference by dll the build works fine.

My first suspicion is that this is a permissions issue. We are setting this environment up for first usage so it's likely we missed something.

What I have tried

There are two Project Build Service groups defined, I have tried giving both of them Contributor rights, one only had Collaborator, but that didn't change anything.

My question

• Is this indeed a permissions issue? If so, which service account (or group) would need what rights?
• If not, what could be happening?