Azure Automation Reviews

Azure Automation is used primarily to automate repetitive infrastructure and security operation tasks across multiple customer environments. We use it for VM lifecycle management, patch orchestration, scheduled compliance checks, and automated remediation workflows, which reduces manual efforts and improves operational consistency across all environments.

Azure Automation has been used to automate security operations workflows such as collecting diagnostic data, executing predefined remediation scripts, and enforcing configuration standards across customer environments. This has helped us standardize operational processes and reduce response times for recurring infrastructure and security-related tasks.

Azure Automation has significantly reduced manual operational effort and improved consistency across our managed customer environments. From a cybersecurity and operation standpoint, it has helped us standardize routine tasks, reduce configuration drifts, accelerate remediation activities, and allow engineers to focus on higher-value work instead of repetitive administration.

We have seen measurable benefits from Azure Automation. Routine operational tasks now require approximately 50 to 60% less manual effort. Configuration-related errors have been decreased by around 30% due to standardized automation workflows. Security and compliance remediation activities that previously took hours can often be completed in minutes through automated runbooks and scheduled actions.

The best features of Azure Automation are runbook automation, centralized job scheduling, update management, and integration with Azure services and APIs. From a security and operation perspective, we particularly value the ability to automate repetitive administrative tasks, enforce operational consistency, and execute remediation workflows at scale across multiple customer environments.

Centralized job scheduling in Azure Automation allows us to run maintenance, patching, and compliance tasks across multiple customer environments from a single platform, reducing manual coordination efforts. Integration with Azure APIs enables us to automate actions such as resource provisioning, security checks, and remediation workflows, which has reduced operational efforts and improved consistency across large-scale deployments.

One feature that is often overlooked in Azure Automation is how efficiently it scales across multiple subscriptions and customer environments. For managed service providers, the ability to standardize operational runbooks and reuse automation workflows across different customers delivers significant efficiency, consistency, and governance benefits.

From our experience, Azure Automation could be improved with better debugging and troubleshooting capabilities for complex runbooks, especially in large-scale environments. We would also prefer improved, more advanced reporting, centralized visibility across automation jobs, and stronger native integrations with security operations and compliance monitoring workflows.

One additional area Microsoft could improve in Azure Automation is providing more detailed execution analytics and dependency mapping for automation workflows. In large enterprise environments, better visibility into runbook performance, failure impact analysis, and cross-subscription automation governance would make troubleshooting and operational management much more efficient.

I have been using Azure Automation for two years.

Azure Automation is stable in our experience.

Azure Automation is scalable. We initially used it for a single line of business, and now we have been using it for multiple customers and multiple lines of businesses. It is scaling well without any performance issues or downtime and it is suitable for small-scale enterprises to large-scale enterprises, and it is highly scalable.

The customer support from our experience has been responsive and technically knowledgeable. Resolution time depends on the support tier, but overall, we have been able to resolve critical automation-related issues efficiently when escalation was required.

Before adopting Azure Automation, we primarily relied on custom PowerShell scripts, Windows Task Scheduler, and a mix of third-party automation tools for infrastructure management. We switched to Azure Automation because it provided a centralized, scalable, and cloud-native platform for managing automation across multiple customer environments with better governance, scheduling, and integration with Azure services.

Our experience with Azure Automation has been generally positive from a pricing and licensing perspective. The consumption-based model is straightforward and easy to understand, and setup costs were minimal since it is a managed cloud service. The main consideration is monitoring job execution and automation usage at scale to keep operational costs predictable across multiple customer environments.

We have seen a strong ROI from Azure Automation. Manual operational effort for recurring tasks has been reduced by approximately 50 to 60%. Routine remediation and maintenance activities are completed 70 to 80% faster through automation. We did not reduce headcount, but our existing engineering team can manage significantly more customer environments without adding additional operational resources.

Before selecting Azure Automation, we evaluated traditional scripting frameworks, enterprise job schedulers, and several third-party IT automation and orchestration platforms. We chose Azure Automation because of its native Azure integration, centralized management, scalability, and the ability to standardize automation workflows across multiple customer environments with minimal infrastructure overhead.

My advice for organizations adopting Azure Automation is to start with well-defined, repetitive operational tasks and standardize your runbook deployment process early. Use managed identity instead of hard-coded credentials. Implement proper testing and version controls for runbooks, and focus on automation that delivers measurable operational or security benefits before expanding to more complex workflows.

From our experience, Azure Automation is primarily an automation platform rather than an AI-driven product. From a governance and security perspective, its strengths are role-based access control, managed identities, auditability, and controlled execution of automation workflows, which help us enforce security policies and reduce operational risk across customer environments.

Azure Automation does not rely heavily on AI-generated outputs. Its effectiveness depends on the quality of the automation logic and runbooks implemented. When properly designed and tested, automation jobs execute very reliably and consistently, which is critical for infrastructure management, compliance enforcement, and security operations workflows. I would rate this product a 9 overall.

