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
138
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 provides a wonderful user interface which is easy to use."
"The metrics gathered after deployment, for example, the rate of success versus the rate of failure."
"I like that really complex deployments are possible with it."
"It can support very complex environments and dependencies."
"The IT process automation is the most valuable aspect of this solution."
"You can automate everything you want."
"The agents are one of the solution's most valuable features, and I like agents for file transfers so you can transfer the files from agent to agent on the different platforms."
"You can design your workflows for your needs."
"The initial setup is very easy."
"Allows for source control and CI/CD pipelines while linking back to the work items on the Kanban board."
"The work items option is incredibly flexible."
"Most of the features are very valuable for us, especially the source code control and task management."
"Detailed logs allow us to pinpoint the exact cause of any issues, making troubleshooting efficient and accurate."
"The solution is great due to the fact that it's kind of an entire ecosystem."
"Most developers and project managers choose the Microsoft tools to begin with because of familiarity, and these new tools are almost an extension of the tools you're already familiar with. There's a lot of knowledge transfer, which helps, rather than bringing in a new product line."
"Technical support has been excellent; on that side, Microsoft is very good, and the customer support of Microsoft has really improved this past year, and on the cloud side also we are very satisfied because it offers very good support."
 

Cons

"Stability-wise I think it still needs to be improved; performance-wise. It crashes from time to time."
"There are some bugs. For example, during the design of a workflow, important information is lost, it vanishes."
"key thing is support for cloud-based deployment. That is lacking."
"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 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."
"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."
"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 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."
"It is a really complicated product."
"Better integration with the Linux operating system would be an improvement for this solution."
"One thing I would note is that it's hard to know what is included or not in the product."
"The documentation isn't straightforward."
"There are certain areas in Azure DevOps that are better in other products."
"This solution is not as good as Jira when it comes to project management and I think they know it, but it's good enough."
"The dashboards need bigger with better extensions and layouts. There isn't a workflow related to the statuses on the dashboard. It only lists the statuses. You can have one started, and once done, but everything in between is only in progress and could be in any order you want, it lacks flow."
 

Pricing and Cost Advice

"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."
"We increased our quality and reduced our time costs."
"I find that the pricing is good, and it is competitive with the other vendors in the market."
"The main agile features are very expensive."
"Most of the things that we need and use are incorporated in the corporate solution — there are no additional costs."
"It is relatively inexpensive compared to other solutions that necessitate servers and physical hardware."
"We do not pay licenses for this solution."
"The licensing structure is good."
"The cost is quite affordable."
"There is a licensing fee of $6/user per month."
report
Use our free recommendation engine to learn which Release Automation solutions are best for your needs.
907,768 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Construction Company
13%
Comms Service Provider
11%
Outsourcing Company
10%
Financial Services Firm
10%
Manufacturing Company
14%
Financial Services Firm
9%
Government
7%
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 Business43
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.
907,768 professionals have used our research since 2012.