We performed a comparison between Automic Continuous Delivery Director 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."CDD is primarily used for showing end users (managers, business teams, project managers, and release managers) what is happening with each release. The status and reporting features are very important. Automation reduces time to deploy. It also allows us to do more with releases and testing prior to production, better guaranteeing a smooth deployment."
"Its extensive range of available connectors eliminates the need for manual code writing when implementing solutions, thus reducing coding efforts."
"The most valuable features of Automic Continuous Delivery Director are the UI, release planning, and tracking, and you can do your soft and hard freeze through CDP."
"The second valuable aspect is its capability to drive external systems like deployment automation engines or to integrate with Agile Central."
"Its ability to automate release deployments, streamline release scope, and reduce the cost of and time for deployment."
"The most valuable feature for me is the fact that you can easily design a pipeline to promote applications from a development environment up to a production environment, and the team can become autonomous in designing those pipelines."
"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."
"It's a great product for the CI/CD process."
"Azure Pipeline and Azure Release are most valuable. I use Azure DevOps through pipeline and release."
"What I like most about Azure DevOps is how easy it is to manage projects and control deployments."
"It's a complete solution that has everything you need."
"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."
"The work items option is incredibly flexible."
"This platform provides a large span of tools and technologies."
"CDD and RA should be two modules in the same product. They do not automatically “talk” to each other. and they require endpoint definition."
"Reporting and dashboarding could be improved. Release pipelines should be creatable via templates as well as easily integrable/chained together. Visual navigation could also be improved when the pipelines become too large."
"We would like to have a more user-friendly interface. It is already very friendly, but as soon as you start to have many applications with many tasks, the applications should be easier to manipulate on the screen."
"The product's development has been stopped. It focuses on maintaining existing products."
"We have rolled out the SAFe model, but what we would like to have is better integration with Agile Central, for instance, or at least at the plugin level, where we would select only certain stories instead of many stories in the sprint."
"Automic Continuous Delivery Director can improve the integrations. We have 25 but would like more."
"I think that they have some menus there that are not very well placed."
"We are facing some problems because the capacity can only be measured within a project. It cannot be measured across multiple projects. So, the reporting needs to be enhanced, and there should be more graphs to be able to easily give the upper management insights about all the employees from different departments. It will be helpful for employee management. Currently, the managers over here are using Power BI for insights because the functionality of Azure DevOps Boards is not enough. So, we have to export the data into another visualization tool and get the results."
"It would be very useful if it had better integration with Microsoft Word because we would like to be able to define the priority requirement document and add it to different stages of the backlog."
"Its setup is quite complex."
"Reporting could be better. We would like to see how many applications are onboarded in DevOps and in which phase they are. We would like to know for how many applications we have done only the repository, but we have not yet done the build pipeline or deploy pipeline. Currently, there is no such report. We have to figure it out ourselves. There is no way to check how many applications are completing their build pipelines, how many applications are completing their deploy pipeline, how many are ready to use, and how many pipelines are working."
"The solution should have fewer updates."
"I would like to see more customization available to the administrator."
"Reporting across multiple projects could be improved."
More Automic Continuous Delivery Director Pricing and Cost Advice →
Automic Continuous Delivery Director is ranked 14th in Release Automation with 5 reviews while Microsoft Azure DevOps is ranked 1st in Release Automation with 126 reviews. Automic Continuous Delivery Director is rated 8.0, while Microsoft Azure DevOps is rated 8.2. The top reviewer of Automic Continuous Delivery Director writes "An automation solution to automate the entire release process but lacks development". On the other hand, the top reviewer of Microsoft Azure DevOps writes "Good support, helpful management capabilities, and great Kanban boards". Automic Continuous Delivery Director is most compared with , whereas Microsoft Azure DevOps is most compared with GitLab, Jira, TFS, Rally Software and ServiceNow Strategic Portfolio Management.
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.
