Universal Automation is PowerShell specific. Although Azure DevOps has tasks that integrate with PowerShell, they only collect output from the stdout stream and don’t integrate as tightly with PowerShell.

Azure DevOps requires a connection to the internet to control the execution of scripts on agents that run on-premises. Universal Automation is a stand-alone agent and does not require a connection to a master to drive the execution of scripts.

Both Azure DevOps and Universal Automation can execute scripts and schedule scripts to run.

Both Azure DevOps and Universal Automation allow for users to provide parameters to scripts when running them. Universal Automation doesn’t require any configuration for these parameters as they will be interpreted from the param block of your scripts.

Azure DevOps has the concept of projects, pipelines, tasks, and steps. Universal Automation’s architecture is simpler and doesn’t have the same level of organization. Scripts within UA can trigger other scripts to achieve pipeline-like functionality.

Azure DevOps offers extensive role-based access and access controls. UA provides role-based access controls. UA provides authentication through its Universal Dashboard website. This requires some configuration of UA.

Azure DevOps configuration is handled through the use of YAML scripts within the configured repository. UA uses PowerShell scripts for configure and jobs that are run as PowerShell scripts.