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

"Self-service for developers, because they are able to deploy to development departments on their own, without needing people from operations."
"The main benefit is you can deploy everything with it."
"The capability to provide visibility to the stakeholders, to management, is the biggest piece that showcases what the solution is about."
"The most valuable feature is the ability to see which problems have been resolved from deployment."
"Gives people insight into what's happening during the deployment."
"It provides a wonderful user interface which is easy to use."
"It can support very complex environments and dependencies."
"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."
"This solution works with other Microsoft solutions pretty easily. It was easy to integrate everything into all the other tools that we were using. It integrates very seamlessly."
"Fields can be customized and the reporting is good."
"Stable and scalable solution for work planning and code collaboration. It's fast, and it offers a good user experience."
"Most of the features are very valuable for us, especially the source code control and task management."
"This solution is stable."
"Azure DevOps' collaborative features are good, and it integrates well with other tools in the software development process, like quality testing, documentation, and agile development."
"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."
"It is good for monitoring purposes. We are using the build pipelines of Microsoft Azure. They are also valuable."
 

Cons

"The stability of the solution can be improved."
"key thing is support for cloud-based deployment. That is lacking."
"I would like to see more support for WebSphere."
"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."
"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."
"We hope that we can integrate the new CD Directive into our portfolio, so we can bring the deployment and release management closer together."
"GUI for mobile phones: Availability to approve and start deployment through mobile phones."
"Not a perfect ten because the user interface is brand new and it needs improvement."
"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."
"The tutorials for building pipelines are an area that is a bit technical for a beginner."
"Right now, they tend to have a limit of 1,000 tasks per sprint, and some of their web-based boards, such as the Kanban boards, no longer display tasks. Once you hit over a certain number of task limits, you need to increase those limits."
"Azure DevOps could be improved with more security plugins, especially for SaaS scanning and vulnerability scans."
"We did have some brief performance issues, however, that was due to putting everything on one epic instead of breaking a project up."
"It is very difficult to integrate the product with third-party tools."
"It should have security features for scanning the code and checking it for vulnerability and security. Currently, I am using other tools for this. It should also have integration with other tools to improve security."
"Microsoft Azure DevOps could improve by having better integration with other email servers."
 

Pricing and Cost Advice

"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."
"I can save time and money more quickly."
"Customers often complain about the price."
"The price of the solution is expensive."
"The solution costs $5 or $10 per user, per month."
"I am not aware of any licensing subscriptions for the solution."
"I find that the pricing is good, and it is competitive with the other vendors in the market."
"It is relatively inexpensive compared to other solutions that necessitate servers and physical hardware."
"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."
"There is a license for this solution."
"The pricing of Azure DevOps falls within the average range and it is fixed."
report
Use our free recommendation engine to learn which Release Automation solutions are best for your needs.
881,455 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
9%
 

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: January 2026.
881,455 professionals have used our research since 2012.