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

"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."
"You can design your workflows for your needs."
"At the end of the day, at the end of the year, CA offered the best package overall, and that wasn't just from a product standpoint but also a support standpoint."
"The metrics gathered after deployment, for example, the rate of success versus the rate of failure."
"It can support very complex environments and dependencies."
"The most valuable feature is the ability to see which problems have been resolved from deployment."
"They have gained efficiency that they cannot achieve in any other way."
"I like that really complex deployments are possible with it."
"Some of the most valuable features are the ease of use and the ability to monitor a lot of things. It has a lot of applications and facilities that meet all the developers' requirements. For example, we can use application insights to get an idea of our application's performance. Since it's cloud-based, it's really good for collaboration and working as a team."
"It has a good GUI, and it's very user-friendly."
"Azure DevOps is effective for repository management and code collaboration. We can create branches, differentiate between code versions, save and review code later, get PR approvals, and more. All these features are valuable."
"We tried other tools, but Azure DevOps has a richer toolset, and it fits in better with our process."
"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."
"Microsoft Azure DevOps is very useful in terms of management."
"It is good for the purpose it is designed for. It is good for maintaining a repository of application code, creating pipelines for deploying the code, building the code, and deploying the code. It can be easily used by developers. There are no issues."
"The most valuable feature of this solution is that it saves time."
 

Cons

"We hope that we can integrate the new CD Directive into our portfolio, so we can bring the deployment and release management closer together."
"Stability-wise I think it still needs to be improved; performance-wise. It crashes from time to time."
"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."
"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 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."
"key thing is support for cloud-based deployment. That is lacking."
"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."
"They have brought a lot of new collaboration features in the latest version. We haven't used those features, but they should continue to expand it more on the collaboration front so that two developers can look at the code and work at the same time. It will be helpful for working from home."
"A notable improvement would be adding more notifications."
"Microsoft could improve Visual Studio by making it easier to find the plugins you need to get your job done. Maybe they could implement an AI search instead of a simple tech search. Sometimes, people come up with a catchy name for something, and you don't know how it's spelled. For example, a developer might come up with a packet wizard and spell weird, like P-A-K-I-T."
"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."
"I think that they have some menus there that are not very well placed."
"The ability to integrate Microsoft Azure DevOps with other platforms and Microsoft products can be improved."
"Integration and plugins for other tools could better. Like if you want to integrate the DevOps with other tools that are in the market. This could be for the engineering tools to check code quality, application security tools, and DevOps dashboard tools."
"The dashboard could be improved. Although there is flexibility in configuring it, there are some metrics that we have to configure ourselves."
 

Pricing and Cost Advice

"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."
"Customers often complain about the price."
"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 licensing fee of $6/user per month."
"The cost is quite affordable."
"It is a subscription model and I only pay for what I use."
"It is the least expensive product in this class."
"There is a license for this solution."
"I find that the pricing is good, and it is competitive with the other vendors in the market."
"Its pricing is reasonable for the number of features that you get and the functionality that you can utilize for the agile delivery, which is what we are using it for. I found it extremely cost-effective."
report
Use our free recommendation engine to learn which Release Automation solutions are best for your needs.
902,588 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Construction Company
15%
Comms Service Provider
13%
Financial Services Firm
11%
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,588 professionals have used our research since 2012.