No more typing reviews! Try our Samantha, our new voice AI agent.

Automic Continuous Delivery Automation [EOL] vs Microsoft Azure DevOps comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Automic Continuous Delivery...
Average Rating
8.0
Number of Reviews
13
Ranking in other categories
No ranking in other categories
Microsoft Azure DevOps
Average Rating
8.2
Reviews Sentiment
7.0
Number of Reviews
139
Ranking in other categories
Application Lifecycle Management (ALM) Suites (2nd), Release Automation (1st), Enterprise Agile Planning Tools (1st)
 

Featured Reviews

reviewer895359 - PeerSpot reviewer
Principal Project Engineer at a computer software company with 501-1,000 employees
Automatic installation for complex deployments and environments, with good workflow support
I like that really complex deployments are possible with it. It's very good. You have everything you need. You can design your workflows for your needs. You can do so much more, it's not just an automatic installation tool. It's a real deployment tool. I can do the complete deployment with everything that is possible.
Bharadwaj Deepak Mohapatra - PeerSpot reviewer
DevOps Engineer at ENTERPRISE SYSTEM SOLUTIONS LIMITED
Have built reliable end-to-end pipelines and streamlined cloud provisioning through consistent collaboration practices
I am currently working with open-source tools such as Jenkins for my main CI/CD pipeline, and for enterprise clients, I am using Microsoft Azure DevOps CI/CD pipeline. For other clients, I have also implemented CI/CD YAML pipelines through GitLab CI/CD workflow and GitHub Actions. I am creating the end-to-end CI/CD pipeline from development to deployment and monitoring all of this. Azure Boards is easier than Jira for my understanding because there are very easy points to manage the Agile methodology which we work on. Because it is a GUI, sometimes the process may take a few minutes more than the CLI process since the backend is running the exact CLI, but we are commanding through the GUI. There is definitely a time lag, but it is more secure. Microsoft Azure DevOps pipelines work very seamlessly rather than other CI/CD pipelines, as of my understanding. The downside is that the process may take more time when deploying some clusters, Kubernetes, Azure AKS service, or some vast microservice architecture deployments. There may be a little bit of lag I feel, though I cannot tell very strictly that this is a disadvantage, but sometimes it takes a little more time than other cloud infrastructures. All the major things are done by GUI, which is somewhat a little slow. However, if considering automations, process, monitoring, and provisioning, then it is the best cloud service across all the other service providers. Our implementation is a hybrid cloud. Microsoft Azure DevOps is definitely easily scalable. I have worked on many Kubernetes infrastructures and microservice deployments, and I have seen that replication is very good because it is very easy. The replication process is very straightforward. I definitely advocate for using less code because it is very time-consuming. If using GCP or Amazon Web Service, there is more interaction related to work over the CLI process. In terms of Microsoft Azure DevOps, there are many things done by the GUI, which is the best part.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"It provides a wonderful user interface which is easy to use."
"We have saved on our time costs and have seen more quality."
"The most valuable feature is the ability to see which problems have been resolved from deployment."
"I would say our headwind, or our time to market, is reduced considerably. We get more consistent results out of it, because you write one time and once it's automated you expect it to behave the same way every time. And it cut down a lot of re-work for us."
"It is a very stable solution and we can rely on pressing a button to perform a full-stack automatic installation that reliably finishes in eight hours instead of a problematic three-week manual installation."
"In first pilot run, we achieved five times faster deployment without human work."
"The metrics gathered after deployment, for example, the rate of success versus the rate of failure."
"The main benefit is you can deploy everything with it."
"It is a well-integrated product in terms of the development lifecycle."
"What I like the most is that it is easy to comprehend, and it's easy to use."
"The nice thing about Visual Studio Code is that it's a modular design. So if you're working on a strange language that has a different syntax, you can just get a plugin that'll format your code for you based on the language it's in."
"As a result, the throughput and velocity increased simply because the Kanban board made them more visible."
"It is good for the purpose it is designed for. It is good for maintaining a repository of application code, creating pipelines for deploying the code, building the code, and deploying the code. It can be easily used by developers. There are no issues."
"The solution integrates well with other Azure services and third-party tools."
"Detailed logs allow us to pinpoint the exact cause of any issues, making troubleshooting efficient and accurate."
"The solution has proven itself to be very mature and robust, quite stable, and its scalability potential is very good."
 

