Try our new research platform with insights from 80,000+ expert users

Azure Automation vs Control-M comparison

 

Comparison Buyer's Guide

Executive Summary
 

Categories and Ranking

Azure Automation
Ranking in Process Automation
30th
Average Rating
8.0
Number of Reviews
1
Ranking in other categories
No ranking in other categories
Control-M
Ranking in Process Automation
2nd
Average Rating
8.8
Number of Reviews
114
Ranking in other categories
Managed File Transfer (MFT) (3rd), Workload Automation (1st)
 

Featured Reviews

MS
Dec 5, 2023
Can be used to automate the CI/CD pipeline, from data ingestion to endpoint generation
We use Azure Automation to automate the CI/CD pipeline, from data ingestion to endpoint generation The most valuable feature of Azure Automation is the scripting. The solution’s user interface is also another valuable feature. The solution’s user interface could be improved. I have been using…
SS
Jul 15, 2024
It provides a centralized view of our enterprise workload
Control-M provides a centralized view of our enterprise workload. As the owner, I can access my dashboard and see the status of jobs across the enterprise. It is strong at integrating with different applications and creating a pipeline of dependencies across applications on different operating systems. When it comes to developments where we have to move across regions or environments, it seamlessly integrates and adapts to different regions. Regarding integration with the DevOps pipeline, it allows us to use a JSON file and promote it across environments easily. We use Control-M to deploy workflows for DataOps and DevOps initiatives. It allows us to quickly test workflows or configuration changes without much manual effort. We add the JSON file for the conversation parameters and let the system handle the schedule. Integrating other DevOps tools within the journey gives us the management perspective and approval of multiple pipelines.

Quotes from Members

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

Pros

"The most valuable feature of Azure Automation is the scripting."
"The integration with ServiceNow is good. When a job ends and there are problems with it, we automatically open an incident in this platform, and the number of the incident is forwarded to Control-M. This means that we have a record of it with the log of the job."
"BIM is helpful because we do not miss any SLAs, as we get to know the issue well in advance. It is the topmost service that has helped us provide better solutions for the business."
"We value Control-M mainly for the ability to control multiple nodes in a coordinated manner. Control-M has the ability to really coordinate across a lot of nodes."
"Maintaining and monitoring of workloads have been and continue to be the most valuable feature in our environment."
"We are now able to deliver data to our data warehouses and dashboards promptly."
"There is a batch monitoring tool called Batch Impact Manager, which proactively warns when processing is behind and SLAs are in jeopardy of being missed."
"Control-M is useful to automate all critical and non-critical processes. Using Control-M, we can automate application workflows as well as file transfers involved in application workflows. We can also use it to run batches related to applications. Automating these processes reduces the RTO and RPO, which helps in the case of failures. It also helps us to identify bottlenecks and take corrective measures."
"I find Control-M for SAP and Control-M for Informatica good. You can connect to the Linux or Windows servers, and you can run multiple jobs."
 

Cons

