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

"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 product provides efficiency, in terms time, cost, and resources."
"It gives us good feedback on visualizations and on how our processes have progressed."
"Self-service for developers, because they are able to deploy to development departments on their own, without needing people from operations."
"The most valuable feature is the ability to see which problems have been resolved from deployment."
"It can support very complex environments and dependencies."
"You can design your workflows for your needs."
"We increased our quality and reduced our time costs."
"It is a really easy way to define all of the features that you need to deliver. You can link those features to epics and break them down into user stories. You can also assign the user stories into sprints for doing your product improvement planning."
"The creation of test plans is valuable and I like the reporting features."
"The product is easy to use...It is a stable solution."
"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."
"Overall, the solution is pretty good, it fulfills most of our requirements, the stories and test cases on offer are great, the initial setup was self-explanatory and straightforward, and the pricing seems to be reasonable."
"We tried other tools, but Azure DevOps has a richer toolset, and it fits in better with our process."
"Mostly, I have found the source code control pipeline and the pull request governance to be very valuable."
"It's graphical representation and tools are easy to use."
 

Cons

"GUI for mobile phones: Availability to approve and start deployment through mobile phones."
"We hope that we can integrate the new CD Directive into our portfolio, so we can bring the deployment and release management closer together."
"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."
"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."
"key thing is support for cloud-based deployment. That is lacking."
"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 are some bugs. For example, during the design of a workflow, important information is lost, it vanishes."
"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."
"Some things like project management, tasks, progress, and having work progress views require us to use some external tools, or to create our own internal tools. These are not native to DevOps. It would be ideal if, instead of searching for third-party solutions, they had these feature sets or capabilities included under DevOps."
"There is room for improvement, as this is not the finished article at all."
"When you compare with Jira, there is a lack of progress features."
"At times, our development work encounters issues, particularly when executing numerous CI/CD processes."
"DevOps is simple to use, but it is severely limited in terms of project management."
"The interface is very bad."
"I would like to automate notifications on sprint planning. When we are getting to the end of sprint planning, we would be automatically notified."
"There could more integration with other platforms."
 

Pricing and Cost Advice

"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."
"Customers often complain about the price."
"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."
"We do not pay licenses for this solution."
"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."
"When compared to other vendors, it is cheaper."
"The licensing structure is good."
"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."
"Most of the things that we need and use are incorporated in the corporate solution — there are no additional costs."
"The main agile features are very expensive."
report
Use our free recommendation engine to learn which Release Automation solutions are best for your needs.
902,456 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Construction Company
16%
Comms Service Provider
14%
Financial Services Firm
12%
Marketing Services Firm
10%
Manufacturing Company
14%
Financial Services Firm
9%
Government
8%
Computer Software Company
7%
 

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 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...
Microsoft Azure DevOps: what is your experience regarding pricing and costs ?
Pricing experience is limited, as I am a user of this product and not involved in the pricing aspects. There has definitely been a lot of return on investment from using Microsoft Azure DevOps due ...
 

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: June 2026.
902,456 professionals have used our research since 2012.