Cons

"File transfer is not very efficient. It takes a bit longer than some other methods and when you send the file from one platform to another, especially from the mainframe, the results consumption is quite high compared to other methods."
"There is an issue with the stability in the tool. The process of agent will stop, then the monitoring agent can't be recognized because the process is running, but you can talk with the system."
"I would like to see more support for WebSphere."
"If you have a technical problem and need development of the tool, the support team is terrible, because they cannot help with the technical details."
"It would be very beneficial for us to see integrations into cloud environments, especially into the Google Cloud environment because we are heading towards cloud."
"At the moment, the version that we are using (version 12.0), the environment is complex with multiple installations. Therefore, the monitoring is not scalable, but this should be improved in 12.1 and 12.2."
"There are some bugs. For example, during the design of a workflow, important information is lost, it vanishes."
"The stability of the solution can be improved."
"When we don't have some permissions, we have to research how to get them, and it's not obvious."
"The UI, the user experience, is challenging for newcomers."
"While reporting in Azure DevOps is a robust capability, there's always room for enhancement, particularly in providing more granular reports."
"The Wiki for this solution is not very good."
"Definitely, there should be more integration between GitHub and Azure DevOps."
"They should expand it from just a PC, software, or server development platform to other kinds of software or engineering systems so that it is not necessarily built around a normal PC with a server. I would like to see the ability to write my own scripts in my own compiled program or online. Right now, there are things that you can do in the user interface, but you can't do them programmatically and vice versa. I want to see them both. If I can do it in a script, I should be able to do it from the user interface, and if I can do it in the user interface, I should be able to do it in a script."
"It is very difficult to integrate the product with third-party tools."
"There may be a little bit of lag I feel, though I cannot tell very strictly that this is a disadvantage, but sometimes it takes a little more time than other cloud infrastructures."
 

Pricing and Cost Advice

"We increased our quality and reduced our time costs."
"I can save time and money more quickly."
"Customers often complain about the price."
"If you have a fixed contract, it has limits to spreading out. If you have a flexible enterprise license contract, then you have a lot of scalability for this tool."
"The cost is quite affordable."
"It is a subscription model and I only pay for what I use."
"Microsoft Azure DevOps is an expensive solution."
"The pricing of Azure DevOps falls within the average range and it is fixed."
"As a Microsoft Partner, you get a discount on the pricing. Licensing costs are around $80 a month for DevOps, but for Azure, it is about $200 a month."
"There are other solutions available that are open source and free, such as GitLab."
"The price is reasonable, but of course, you can find others that are cheaper such as Atlassian."
"Microsoft Azure DevOps is free for up to five users and allows you to track a maximum of three projects."
report
Use our free recommendation engine to learn which Release Automation solutions are best for your needs.
911,493 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Construction Company
15%
Outsourcing Company
13%
Comms Service Provider
12%
Financial Services Firm
8%
Manufacturing Company
14%
Financial Services Firm
9%
Government
7%
Computer Software Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business2
Midsize Enterprise2
Large Enterprise9
By reviewers
Company SizeCount
Small Business44
Midsize Enterprise28
Large Enterprise70
 

Questions from the Community

Ask a question
Earn 20 points
Which is better - Jira or Microsoft Azure DevOps?
Jira is a great centralized tool for just about everything, from local team management to keeping track of products and work logs. It is easy to implement and navigate, and it is stable and scalabl...
Which is better - TFS or Azure DevOps?
TFS and Azure DevOps are different in many ways. TFS was designed for admins, and only offers incremental improvements. In addition, TFS seems complicated to use and I don’t think it has a very fri...
Microsoft Azure DevOps: what is your experience regarding pricing and costs ?
I rate Microsoft Azure DevOps price as a one, which means it is a good value.
 

Also Known As

CA Continuous Delivery Automation, Automic Release Automation, Automic ONE Automation, UC4 Automation Platform
Azure DevOps, VSTS, Visual Studio Team Services, MS Azure DevOps
 

Overview

 

Sample Customers

BET365, Charter Communications, TASC
Alaska Airlines, Iberia Airlines, Columbia, Skype
Find out what your peers are saying about Microsoft, GitLab, Red Hat and others in Release Automation. Updated: August 2026.
911,493 professionals have used our research since 2012.