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

"I would say our headwind, or our time to market, is reduced considerably. We get more consistent results out of it, because you write one time and once it's automated you expect it to behave the same way every time. And it cut down a lot of re-work for us."
"The most valuable feature is the ability to see which problems have been resolved from deployment."
"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."
"Gives people insight into what's happening during the deployment."
"It is an umbrella system that allows us to integrate many different systems into our heterogeneous environment."
"It can support very complex environments and dependencies."
"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."
"The product provides efficiency, in terms time, cost, and resources."
"DevOps is easy to use because we can arrange each task in a project and follow up with the testing, development, and business teams. We manage everything through this."
"The simplicity and ease of use are two features that we have found to be most valuable."
"My team likes the integration that Microsoft Azure DevOps has with GitHub and Microsoft Teams. The solution is well integrated with other Microsoft tools in one place, it is very good."
"Most developers and project managers choose the Microsoft tools to begin with because of familiarity, and these new tools are almost an extension of the tools you're already familiar with. There's a lot of knowledge transfer, which helps, rather than bringing in a new product line."
"We can forecast tasks and the number of hours a task will take and can compare it with how long a task actually takes."
"The solution is scalable."
"You can have test cases in DevOps but not in JIRA. And, DevOps has advantages in terms of executing those test cases."
"The product is easy to use and very stable."
 

Cons

"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."
"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."
"Not a perfect ten because the user interface is brand new and it needs improvement."
"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."
"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."
"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."
"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."
"We did have some brief performance issues, however, that was due to putting everything on one epic instead of breaking a project up."
"The communication could work better, especially for the development team."
"Definitely, there should be more integration between GitHub and Azure DevOps."
"I think that the integration is to some extent, immature."
"It would be great if I could integrate with a human resource type of software that could control timesheets."
"Its interface could be more user-friendly. It could be simplified for users with no prior knowledge. There should also be better tutorials."
"In comparison to JIRA, I believe DevOps has very poor reporting and metrics support."
"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."
 

Pricing and Cost Advice

"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."
"I can save time and money more quickly."
"We increased our quality and reduced our time costs."
"The costs are moderate and justify the value provided."
"We do not pay licenses for this solution."
"I find that the pricing is good, and it is competitive with the other vendors in the market."
"Most of the things that we need and use are incorporated in the corporate solution — there are no additional costs."
"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."
"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."
"The solution costs $5 or $10 per user, per month."
"The solution's deployment and licensing costs are very cheap compared to those of its competitors."
report
Use our free recommendation engine to learn which Release Automation solutions are best for your needs.
884,797 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
No data available
Manufacturing Company
14%
Financial Services Firm
10%
Government
10%
Computer Software Company
8%
 

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: March 2026.
884,797 professionals have used our research since 2012.