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

"I like that really complex deployments are possible with it."
"It can support very complex environments and dependencies."
"It provides a wonderful user interface which is easy to use."
"In first pilot run, we achieved five times faster deployment without human work."
"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."
"Deployment workflow (WF) can be designed this way, so that it is not necessary to provide all applications (systems) artifacts of which an application consists."
"The main benefit is you can deploy everything with it."
"The event monitor is very good. You can monitor when the file is created so you can pick up the file once it's done."
"Microsoft Azure DevOps provides tools for tracking tasks and requirements, allowing the team to log in, see their assigned tasks, and mark them as finished while offering integrated graphics to monitor project progress."
"I would recommend this solution; I like Azure DevOps."
"The extensibility of the work item forms and customizations as well as the backend API to query the data, et cetera, and manipulate the data programmatically are all very valuable aspects of the product."
"It is a really easy way to define all of the features that you need to deliver. You can link those features to epics and break them down into user stories. You can also assign the user stories into sprints for doing your product improvement planning."
"Overall, this is a good product and if the Gantt chart and occupancy reporting features are added then it will be the most powerful one in this space."
"The pricing seems to be reasonable."
"It is easy to use. The shared repository is useful. Everything is in one environment."
"Setting up Azure DevOps was straightforward. It's easy to use the default templates. Everything is under our control, so it's simple to implement new requirements."
 

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."
"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 are some bugs. For example, during the design of a workflow, important information is lost, it vanishes."
"We hope that we can integrate the new CD Directive into our portfolio, so we can bring the deployment and release management closer together."
"I would like to see more support for WebSphere."
"Stability-wise I think it still needs to be improved; performance-wise. It crashes from time to time."
"The dashboard should allow you to see the current state of packages in each environment, not only on an individual application basis, but across the entire application platform."
"key thing is support for cloud-based deployment. That is lacking."
"We are facing some problems because the capacity can only be measured within a project. It cannot be measured across multiple projects. So, the reporting needs to be enhanced, and there should be more graphs to be able to easily give the upper management insights about all the employees from different departments. It will be helpful for employee management. Currently, the managers over here are using Power BI for insights because the functionality of Azure DevOps Boards is not enough. So, we have to export the data into another visualization tool and get the results."
"I would like to see better interoperability with the agile scaling frameworks."
"I think that the integration is to some extent, immature."
"The portfolio is one area where DevOps has room for improvement. Built-in reporting and visualization also could be better. We're using Power BI and Tableau to compile more complex reports and dashboards. Azure DevOps has some out-of-the-box reporting capabilities, but they're very simple. It's usually okay on the team level, but if you have to run a complex report, it's difficult and insufficient, so we use Power BI as an extension."
"The ability to extend work items was more flexible than it is now. Talking version control, one of our customers had some issues because they found it very difficult to manage more than 1000 repositories for one team project."
"Testing is very important. Microsoft Azure DevOps tests very well. However, DevOps teams need to be aware of what they are impacting when someone updates anything on the system."
"There could more integration with other platforms."
"The testing agents need to be improved, they can enhance the areas related to continuous integration and build automation and add more technologies for the build."
 

Pricing and Cost Advice

"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."
"I can save time and money more quickly."
"We increased our quality and reduced our time costs."
"When compared to other vendors, it is cheaper."
"The solution's deployment and licensing costs are very cheap compared to those of its competitors."
"We have an MPN subscription for Microsoft Azure DevOps, and it's all included."
"The solution costs $5 or $10 per user, per month."
"There is a license for this solution."
"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."
"The costs are moderate and justify the value provided."
"We do not pay licenses for this solution."
report
Use our free recommendation engine to learn which Release Automation solutions are best for your needs.
916,582 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Outsourcing Company
15%
Construction Company
13%
Comms Service Provider
11%
Healthcare Company
8%
Manufacturing Company
13%
Financial Services Firm
9%
Government
7%
Outsourcing 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 am not much involved in the pricing, licensing, or costing aspects. However, one of my colleagues is involved in the licensing and pricing part, and it is very efficient. We are Microsoft Gold Pa...
 

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: October 2026.
916,582 professionals have used our research since 2012.