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

"The measurement and the display functions make it easy to report all the statuses up to management, and it has helped our customers with their time, costs, and resources."
"We have saved on our time costs and have seen more quality."
"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."
"The main benefit is you can deploy everything with it."
"The product provides efficiency, in terms time, cost, and resources."
"The capability to provide visibility to the stakeholders, to management, is the biggest piece that showcases what the solution is about."
"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 most valuable feature is the ability to see which problems have been resolved from deployment."
"It's a good tool, quite rich, it has a lot of features, and quite a lot of analytical capabilities which are built on top of it so that you can see how your projects are going and all that stuff."
"If you are working with Microsoft products like Office 365 the best cloud solution would be on Azure services."
"It is good for monitoring purposes. We are using the build pipelines of Microsoft Azure. They are also valuable."
"It has a good GUI, and it's very user-friendly."
"Everything that's related to the pipeline has been very good."
"It's very user-friendly, and the documentation is good. The most valuable feature is backlog item creation, where we pick features and other things. The burndown chart created for projects to be maintained by the development teams is also useful."
"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."
"Microsoft Azure DevOps is a very useful system."
 

Cons

"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."
"I would like to see more support for WebSphere."
"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."
"There are some bugs. For example, during the design of a workflow, important information is lost, it vanishes."
"GUI for mobile phones: Availability to approve and start deployment through mobile phones."
"key thing is support for cloud-based deployment. That is lacking."
"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."
"It would be very beneficial for us to see integrations into cloud environments, especially into the Google Cloud environment because we are heading towards cloud."
"The user interface could be improved."
"Every time we scale up we need a new license and that takes time, it's not just a click and it's done."
"The functions have too much dependency right now, so it makes it really, really hard to upgrade and make a change in the code."
"The solution's roadmap and Gantt charts could be improved."
"Information to make it easier to choose items from the marketplace (like MS verified), etc. Otherwise, every item requires a full InfoSec review."
"A notable improvement would be adding more notifications."
"When we don't have some permissions, we have to research how to get them, and it's not obvious."
"Its UI can be easier and more customer-friendly. The UI can be improved from the project management and agile perspective."
 

Pricing and Cost Advice

"We increased our quality and reduced our time costs."
"Customers often complain about the price."
"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."
"Most of the things that we need and use are incorporated in the corporate solution — there are no additional costs."
"There is a license for this solution."
"As a Microsoft Partner, you get a discount on the pricing. Licensing costs are around $80 a month for DevOps, but for Azure, it is about $200 a month."
"The main agile features are very 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 cost is quite affordable."
"The solution is expensive."
"With Azure, you have to pay for every user."
report
Use our free recommendation engine to learn which Release Automation solutions are best for your needs.
911,839 professionals have used our research since 2012.
 

Top Industries

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