No more typing reviews! Try our Samantha, our new voice AI agent.

ActiveBatch by Redwood vs Azure Automation 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

ActiveBatch by Redwood
Ranking in Process Automation
13th
Average Rating
9.0
Reviews Sentiment
7.2
Number of Reviews
41
Ranking in other categories
Managed File Transfer (MFT) (10th), Workload Automation (9th)
Azure Automation
Ranking in Process Automation
22nd
Average Rating
8.0
Reviews Sentiment
6.2
Number of Reviews
4
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of November 2026, in the Process Automation category, the mindshare of ActiveBatch by Redwood is 1.3%, up from 1.0% compared to the previous year. The mindshare of Azure Automation is 1.1%, down from 1.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Process Automation Mindshare Distribution
ProductMindshare (%)
ActiveBatch by Redwood1.3%
Azure Automation1.1%
Other97.6%
Process Automation
 

Featured Reviews

Sai  - PeerSpot reviewer
Ai/Data Analyst at CSD
Automation has streamlined complex data workflows and now saves time on recurring reporting
To improve ActiveBatch by Redwood, the UI could be more modern and intuitive, and another thing that comes to mind is that it can feel overwhelming when workflows become large and complex. Troubleshooting can take extra time when there are multiple dependencies, jobs, and integrations running together. Better visualization of workflow relationships and easier debugging would really help. I would also appreciate seeing more simplified onboarding and documentation for newer users, as there is a learning curve at the beginning. Another improvement area could be smarter analytics or AI-driven recommendations, such as proactively identifying workflow bottlenecks, failed job patterns, or optimization suggestions instead of relying mostly on manual monitoring. From an operational perspective, faster configuration for integrations and cloud-based workflows would make implementation smoother, especially in environments working heavily with APIs and data pipelines. I have covered the main points regarding needed improvements. Overall, the platform is very capable and reliable for automation and workflow scheduling, especially in data-heavy environments. Most of the improvements I want are around making it easier for day-to-day use, such as a more intuitive UI, simpler troubleshooting for complex workflows, better onboarding for newer users, and more intelligent monitoring or optimization insights. The core functionality is strong, and the biggest opportunity is improving the overall user experience and simplifying operational management.
reviewer1017936 - PeerSpot reviewer
Senior Database / Data Management Expert at a comms service provider with 10,001+ employees
Automation has reduced manual work and supports efficient customer-focused development
Any solution has room for improvement, and this one is no exception.In future updates, I believe more AI functionality could be added to Azure Automation, as AI is becoming increasingly prevalent across all solutions. Sometimes when integrating with third-party tools, we cannot find the proper API and must perform manual work, which requires additional development on our end. We encounter these issues occasionally.

Quotes from Members

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

Pros

"This is a very good tool and I'm really missing it in my new company because I don't have a robust enterprise-wide scheduling tool and a really good tool for automating end-to-end."
"By implementing a sophisticated scheduling mechanism, the system allows for the precise triggering of jobs at user-selected frequencies, enabling a seamless and automated execution of tasks according to specified time intervals."
"I find this to be the easiest product that I have ever used, especially compared to Robot Schedule and CA AutoSys as well as an in-house scheduling software that I had designed and developed at one time."
"As far as centralization goes it's nice because we can see all these processes that are tied to this larger process. The commissions, FTP processing, the reporting, the file moves to the business users — all that is right there. It's very easy to read. It's easy to tie it together, visually, and see where each of these steps fits into the bigger picture."
"It can connect to a number of third-party/legacy systems."
"One of the most valuable features of this solution is the versatility of the prebuilt jobs."
"We save thousands of man-hours annually."
"Managing the workload and monitoring the tasks were very difficult with manual interventions. Now, by using ActiveBatch, the process is automated and it runs tasks on a scheduled basis."
"The most valuable part of Azure Automation is that it is a platform providing features that can be custom-used, with very wide functionalities, and the user-friendly nature and available technology can be simply applied to different technologies."
"The best features of Azure Automation help us automate tasks for the customer and eliminate a significant amount of manual work."
"Azure Automation brings many benefits to my company and my customers' companies because many jobs can be converted automatically through an AI agent to complete tasks."
"The most valuable feature of Azure Automation is the scripting."
 

Cons

