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.1
Number of Reviews
133
Ranking in other categories
Application Lifecycle Management (ALM) Suites (2nd), Release Automation (1st), Enterprise Agile Planning Tools (1st)
 

Featured Reviews

MJ
The main benefit is you can deploy everything with it, but everybody has to need to use this tool in the organization
The main benefit is you can deploy everything with it, but everybody has to need to use this tool in the organization. If some organizations have their own tool, it is hard to make it clear that ARA would be better if everyone used it, because it provides a benefit when you can monitor all the users.
Ivan Angelov - PeerSpot reviewer
Facilitates agile transformation with potential for enhanced intuitiveness
What I liked about the solution is that it offers numerous features that are not available by default unless you are agile. Transitioning from the traditional Waterfall model to an agile methodology was challenging for us. Until 2020, our team predominantly worked with the Waterfall approach, using local tools like ServiceNow. We had a few team members who were familiar with Agile ISO, but none had experience with Azure. Therefore, we pursued Azure certification at the AZ-900 level. Our company organized a training session with a certified Azure expert, which was extremely beneficial for adopting best practices during the initial three months. This preparation helped us get accustomed to the new tool, as transitioning to a new system invariably requires time. Managing a pipeline of deliverables became significantly easier with this solution. We utilized it for stories and integrated change management with Azure DevOps. Eventually, everything related to the environment was organized there, enabling us to follow up and track progress with our technical engineers on an hourly, daily, or weekly basis. Reports were automatically generated and sent to management, offering them insights into our progress concerning the predefined roadmap.

Quotes from Members

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

Pros

"Gives people insight into what's happening during the deployment."
"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. We don't have to wait for someone to do something."
"It provides a wonderful user interface which is easy to use."
"Self-service for developers, because they are able to deploy to development departments on their own, without needing people from operations."
"The metrics gathered after deployment, for example, the rate of success versus the rate of failure."
"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 features that have a significant impact on us include CI/CD, where we have full integration with the source code repository and Azure Pipelines."
"Before using this solution, we had to deploy our applications, from pre-production to production, manually."
"The installation is straightforward. We can create a whole new organization in less than a day."
"Typically the sprints themselves and managing the tasks have essentially eliminated our need for reporting."
"This platform provides a large span of tools and technologies."
"It is good for monitoring purposes. We are using the build pipelines of Microsoft Azure. They are also valuable."
"Mostly, I have found the source code control pipeline and the pull request governance to be very valuable."
"I like the fact that there is built-in Power BI. Both are Microsoft tools. So, you can incorporate dashboard capabilities."
 

Cons

"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."
"We hope that we can integrate the new CD Directive into our portfolio, so we can bring the deployment and release management closer together."
"The stability of the solution can be improved."
"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."
"I would like to see more support for WebSphere."
"Not a perfect ten because the user interface is brand new and it needs improvement."
"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."
"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."
"The test management section needs to be improved."
"Microsoft could focus on refining the reporting and dashboard elements of Azure DevOps to improve it."
"I would like to automate notifications on sprint planning. When we are getting to the end of sprint planning, we would be automatically notified."
"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."
"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."
"Its UI can be easier and more customer-friendly. The UI can be improved from the project management and agile perspective."
"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. To see the percentage completion for a feature or progress of any delivery, it is not easy to draw a report."
"Being more technology-agnostic through ease of integration would be beneficial."
 

Pricing and Cost Advice

"I can save time and money more quickly."
"We increased our quality and reduced our time costs."
"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."
"There is a licensing fee of $6/user per month."
"The price of this solution is fair."
"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."
"The licensing structure is good."
"The costs are moderate and justify the value provided."
"The solution is expensive."
"It is a subscription model and I only pay for what I use."
"The price is cheaper than Jira and some of the other competing tools."
report
Use our free recommendation engine to learn which Release Automation solutions are best for your needs.
851,604 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
No data available
Manufacturing Company
13%
Computer Software Company
13%
Financial Services Firm
12%
Government
9%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

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: May 2025.
851,604 professionals have used our research since 2012.