UiPath Tasks for Azure DevOps

I assume that you've recently installed the agent, so the agent version would indeed be newer. 

Make sure to also install npm from here, or just don't demand npm from the required agent capabilities for your job, since our tasks do not need it.

As per .NET backward-compatibility rules, this should work just fine.

The service connection has nothing to do with the agent itself. A service connection is basically a way of sending a set of credentials to a build agent in a secure manner.

You should just create the agent (see the Self-hosted agent topic over at https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/agents?view=azure-devops&tabs=browser), add it to a new agent pool, and assign jobs to that pool in your pipeline/build definition (either set it in your YML file or, if you're using a classic pipeline with the visual editor, just edit the build definition and assign it over there). 

Obviously, the self-hosted agent needs to be able to access your Azure DevOps instance (be it Cloud or On-Premises) for it to even be connectable.

Separately, you should go to Project Settings -> Service Connection and add a new service connection to Orchestrator (basic auth should be used for on-premises Orchestrators), one that you should use in your task, irrespective of where the agent that will run the build is located.

Hi Allen,

You will first have to add a service connection to that Orchestrator beforehand, but otherwise it's the same.

Your Orchestrator doesn't need to have a public URL if you use an on-premises Azure DevOps agent (that is, one that has access to the Orchestrator, even if the Orchestrator isn't publicly exposed).