"The solution’s user interface could be improved."
"Their technicians should be more involved when we're applying new technology to Control-M, such as cloud. We're working with cloud right now, with AWS, and getting the attention of a technician, sometimes, can take some time. It would be nice if they had somebody assigned to it. Dedicated support."
"Consider adding a mobile application for remote management."
"A Control-M on-prem license is based on the number of jobs, which is the number of tasks a particular customer wants to have. These tasks have to be run within 24 hours window. For example, if you have a license for 100 jobs, you can run a maximum of 100 jobs in a 24-hour window. If your operations could not run 10 jobs, and they ran only 90 jobs, they just carry over to the next day, but the next day, they will have 110 jobs. Control-M asks you to buy those 10 more licenses because you were out of compliance in terms of the number of licenses. This is something that needs to be indicated in Control-M GUI so that customers know the number of licenses they're going to use in this time window. Their support and documentation should be improved. I am not that satisfied with their customer support. Sometimes, they don't have the answers. Their documentation is very poor. It is not well written, and it is not in a very logical manner. You can use it on Unix, Linux, Windows, and AIX, but it needs some improvement on iSeries. It needs a built-in mechanism inside the system to give you an option to restore from the last point of failure. If a process crashes, the Control-M needs to have a mechanism in iSeries where the process can be restored from the last point of failure."
"Sometimes, with technical support, they will take feedback, but you don't know where that feedback goes or if it proceeds along in the thought process."
"The community and the networking that goes on within that community need improvement. We want to be able to reach out to an SME, and say, "Hey, we are doing it this way. Does that make sense?" Ideally, they come back. and say, "Yes, it does make sense to do it that way. However, if you want to do it this way, then it is a little more efficient." We understand that one solution framework doesn't fit everybody. Depending on the breadth of the data and how broad it is, you may have different models for one over the other."
"With the current version update, I'm not sure why we needed a separate database upgrade. Why not put it all in one package? Previously, you could do it either via a manual upgrade or an in-place upgrade but it wasn't separate."
"The stability of Control-M has Not been great. A big thing we've been trying to work on with BMC is observability. Modern applications should be observable and resilient, but we're finding that sometimes Control-M is not very resilient and many times Control-M is not very observable."
"I would like to see more auditing capabilities. Right now, it has the basics and I've been trying to set those up to work with what our auditors are looking for."
 

Pricing and Cost Advice

Information not available
"The annual licensing within BMC Control-M is on a per task basis. Three- and five-year contracts are also offered. The customer usually buys a bundle of tasks, e.g., 5,000 tasks, then my team configures Control-M for their usage."
"BMC's price is based on the number of jobs."
"You're going to spend a lot of money upfront, but the benefits you're going to get out of it are going to quickly pay for it."
"we are more looking for a better cost/license/performance model because BMC, while we could say it's the best, is also the most expensive. That is what we are probably most annoyed with. We are paying something like €1,000,000 over three years for having 4,000 jobs running. That's expensive."
"The price is right because of the licensing schema, which is based on nodes and processes. You purchase what you use, no more and no less, and you can grow with time."
"The cost is basically $100 a job, give or take."
"The pricing and licensing could be better. However, when I compare Control-M pricing with JAMS, Control-M is still better priced than JAMS enterprise."
"Compare to other tools Pricing and licensing was more. It should be decrease."
report
Use our free recommendation engine to learn which Process Automation solutions are best for your needs.
801,394 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
No data available
Financial Services Firm
28%
Computer Software Company
13%
Manufacturing Company
8%
Insurance Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What do you like most about Azure Automation?
The most valuable feature of Azure Automation is the scripting.
What needs improvement with Azure Automation?
The solution’s user interface could be improved.
What is your primary use case for Azure Automation?
We use Azure Automation to automate the CI/CD pipeline, from data ingestion to endpoint generation.
How does Control-M compare with AutoSys Workload Automation?
Control-M acts as a single, centralized interface for monitoring and managing all batch processes, which is helpful because nothing gets left unattended since it is all visible in one place, and th...
What do you like most about Control-M?
First of all, the shift from manual to automation has been valuable. We have a tool that can automate.
What is your experience regarding pricing and costs for Control-M?
The product price is reasonable. I rate the pricing an eight.
 

Also Known As

No data available
Control M
 

Learn More

Video not available
 

Overview

 

Sample Customers

1. Adobe 2. BMW 3. Coca-Cola 4. General Electric 5. Johnson & Johnson 6. NBCUniversal 7. Pfizer 8. Samsung 9. Siemens 10. Toyota 11. Verizon 12. 3M 13. Accenture 14. Airbus 15. Allianz 16. American Express 17. AT&T 18. Bank of America 19. Boeing 20. Cisco 21. Dell 22. ExxonMobil 23. Ford 24. General Motors 25. IBM 26. Intel 27. JPMorgan Chase 28. Microsoft (self-use) 29. Nestle 30. Procter & Gamble 31. Shell 32. Walmart
CARFAX, Tampa General Hospital, Navistar, Amadeus, Raymond James, Railinc
Find out what your peers are saying about Camunda, BMC, Appian and others in Process Automation. Updated: August 2024.
801,394 professionals have used our research since 2012.