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

"We have saved on our time costs and have seen more quality."
"The product provides efficiency, in terms time, cost, and resources."
"They have gained efficiency that they cannot achieve in any other way."
"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."
"In first pilot run, we achieved five times faster deployment without human work."
"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."
"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."
"The metrics gathered after deployment, for example, the rate of success versus the rate of failure."
"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."
"I like that the solution is stable and that all ends of the process are integrated seamlessly into the tool."
"DevOps is easy to use because we can arrange each task in a project and follow up with the testing, development, and business teams, and we manage everything through this."
"The most valuable feature is that we can run integrations with DevOps. From a QA perspective and a testing perspective, we can run those tests and integrate automation tools. Then we can run those tests as part of the deployment process. Every time we are deploying something, it automatically runs all the tests."
"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."
"In Microsoft Azure DevOps, you have a one shop to get everything."
"If you're looking for a cross-platform solution that end-to-end does everything in the development life cycle, this would be a very good solution for you."
"Microsoft Azure DevOps has positively impacted our project delivery times; it accomplished exactly what we needed at the right time, and there weren't any issues."
 

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."
"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."
"GUI for mobile phones: Availability to approve and start deployment through mobile phones."
"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."
"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."
"Stability-wise I think it still needs to be improved; performance-wise. It crashes from time to time."
"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 is a lack of integration and portability with other tools and products."
"I would like to see new features added."
"We are currently in the process of moving all of our on-prem to the cloud platform. We are trying to make that move and host the majority of our DevOps services in the cloud because the cloud is where most of the things are going nowadays. However, the process of this transfer is not straightforward, and it could be a lot easier. Microsoft hasn't provided the maturity for migration tools. It could be a lot easier in that respect. I want to see them continue to advance the API capabilities. They could add some more robust functionality to the administrative layer within ADO services. There are a lot of configuration elements that you need to take care of at the organization level and the project configuration level from an administrative capacity. When you're dealing with process templates and things of that nature, you have to do them all manually. Being able to automate some of that using scripts or API functionality would be really nice."
"Non-functional testing such as security testing, log testing, and performance testing can be improved with a better visualization."
"The solution is generally stable but not entirely issue-free."
"Its testing features are limited and can be improved a little more. They should provide more options from the testing and build perspective. Currently, we have to use a third-party product for testing. It would be great if it has more than one testing tool."
"Despite the fact that you can automate most of the things, you still have to produce some scripts."
"One thing I would note is that it's hard to know what is included or not in the product."
 

Pricing and Cost Advice

"Customers often complain about the price."
"I can save time and money more quickly."
"We increased our quality and reduced our time costs."
"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."
"It is the least expensive product in this class."
"I don't have a problem with the pricing."
"The costs are moderate and justify the value provided."
"The price is reasonable for the solution."
"The solution is expensive."
"As the cost structure is per user, I would recommend paying the cost structure based on the amount of data you use rather than the number of users."
"The price of the solution is expensive."
"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.
913,654 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Outsourcing Company
16%
Construction Company
14%
Comms Service Provider
11%
Healthcare Company
9%
Manufacturing Company
13%
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 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: August 2026.
913,654 professionals have used our research since 2012.