What I like most about Azure Pipelines is its seamless integration with Azure DevOps, enabling us to automate the entire CI/CD lifecycle—from build and testing to deployment. Its YAML-based pipeline configuration, reusable templates, support for multiple environments, and integration with various development tools make it flexible and scalable. It also provides good visibility into pipeline execution, simplifies release management, and helps teams deliver software more consistently and efficiently. Review collected by and hosted on G2.com.

Azure Pipelines can have a steep learning curve when configuring complex YAML pipelines, managing templates, and troubleshooting failures. Debugging pipeline issues is not always straightforward, and error messages can sometimes lack sufficient context. Managing self-hosted agents, permissions, and environment-specific configurations also adds operational overhead. Additionally, pipeline execution times and parallel job limitations can affect productivity, particularly for teams handling multiple projects and frequent deployments. Review collected by and hosted on G2.com.

What I like most is the seamless support for any language, platform, and cloud provider. Being able to run parallel builds across Windows, Linux, and macOS with cloud-hosted agents makes it much easier to set up our CI/CD workflows and keeps the whole process extremely efficient. Review collected by and hosted on G2.com.

Azure Pipelines can come with a steep learning curve, especially when you’re setting up complex, multi-stage deployments in YAML. On top of that, troubleshooting failed builds can feel time-consuming because the logs aren’t always immediately clear. I also find that switching between the older and newer interface views can be a bit confusing at times, and the overall navigation can occasionally feel cluttered. Review collected by and hosted on G2.com.

I find Azure Pipelines very scalable and reliable with almost all the required source resources. The user interface is very interactive, making it easy to use. The operation part and the flow of the pipeline are very easy to understand, which enhances usability. The initial setup was quite easy, with clear and straightforward instructions that were user-friendly. This ease of use extends across the Microsoft ecosystem, making it simple to maintain and modify tasks compared to Jenkins. Additionally, the whole process was quite easy to manage due to its interactive and user-friendly nature. Review collected by and hosted on G2.com.

Sometimes the pipeline takes much more time for a very small task. That might be due to latency or some backend issue. So, I think that is something that needs to be improved. Review collected by and hosted on G2.com.

Azure Pipelines helps automate the build, testing, and deployment process, which saves a lot of manual effort. I like that once a pipeline is set up, code changes can automatically move through the deployment process with minimal intervention.

For example, after completing a code change, I just need to create a pull request and merge it. The pipeline handles the build and deployment steps automatically, which reduces manual work and the chances of human error. Review collected by and hosted on G2.com.

Troubleshooting pipeline failures can sometimes be difficult, especially when the error messages are not very clear. Small configuration issues can also cause a build or deployment to fail.

In some cases, I spent more time investigating pipeline configuration issues than fixing the actual code issue. Review collected by and hosted on G2.com.

Azure pipelines make the implementation of CI/CD easier to manage and automate. They are compatible with most development tools, offer support for multiple platforms, and enable the team to deliver consistent updates with reduced manual effort. Review collected by and hosted on G2.com.

The configuration process can be challenging, especially when it comes to YAML pipelines. Moreover, pipelines have various features, some of which are not easy to set up. Review collected by and hosted on G2.com.

Azure Pipelines helps automate the entire CI/CD process, reducing manual effort and improving deployment reliability. I also like its YAML-based approach, which makes pipeline management simple and consistent. Review collected by and hosted on G2.com.

One thing I dislike about Azure Pipelines is that troubleshooting pipeline failures can sometimes be time-consuming, especially when dealing with complex YAML configurations. It can also have a learning curve for new users who are not familiar with CI/CD concepts and pipeline setup Review collected by and hosted on G2.com.

What I value most is the seamless integration with YAML-based definitions, Azure services, and the built-in artifact management. The Environments feature is a game-changer for tracking deployments across stages. Also, as someone who started with personal projects, the availability of free hosted agents is a huge plus; it lowers the entry barrier and allows your CI/CD strategy to scale naturally as the project grows into an enterprise environment. Review collected by and hosted on G2.com.

The workflow for expired Service Connections is a bit friction-heavy. Currently, you often have to jump back to the Azure Portal to renew them because the error messages within DevOps aren't always explicit about the expiration. It would be much smoother to have a "renew" or "re-authorize" trigger directly within the DevOps Service Connection interface to avoid context switching. Review collected by and hosted on G2.com.

In Azure Pipelines you can build, test, write apps in multiple languages.

collaboration is very easy with help of YAML based pipeline definitions.

Boards, Repos, Test Plans, and Artifacts all connect seamlessly because of integration with Azure devops ecosystem

Easy plugins are available in third party tool.

Integration is very easy with other tools Review collected by and hosted on G2.com.

Debugging of failure is very hard to identify due to YAML pipelines.

complexity within Azure DevOps due to which new users fail to understand the syntax

Execution speed and resource limit due to which often there is spike in performance

providing rule base access is very tedious job and time consuming

Cost is very high Review collected by and hosted on G2.com.

The native integration with GitHub and the broader Azure ecosystem is incredibly powerful. Setting up automated CI/CD triggers directly from pull requests is seamless, and the deep traceability from code commit to production deployment provides excellent visibility Review collected by and hosted on G2.com.

Disjointed documentation makes advanced setups difficult to find Review collected by and hosted on G2.com.

YAML pipelines offer strong flexibility and solid version control. Being able to keep pipeline definitions alongside application code supports Infrastructure as Code and makes changes easier to track and audit. Support for multi-stage pipelines, including approvals and environments, also enables more mature release processes with clearer governance. Review collected by and hosted on G2.com.

There isn’t a simple or official way to fully test Azure Pipelines locally, which often forces me into trial-and-error commits just to validate the pipeline logic and confirm everything works as expected. Review collected by and hosted on G2.com.