No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Has anyone experience a 401 nuget error when running Pulumi on Azure Pipelines when your NuGet.config has an internal/private nuget source?

How did you fix this?  Can't seem to be able to do a pulumi up, works fine in local with the creds manager. but when on pipeline it can't seem to be able to authenicate.

If you are using private feeds, make sure you do NuGet Authenticate.

```- task: NuGetAuthenticate@0
  displayName: 'Authenticate'```


image.png

used your example yaml and made sure build service has permission to access azure artifacts

you are doing that before the restore right?

```    steps:          
      - task: NuGetAuthenticate@0
        displayName: 'Authenticate'
        
      - task: DotNetCoreCLI@2
        displayName: 'Restore'
        inputs:
          command: restore
          projects: ${{ parameters.pathToSolution }}
          feedsToUse: config
          nugetConfigPath: ${{ parameters.directory }}/NuGet.config
          workingDirectory: ${{ parameters.directory }}
          
      - task: DotNetCoreCLI@2
        displayName: 'Build'
        inputs:
          projects: ${{ parameters.pathToSolution }}
          arguments: '--configuration ${{ parameters.buildConfiguration }}'
          workingDirectory: ${{ parameters.directory }}```