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

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

 

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

"The main benefit is you can deploy everything with it."
"You can design your workflows for your needs."
"The measurement and the display functions make it easy to report all the statuses up to management, and it has helped our customers with their time, costs, and resources."
"The IT process automation is the most valuable aspect of this solution."
"What we like about the product is that it is more or less an umbrella system that allows us to integrate many different systems into our heterogeneous environment."
"I like that really complex deployments are possible with it."
"I think on a day-to-day basis, it has increased the capacity to deploy. We don't have to wait for someone to do something."
"You can automate everything you want."
"In my previous company, we used this solution to create test cases, test reports, test execution, task boards, and we use the dashboard for the product activity."
"I would advise someone considering this solution to use Microsoft because it is very user-friendly, it can run on small levels of applications, can be calibrated to the application, it can be scaled to a larger scale, from small scale to larger scale, and it is very stable as long as you increase the resources when you need to scale to a larger scale."
"The solution is very useful; it's very easy to use and easy to navigate, the product is very stable and quite reliable, and the scalability, for now, is good for what we need."
"I really like the Microsoft DevOps survey."
"It's graphical representation and tools are easy to use."
"The reports have been most valuable. We have created some dashboards allowing us to be able to check our teams, their progress, and mission plans."
"Microsoft has good integration with its other products, such as Office, Teams, et cetera."
"The solution's most valuable features are backlog management, build release pipeline, and testing."
 

Cons

"We're a WebSphere shop so I would like to see more support for WebSphere, only because it's the platform that they seem to want to use the most."
"The first time setup can be very complicated."
"Stability-wise I think it still needs to be improved; performance-wise. It crashes from time to time."
"One of the biggest features I've been asked by my team to put in there is opening more scripting languages to be part of the platform."
"I would like to see more support for WebSphere."
"There are some bugs. For example, during the design of a workflow, important information is lost, it vanishes."
"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 needs to be better error handling and error descriptions. It should be more clear what the errors are and what we can do to fix them."
"It's too technical sometimes because it's meant for network developers. The CI/CD pipelines are not very easy to manage because it requires a lot of input. So it could be easier to manage."
"I can't think of anything I would like to improve, since I don't have complete knowledge of the platform yet. I'm sure that as I gain more experience, I will understand it better. The price could maybe be cheaper, but I'm sure I'll have more ideas as to improvements and additional features once I've used it more."
"The optimization feature in Microsoft Azure DevOps needs improvement. Sometimes, having control over multiple projects for a customer could be difficult."
"The initial setup of this solution was complex. Every part of the implementation was difficult."
"Requirements management is an area that can be improved."
"There is a lack of integration and portability with other tools and products."
"While reporting in Azure DevOps is a robust capability, there's always room for enhancement, particularly in providing more granular reports."
"Proper Gantt charting should be a feature that is included because as it is now, we have to create it ourselves."
 

Pricing and Cost Advice

"I can save time and money more quickly."
"We increased our quality and reduced our time costs."
"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."
"Customers often complain about the price."
"I don't know what we pay, but I do know what I've seen online. If we switched to JIRA, we will basically have to double our costs because we still have to pay for the DevOps licensing. We're probably spending $100 a month on it. It has only standard licensing fees."
"As the cost structure is per user, I would recommend paying the cost structure based on the amount of data you use rather than the number of users."
"I don't have a problem with the pricing."
"The pricing is very competitive because of the whole development cycle by Azure DevOps. You don't have to buy and integrate several different tools."
"We do not pay licenses for this solution."
"For the basic license, it is around five euros per month."
"The main agile features are very expensive."
"It is the least expensive product in this class."
report
Use our free recommendation engine to learn which Release Automation solutions are best for your needs.
910,564 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Construction Company
16%
Comms Service Provider
12%
Outsourcing Company
11%
Financial Services Firm
9%
Manufacturing Company
14%
Financial Services Firm
9%
Government
8%
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: July 2026.
910,564 professionals have used our research since 2012.