I'm trying to use the Pipelines Agent artifact (windows-vsts-build-agent) to setup a new agent`:
- using Azure's Windows 10 image
- configured interactively (with autologon = true)
- with the goal to run UI Tests on it (through Azure Pipelines).
While the agent configuration succeeds (an entry is created in Agent Pool on Azure Pipelines), it shows as offline.
After logging in to this VM manually, I can see this screen:
After confirming this screen and logging into the VM manually, the agent comes up as expected.
Any ideas/hints what we can do, so the agent comes 'online' without the need for manual intervention?