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
137
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

"Self-service for developers, because they are able to deploy to development departments on their own, without needing people from operations."
"It can support very complex environments and dependencies."
"You can automate everything you want."
"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."
"We have saved on our time costs and have seen more quality."
"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."
"The product provides efficiency, in terms time, cost, and resources."
"I think on a day-to-day basis, it has increased the capacity to deploy."
"The most valuable feature of this solution is that it saves time."
"With the pipeline we're using, that time was reduced by ten times."
"The most valuable feature is that it brings order to our projects, and we know the status of each one at every moment."
"I like the entire tool because it is a one-stop-solution for DevOps."
"The most valuable feature is that it's fully integrated, where we have a single place to do everything that we need."
"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."
"The automated bill feature is most valuable. As with most software developers, I can build code on my machine, but if one of my coworkers can't build the same code on theirs, there are always issues in trying to track it down. The automated bill process makes it a lot easier to track down where the issues are and find out what bugs aren't being included for whatever reason."
"Using the infrastructures of code enables a productivity increase of a thousand percent."
 

Cons

"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."
"I would like to see more support for WebSphere."
"Not a perfect ten because the user interface is brand new and it needs improvement."
"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."
"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."
"The stability of the solution can be improved."
"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. There is a little bit of a learning curve in learning how to code some of the workflows in Automic at this time. If widely used languages like Perl and Python were integrated, on top of what's already there, the proprietary language, it would make it easier to on-board new resources."
"The first time setup can be very complicated."
"Azure DevOps is set up more for development and less for testing. If it is set up correctly, everyone can use it better, but it was set up from a development point of view, which means it is lacking in what I need from a testing perspective."
"Microsoft could focus on refining the reporting and dashboard elements of Azure DevOps to improve it."
"Information to make it easier to choose items from the marketplace (like MS verified), etc. Otherwise, every item requires a full InfoSec review."
"The tool has a logical link between epic feature, user story, and task, but when you try to generate a report to show the delivery progress against a feature, it is not easy."
"One potential enhancement in Azure DevOps could be integrating more customizable reporting features, particularly for Power BI integration."
"With the query feature, we have to group items, so it becomes difficult for everyone to understand it. It's easier in JIRA, which has filters and other query options."
"While reporting in Azure DevOps is a robust capability, there's always room for enhancement, particularly in providing more granular reports."
"We did have some brief performance issues, however, that was due to putting everything on one epic instead of breaking a project up."
 

Pricing and Cost Advice

"We increased our quality and reduced our time costs."
"Customers often complain about the price."
"I can save time and money more quickly."
"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 am not aware of any licensing subscriptions for the solution."
"I don't know the pricing of DevOps. It would be much cheaper than ALM because ALM came out as a software product initially. Now they are moving into a cloud and subscription model. In that case, Microsoft is coming from Azure and the cloud and DevOps and software as a service, so it would be much cheaper, but the catch would be that they are trying to get money on all the sides, like an operating system, Microsoft Office, or Microsoft Azure DevOps."
"The licensing costs are reasonable."
"The licensing structure is good."
"Most of the things that we need and use are incorporated in the corporate solution — there are no additional costs."
"It is the least expensive product in this class."
"The price is reasonable for the solution."
"The costs are moderate and justify the value provided."
report
Use our free recommendation engine to learn which Release Automation solutions are best for your needs.
886,906 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
17%
Marketing Services Firm
12%
Comms Service Provider
10%
Real Estate/Law Firm
10%
Manufacturing Company
13%
Financial Services Firm
9%
Government
9%
Computer Software Company
8%
 

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 Business43
Midsize Enterprise28
Large Enterprise68
 

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...
What do you like most about Microsoft Azure DevOps?
Valuable features for project management and tracking in Azure DevOps include a portal displaying test results, check-in/check-out activity, and developer/tester productivity.
 

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: April 2026.
886,906 professionals have used our research since 2012.