Automic Continuous Delivery Automation [EOL] vs Microsoft Azure DevOps comparison

Broadcom and Microsoft are both solutions in the Release Automation category. Additionally, 86% of Broadcom users are willing to recommend the solution, compared to 95% of Microsoft users who would recommend it.

Automic Continuous Delivery...

Read 13 Automic Continuous Delivery Automation [EOL] reviews

86% willing to recommend

Microsoft Azure DevOps

Read 137 Microsoft Azure DevOps reviews

16,903 Views
9,297 Comparison Views

95% willing to recommend

Automic Continuous Delivery...

Microsoft Azure DevOps

Comparison Buyer's Guide

Download the report

Executive Summary

We performed a comparison between Automic Continuous Delivery Automation [EOL] and Microsoft Azure DevOps based on real PeerSpot user reviews.

Find out what your peers are saying about Microsoft, GitLab, Red Hat and others in Release Automation.

To learn more, read our detailed Release Automation Report (Updated: May 2026).

Buyer's Guide

Release Automation

May 2026

Download the complete report

Helped 895,151 peers since 2012

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

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

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.

Read full review

Bharadwaj Deepak Mohapatra

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.

Read full review

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:

Pros

"The product provides efficiency, in terms time, cost, and resources."

"It can support very complex environments and dependencies."

"The most valuable feature is the ability to see which problems have been resolved from deployment."

"It gives us good feedback on visualizations and on how our processes have progressed."

"It provides a wonderful user interface which is easy to use."

"We have saved on our time costs and have seen more quality."

"Gives people insight into what's happening during the deployment."

"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."

More Automic Continuous Delivery Automation [EOL] pros

"Some of the most valuable features are the ease of use and the ability to monitor a lot of things."

"The solution's most valuable features are backlog management, build release pipeline, and testing."

"I like the entire tool because it is a one-stop-solution for DevOps."

"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."

"We can track everything from the requirements stage to the production stage."

"The most valuable aspect of Azure DevOps for me is its robust version control functionality, which is critical for our workflow."

"We are 100% satisfied with it."

"The product is easy to use and very stable."

More Microsoft Azure DevOps pros

Cons

"Not a perfect ten because the user interface is brand new and it needs improvement."

"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."

"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."

"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."

"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."

"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 hope that we can integrate the new CD Directive into our portfolio, so we can bring the deployment and release management closer together."

"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."

More Automic Continuous Delivery Automation [EOL] cons

"There are some areas that need improvement such as tracking."

"It is not that intuitive. Sometimes, it is hard to find some of the functions. I would like to have an old-fashioned menu structure to be able to easily find things. Its environment setup is not very good. They should improve the way it is set up for different screens and make it easier to find functionalities and maintain team members."

"All of the tests of the applications are done on the mobile or web interface and it could be improved."

"There could more integration with other platforms."

"We are facing some problems because the capacity can only be measured within a project. It cannot be measured across multiple projects."

"Microsoft could focus on refining the reporting and dashboard elements of Azure DevOps to improve it."

"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."

"They do very frequent releases, there's a complete change in UI kind of stuff. Sometimes it feels like they change it too often."

More Microsoft Azure DevOps cons

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."

"Licensing cost per user is approximately $11 to $15. We have about 400 users, but not all are active. We have around 200 to 300 active users."

"The solution costs $5 or $10 per user, per month."

"There is a licensing fee of $6/user per month."

"We purchase the solution on an annual basis."

"There are additional costs for some functionality, such as increased scalability."

"There is a license for this solution."

"I don't know what we pay, but I do know what I've seen online. If we switched to JIRA, we will basically have to double our costs because we still have to pay for the DevOps licensing. We're probably spending $100 a month on it. It has only standard licensing fees."

"It is a subscription model and I only pay for what I use."

More Microsoft Azure DevOps pricing and cost advice

See which vendors are best for you

Use our free recommendation engine to learn which Release Automation solutions are best for your needs.

See recommendations

895,151 professionals have used our research since 2012.

Top Industries

By visitors reading reviews

Financial Services Firm

15%

Comms Service Provider

15%