"The only thing is that it does have a little bit of a learning curve because it is fairly complex."
"There are very few documents that provide us with detailed information on the troubleshooting of errors that occur during integration with the existing environment."
"It does have a little bit of a learning curve because it is fairly complex. You have to learn how it does things. I don't know if it's any worse than any other tool would be, just because of the nature of what it does... the learning curve is the hardest part."
"An area for improvement in ActiveBatch Workload Automation is its interface or GUI. It could be a little better. There isn't any additional feature I'd like to see in the tool, except for the GUI, everything looks good."
"They should offer pricing that is more affordable."
"The monitoring dashboard could have been more user-friendly so that in the monitoring dashboard itself we can see the total number of jobs created in the system and how many were currently active/scheduled/chained."
"Between version 10 and version 12 there was a change. In version 10, they had each object in its own folder. But on the back end, they saw it at the root level. So when we moved over to version 12, everything was in the same area mixed together. It was incredibly difficult and we actually had to create our own folders and move those objects—like schedules, jobs, user accounts—and manually put those into folders, whereas the previous version already had it."
"I can't get the cleaning up of logs to work consistently."
"Technical support could be improved."
"The solution’s user interface could be improved."
"Sometimes when integrating with third-party tools, we cannot find the proper API and must perform manual work, which requires additional development on our end."
"Deployment with Azure Automation can be challenging at times, though sometimes it is very easy."
 

Pricing and Cost Advice

"Currently, we are paying approximately $7,000 yearly, which includes support."
"The price was fairly in line with other automation tools. I don't think it's exorbitantly expensive, relatively speaking."
"It allows for lower operational overhead."
"I like ActiveBatch Workload Automation's licensing model because they're not holding you down on an agentless model or agent model, where every server needs to have an agent. That's the main selling point of the solution and I hope they stay that way."
"ActiveBatch is currently redesigning themselves. In the past, they were a low cost solution for automation. They had a nice tool that was very inexpensive. With their five-year plan, they will be more enhancement-driven, so they're trying to improve their software, customer service, and the way that their customers get information from them. In doing that, they're raising the price of their base system. They changed from one pricing model to another, which has caused some friction between ActiveBatch and us. We're working through that right now with them. That's one of the reasons why we're why we were evaluating other software packages."
"If you compare ActiveBatch licensing to Control-M, you're looking at $50,000 as opposed to millions."
"The pricing was fair. There are additional costs for the plugins. We have the standard licensing fees for different pieces, then we have the plugins which were add-ons. However, we expected that."
"I don't think we've ever had a problem with the pricing or licensing. Even the maintenance fees are very much in line. They are not excessive. I think for the support that you get, you get a good value for your money. It's the best value on the market."
Information not available
report
Use our free recommendation engine to learn which Process Automation solutions are best for your needs.
922,942 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Outsourcing Company
11%
Financial Services Firm
10%
Construction Company
10%
Manufacturing Company
10%
Financial Services Firm
16%
Media Company
9%
Construction Company
8%
Comms Service Provider
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business11
Midsize Enterprise14
Large Enterprise52
No data available
 

Questions from the Community

What is your experience regarding pricing and costs for ActiveBatch Workload Automation?
I was not directly involved in the pricing, setup cost, and licensing decisions for ActiveBatch by Redwood, so my experience is from the user and workflow side rather than procurement. However, bas...
What needs improvement with ActiveBatch Workload Automation?
ActiveBatch by Redwood could be improved with a more modern and intuitive user interface, faster performance for very large workflows, and expanded built-in integrations with newer cloud and DevOps...
What is your primary use case for ActiveBatch Workload Automation?
My main use case for ActiveBatch by Redwood is enterprise workload automation, job scheduling, and orchestrating business processes across applications, servers, and cloud environments. For example...
What needs improvement with Azure Automation?
Any solution has room for improvement, and this one is no exception.In future updates, I believe more AI functionality could be added to Azure Automation, as AI is becoming increasingly prevalent a...
What is your primary use case for Azure Automation?
Azure Automation is typically used for development for the customer. I develop based on requirements rather than for myself.
What advice do you have for others considering Azure Automation?
I cannot identify the weak points of Azure Automation, as I am a director rather than a developer.I do not use Runbooks with Azure Automation. With only one year of experience and a small requireme...
 

Also Known As

ActiveBatch
No data available
 

Overview

 

Sample Customers

Informatica, D&H, ACES, PrimeSource, Sub-Zero Group, SThree, Lamar Advertising, Subway, Xcel Energy, Ignite Technologies, Whataburger, Jyske Bank, Omaha Children's Hospital
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
Find out what your peers are saying about ActiveBatch by Redwood vs. Azure Automation and other solutions. Updated: November 2026.
922,942 professionals have used our research since 2012.