The typical use cases for Azure Automation are business automations, workflows for virtual machines or cloud environments, and automatic triggers for workflows, which we are currently using.

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.

PowerShell and Python scripting capabilities assist us significantly in developing tailored automation at 90% efficiency.

I have utilized Azure Automation runbooks.

We don't create new runbooks because some runbook templates simplify our business processes and tasks effectively.

Deployment with Azure Automation can be challenging at times, though sometimes it is very easy.

In terms of deployment installation, it requires improvement to be less complicated.

I have been using Azure Automation for seven years.

On a scale from one to ten, I would rate Microsoft support as eight.

Positive

I have a technical team that assists with the installation of Azure Automation, but I can do it myself if needed.

There are twenty people in our team.

They are cloud engineers.

Azure Automation is beneficial in terms of finance because we can organize the financial issues; sometimes the customer pays, sometimes we pay, and then we invoice the customer.

It is a bit expensive when comparing it to others.

Some scenarios or architectures require third-party tools or third-party cloud providers, and approximately 10% of our project can use these.

Approximately 10% of our customers use AWS and other providers.

I'm working with various products.

I am familiar with Azure Marketplace and Azure Automation, including Language Understanding.

It takes a couple of hours for my team to deploy the product, though sometimes complicated products take one to two days.

On a scale of 1-10, I rate Azure Automation as 8.

I experienced no challenges or issues when I deployed Azure Automation; the deployment was successful.

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.

Positive

I do not use Runbooks with Azure Automation.

With only one year of experience and a small requirement scope, I am not in a position to provide detailed information about utilizing the Asset Management feature.

I find the pricing to be affordable. I would rate this review an eight out of ten.

My clients mainly use Azure Automation for back-office processes and operations, as the application of this product is wide-ranging. It depends on their in-house capabilities and the opportunities they can leverage to integrate and automate manual activities.

The most valuable part of Azure Automation is that it is a platform providing features that can be custom-used. The functionalities are very wide, and the user-friendly nature and available technology can be simply applied to different technologies.

Azure Automation is very helpful for IT operation efficiency. The research of information and all these helpful features are indeed very useful.

The efficiency of Azure Automation Runbooks on IT operations is very high.

Based on feedback, Azure Automation needs to stay up-to-date with real technology game changers and include new features that meet market demands.

It is essential for Azure Automation to capture necessary technology improvements continuously to provide users with better functionalities.

I have been working with Azure Automation for almost three years now.

The scalability of Azure Automation is very high.

Technical support could be improved.

Positive

I have experience with UiPath. We initially worked with it before transitioning to Azure.

The setup process for Azure Automation is very easy. It is part of the Microsoft licensing, making it user-friendly for most companies that run Microsoft as their core office software.

The licensing pricing for Azure is quite good at the moment, making Microsoft products fairly accessible.

I have compared Azure Automation with other vendors' products. Initially, it wasn't as good, but Microsoft has made it a market leader in automation.

An example of a main competitor for Azure Automation is UiPath and similar products.

Azure is better than UiPath because its progression has been faster.

I currently work with SAP, but I haven't stopped working with that vendor at all. My involvement is cross-technology, so I'm exposed to S/4HANA and other technologies, which are very different from a couple of years ago.

Currently, I am working for a consultancy that is agnostic to technology, so tactically and strategically we provide implementation or knowledge on various technologies including Microsoft, Business Central, Project Operations, SAP, and Board, which are different and linked to various business areas.

Mostly I am working with Microsoft solutions now. In the last recent year, Microsoft is the technology with which we have the most exposure on current implementations, including both Business Central and Project Operations.

I have been working with Microsoft Business Operation for approximately a year and a half.

I am working with different products on Azure, as it is the platform we use to implement various types of solutions, including automation, IPA, and artificial intelligence.

Other colleagues work with Azure File Storage, Blob Storage, and App Services, as these are more related to cloud work.

I am working with Azure Automation, which is a process automation tool.

While we have used the alerts and scheduling functions in Azure Automation very often, I am not able to judge or review their effectiveness.

Integrating Azure Automation with other Azure services is very easy because there are pre-integration tools available that can be easily integrated with different technologies.

The main benefits Azure Automation provides include being useful for recurrent tasks, which help reduce manual intervention and allow people to focus on more added value tasks, enhanced by artificial intelligence for more complex duties.

I rate Azure Automation an eight out of ten.

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 Azure Automation for the past one year.

I rate Azure Automation an eight out of ten for stability.

Around ten users in our organization use Azure Automation.

I rate Azure Automation a nine out of ten for scalability.

I have previously used Git.

On a scale from one to ten, where one is difficult, and ten is easy, I rate Azure Automation a seven out of ten for the ease of its initial setup.

Azure Automation was deployed in a few hours.

Azure Automation is deployed on-cloud in our organization.

Overall, I rate Azure Automation an eight out of ten.