Marketing Services Firm

11%

Real Estate/Law Firm

Manufacturing Company

13%

Financial Services Firm

Government

Computer Software Company

Company Size

By reviewers

Large Enterprise

Midsize Enterprise

Small Business

By reviewers
Company Size	Count
Small Business	2
Midsize Enterprise	2
Large Enterprise	9

By reviewers
Company Size	Count
Small Business	43
Midsize Enterprise	28
Large Enterprise	69

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...

See all answers

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...

See all answers

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.

See all answers

Comparisons

UrbanCode Deploy vs Automic Continuous Delivery Automation [EOL]

Compared 23% of the time

Red Hat Ansible Automation Platform vs Automic Continuous Delivery Automation [EOL]

Compared 16% of the time

Nolio Release Automation vs Automic Continuous Delivery Automation [EOL]

Compared 13% of the time

AWS CodeStar vs Automic Continuous Delivery Automation [EOL]

Compared 12% of the time

More Automic Continuous Delivery Automation [EOL] Competitors

GitLab vs Microsoft Azure DevOps

Compared 51% of the time

OpenText Application Quality Management vs Microsoft Azure DevOps

Compared 7% of the time

Jira vs Microsoft Azure DevOps

Compared 4% of the time

Rally Software vs Microsoft Azure DevOps

Compared 4% of the time

Codebeamer vs Microsoft Azure DevOps

Compared 2% of the time

More Microsoft Azure DevOps Competitors

Product Reports

Buyer's Guide

Automic Continuous Delivery Automation [EOL]

May 2026

Automic Continuous Delivery Automation [EOL] report

Download Automic Continuous Delivery Automation [EOL] product report

Buyer's Guide

Microsoft Azure DevOps

May 2026

Download Microsoft Azure DevOps product report

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

Deliver apps at pace with agile development and let customer satisfaction soar.

Today, the pressure is on to transform how you deliver applications to market. Get release agility and speed without compromising quality and stability with CA Continuous Delivery Automation. Deliver apps reliably on demand from development through production—mobile to mainframe. Agilely scale as the cadence, volume and complexity of your apps grow. It’s DevOps-ready release management and automation for your dynamic enterprise.

Broadcom

Microsoft Azure DevOps offers full cycle integration with CI/CD pipelines and a user-friendly interface. It streamlines development processes and supports Agile planning, making it a versatile choice for teams focusing on software development and project management.

Azure DevOps is designed to enhance productivity with its comprehensive project management features, including task management and backlog organization. It supports automation, agile methodologies, and provides seamless integration with Microsoft products. Despite its robust functionalities, users suggest enhancements in customization, integration with external platforms like GitHub and Office 365, as well as advancements in reporting and dashboard functionalities. Azure DevOps plays a key role in CI/CD workflows, code repository management, work item tracking, and test automation, promoting collaboration across distributed teams.

What are the key features of Microsoft Azure DevOps?

Full Cycle Integration: Manages the entire development lifecycle supporting CI/CD pipelines.
Agile Support: Facilitates agile planning and backlog management for efficient project execution.
Project Management: Offers comprehensive task management features to streamline workflows.
Microsoft Integration: Provides seamless connectivity with other Microsoft tools.
Automation and Reporting: Enhances efficiency through automated processes and reporting capabilities.

What benefits should users expect from Microsoft Azure DevOps?

Increased Productivity: Streamlines development and project management processes.
Scalability: Adapts to the growing needs of development teams and projects.
Customization: Offers extensions to tailor functionalities to meet specific project requirements.
Enhanced Collaboration: Supports distributed teams with effective communication tools.

Microsoft Azure DevOps is widely implemented in industries focusing on software development and IT project management. It is specifically suitable for organizations that prioritize continuous integration, agile practices, and cross-team collaboration. Companies leverage Azure DevOps for managing code repositories, automating builds, and tracking work items, ensuring efficient project delivery in sectors such as technology, finance, and healthcare.

Microsoft

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: May 2026.

DOWNLOAD NOW

895,151 professionals have used our research since 2012.

See our list of best Release Automation vendors.

We monitor all Release Automation reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.