When running the pipeline on Automation Ops, what is the user under which the pipelines are run?
When the Pipeline Runtime Environment is set up, a Pipeline Robot account will be created.
Scenario 1: If there is no user account added to the Pipelines folder and the process is background, it would run under NT authority\Local Service Account.
Process refers to, for example, Build and Publish, etc as shown in the image below:
To check if the package is set to background or not, download it from the Orchestrator folder packages and open it in Studio after renaming it to .zip.
If it is set to background and the pipeline Robot has predefined credentials,:
The job is run under the NT AUTHORITY\LOCAL SERVICE account.
Note: The NT AUTHORITY\LOCAL SERVICE is a predefined local account used by the service control manager in Windows operating systems. This account has minimal privileges on the local computer and presents anonymous credentials on the network.
Scenario 2: Provide credentials to the Pipeline Robot on Orchestrator instead of predefined credentials
It still runs under NT Authority\ Local Service.
Scenario 3:
Modify the background process toggle on the package and republish.
Update the Process on the Orchestrator with the new package.
Run the pipeline, and it runs under the user account defined for the Robot.
