I have a console application written in .Net core that functions as a windows service. My aim is to deploy this to one of our VMs using Azure devops so that we can install the application as a service and have it poll an internal api and run some business logic on a timer behind the scenes.
My build pipeline is in place in DevOps and is generating the necessary artifacts (basically the folder I want to deploy to the VM) as a zip file but the issue I am now having is deploying to the filesystem.
Usually in Devops we would be deploying to IIS using a service principle or an app service that is connected to our Azure tenant meaning a lot of the verification etc is done for us however, after trawling the Microsoft documentation I could not find an example of how to use a service principle (essentially a verified connection between DevOps and the VM) to deploy to the filesystem of the VM.
Does anyone have any pointers as to which task to use for this? I'm look at the transfer files via SSH option and it appears to allow you select a service principle (which we have in place anyway as we are already deploying IIS websites to this server) so in theory I believe I could use this.
Any help or pointers / best practise for this scenario would be greatly appreciated.