Try our new research platform with insights from 80,000+ expert users

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

"It gives us good feedback on visualizations and on how our processes have progressed."
"The metrics gathered after deployment, for example, the rate of success versus the rate of failure."
"The IT process automation is the most valuable aspect of this solution."
"It can support very complex environments and dependencies."
"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."
"It is an umbrella system that allows us to integrate many different systems into our heterogeneous environment."
"The main benefit is you can deploy everything with it."
"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."
"This is an all-in-one, one-stop shop, nothing comes close."
"The solution is good for everything, including end-to-end planning and its deployment and testing."
"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's got something that you won't find in other products."
"Reports were automatically generated and sent to management, offering them insights into our progress concerning the predefined roadmap."
"There has been a measurable improvement in productivity of around 40 to 50% after implementing Microsoft Azure DevOps, which has allowed more time to be spent on other things."
"All features are good. Pipelines feature is great, and Boards and Artifacts features are also really good. It is really good at what it does. It is very comprehensive, and it has some really great aspects to it. It is very easy. It is probably one of the easiest to use DevOps tools in the industry, and it is well integrated."
"Everything that's related to the pipeline has been very good."
 

Cons

"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."
"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."
"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."
"I would like to see more support for WebSphere."
"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."
"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."
"GUI for mobile phones: Availability to approve and start deployment through mobile phones."
"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."
"I want DevOps to have more automated reminders about tasks that don't need management. We don't have reminders, so a project manager must track the tasks. It's not automatic."
"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."
"The solution's roadmap and Gantt charts could be improved."
"We did have some brief performance issues, however, that was due to putting everything on one epic instead of breaking a project up."
"The user interface could be improved."
"The tool was developed for Agile project methodology, but I've noticed that there has also been a try to incorporate what is typically done in MS Project, which is for more sequential Waterfall projects. The problem with that is that it is half-baked for Waterfall projects. If you're going to do it, then either go all the way and allow us to use the tool for both or don't do it at all."
"Some of the queries, the way they're built, need to be looked at. We need better query tools."
"The tutorials for building pipelines are an area that is a bit technical for a beginner."
 

Pricing and Cost Advice

"We increased our quality and reduced our time costs."
"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."
"Customers often complain about the price."
"When compared to other vendors, it is cheaper."
"The pricing of Azure DevOps falls within the average range and it is fixed."
"The solution is expensive."
"The reason that customers are going to the cloud is that it provides the ability to reduce the license cost. For example, when purchasing Office 365 it is bundled with Word, Excel, PowerPoint, Access, and many other applications. In the past, purchasing a license was approximately $600. Today it's only $35 or $45 per customer, per client, or per user, plus the storage. It's less expensive for companies today, to use something, such as Microsoft Azure DevOps, and provide the software to all the employees needing a license. It's better to go with the cloud than just to buy the licenses by themselves."
"It is the least expensive product in this class."
"The costs are moderate and justify the value provided."
"With Azure, you have to pay for every user."
"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."
report
Use our free recommendation engine to learn which Release Automation solutions are best for your needs.
881,082 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
No data available
Manufacturing Company
14%
Government
10%
Financial Services Firm
10%
Computer Software Company
10%
 

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 Business42
Midsize Enterprise28
Large Enterprise69
 

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: December 2025.
881,082 professionals have used our research since 2012.