What is IT automation? Examples, levels and what to automate first
A nightly patch job counts as IT automation. So does an AI agent that restarts a stuck service on its own. We cover 12 examples, how to pick the next job to automate, how to tell whether it pays off and which actions should still wait for a person.
Every IT team already automates something: a patch policy in the RMM, a PowerShell script on a shared drive, a scheduled task someone set up years ago that nobody has opened since. The open question is what to automate next, now that scripts, RMM policies and AI agents all go after the same tickets. IT automation pays back fastest on work that runs often, costs little when it goes wrong and is easy to undo, while a person keeps signing off on everything else.
TL;DR
- What it is. IT automation is software that runs routine IT work, such as patching and account changes, whenever a trigger fires.
- Levels. Teams climb from runbooks to hand-run scripts, schedules, event-driven workflows and AI agents that act with approval.
- Where to start. Frequent, low-risk, easy-to-undo tasks go first.
- Measuring. Count hours saved minus maintenance hours, against a baseline.
- Gates. Read-only actions run freely, reversible ones get logged, destructive ones wait for a person.
What is IT automation?
IT automation is the use of scripts, policies, workflows and AI agents to run IT tasks without a technician doing each step by hand. A trigger starts the job (a schedule, an alert, a ticket or a new hire in the HR system), and the tool makes the change, checks that it worked and writes the result to a log.
For a team that looks after laptops, Microsoft 365 accounts and a help desk queue, that means patches that install overnight, new starters whose accounts exist before their first morning and a full disk that gets cleaned up before anyone files a ticket about it. When the work in question is monitoring, backups and incident response, people call the same thing IT operations automation. Bigger organizations also automate servers, cloud resources and software releases, and our guide to IT infrastructure management covers that side.
How IT automation works
Every IT automation system has four parts, whether it's a short PowerShell script or an AI agent.
The trigger decides when the job runs. It can be a clock (every night at 2 a.m.), an event (a monitoring alert, a device that falls out of compliance, an HR record that changes) or a request (a ticket, a form, a message to a chatbot).
The action is the change itself: run a script, install a package, add a user to a group, restart a service. In an RMM that's a script or a policy. In Microsoft 365 it's often a Graph API call or a Power Automate flow, and in an AI agent it's a tool call the agent picked.
The check reads the result back. A patch job that reports success while the device still waits for a reboot hasn't finished, so the automation asks the system again: is the service running, is the disk below its threshold, can the user sign in? The log then records what ran, on which device, with what result and who approved it. Without that log, nobody can answer "what changed last Tuesday?" in the middle of an incident.
IT automation vs related terms
Vendors use these terms loosely. The table pins each one to what it does on a working day.
| Term | What it means | Example |
|---|---|---|
| IT automation | Software runs an IT task from a trigger | A script installs patches every night |
| IT process automation | A whole multi-step IT process runs end to end, often across teams and approvals | A laptop request goes from ticket to manager approval to a shipped, configured device |
| Orchestration | Several automated tasks run in a set order across different tools | Onboarding creates the account, then the mailbox, then assigns the laptop |
| AIOps | Machine learning reads monitoring data to group alerts and point at causes | Fifty disk alerts become one incident with a likely cause attached |
| RPA | Bots click through screens where no API exists | A bot copies invoices from a vendor portal into the PSA |
| Agentic AI | AI picks and carries out steps toward a goal, using tools | An agent reads a ticket, checks the device and restarts a stuck service |
| IT operations management | The discipline of running IT services day to day, with automation as one of its tools | Monitoring, patching, backups and capacity planning |
Levels of IT automation
Kaseya's 2026 State of the MSP Report found that 53% of MSPs already use AI to automate ticketing, patching and monitoring, and that more than half have automated only about a quarter of their workload. Each level below keeps the ones under it, so a team running AI agents still has scheduled scripts and a runbook or two.
| Level | How it runs | Example | Who presses the button |
|---|---|---|---|
| 1. Documented runbook | A person follows written steps | An offboarding checklist in the wiki | A technician, every time |
| 2. Hand-run scripts | A person runs a script that does the steps | A PowerShell script that disables an account and converts the mailbox | A technician, every time |
| 3. Scheduled policies | The RMM or MDM runs it on a clock | Patches install on a test group on Tuesday night and on everyone else on Thursday | The schedule |
| 4. Event-driven workflows | An alert, a form or an HR change starts it | A disk space alert runs a cleanup script and closes the ticket if the check passes | The event |
| 5. AI agents with approval | An agent works out the fix and a person approves it | An agent finds the same failing service on a group of laptops and asks to restart it | The agent proposes, a technician approves |
| 6. Autonomous fixes with an audit trail | An agent fixes known, low-risk problems on its own and logs each one | The print spooler gets restarted when jobs stick, with a log entry for every restart | The agent, inside rules a person wrote |
At level 2 the script saves the typing, but a person is still the scheduler: when the technician who runs it every Monday is off sick, the job doesn't happen and nothing tells anyone. Level 3 hands the clock to the RMM, and a missed run shows up as a failed job.
Level 4 reacts to what happens on the device. The cleanup script runs when the disk alert fires, and a disk that fills up at 9 a.m. on a Wednesday gets its fix at 9 a.m. on a Wednesday.
Levels 5 and 6 bring in AI agents. A workflow runs steps somebody wrote in advance. An agent starts from the problem, reads the device, the logs and the ticket, and picks the steps itself, so it needs rules for which steps it may take without asking. One admin running NinjaOne and custom PowerShell asked r/sysadmin whether to add autonomous agents. The top reply says the poster would never let AI change production on its own, and another keeps each agent to one job, so an agent that handles email has no PowerShell access.
Level 6 is what people mean by autonomous IT. It sits at the top of the ladder and fits a narrow band of work: problems whose cause is already known, fixes that touch one device or one service, and changes that are easy to roll back. Everything outside that band stays at level 5, with a person on the approval.
IT automation examples
These 12 examples of automation in IT cover the work an internal IT team or an MSP does every week. The approval column is a starting point; tighten it for clients with stricter change control.
| Task | Trigger | What runs | Needs approval? | More |
|---|---|---|---|---|
| Patch deployment | Patch Tuesday, or a new critical CVE | Install on a test group, wait, then roll out to everyone with reboots in a maintenance window | Yes, before the full rollout | Windows patch management |
| Software install and update | A request ticket or a device joining a group | Install or update the package from an approved catalog | No, for catalog apps | Patch management software |
| New-hire onboarding | A new record in the HR system | Create the account, assign licenses and groups, set up the laptop | No, when the HR data is complete | |
| Employee offboarding | The last working day in HR | Block sign-in, revoke sessions, convert the mailbox, hand files to the manager | Yes, for the data handover | Offboarding process |
| Cloud tenant user changes | A role or department change | Swap groups, app access and mailbox permissions | Yes, for admin roles | |
| Password and MFA reset | A user request after an identity check | Reset, force a change at next sign-in, log it | No, once identity is verified | AI help desk software |
| Disk cleanup and service restart | A disk space or service-down alert | Clear temp files or restart the service, then check it stays up | No | Automated remediation |
| Alert-to-ticket routing | A monitoring alert | Open one ticket per incident, attach device details, assign it | No | Alert fatigue |
| Backup verification | Each finished backup job | Confirm the job completed and test-restore a sample | No; a failure pages a person | |
| Inventory and compliance report | A weekly schedule | Collect OS version, encryption and antivirus status, flag drift | No | Compliance automation |
| License reclamation | An account disabled or an app unused for a set period | Remove the license and record the saving | Yes, for anyone still active | Tool sprawl |
| Security baseline enforcement | A device drifting from policy | Re-apply firewall, disk encryption and local admin rules | Yes, for servers | Unified endpoint management |
Onboarding and offboarding make strong early candidates, because every step is predictable once the HR data is right. Brent Yax, CEO of the Michigan MSP Awecomm, told CRN in June 2026 that his team set out to build "a one-touch deployment for any new client employee coming in or exiting." His technicians now spend their time getting the right details into the ticket and checking the run afterwards.
Professor Messer's CompTIA A+ lesson on scripting walks through the same everyday jobs (reboots, drive mapping, backups, installs, updates) and closes on the steps people skip: test first and plan the rollback.
The help desk rows (resets, routing, software requests) also feed a ticket queue, and our guide to what a help desk does covers that side of the work.
Benefits of IT automation
A script runs the fortieth offboarding the same way it ran the first, including the step a person skips at 5 p.m. on a Friday, and the same goes for the security baseline it re-applies whenever a laptop drifts. The log it leaves behind is audit evidence you don't have to assemble by hand.
An event-driven fix runs when the alert fires, 3 a.m. included, so users find the problem already solved in the morning. Patches reach the fleet in days, which shortens the window an attacker has on a known vulnerability.
Automation also takes routine work off the queue so the same team can look after more devices, more users or more clients, and IT teams keep hiring while they do it. In Avasant's IT Spending and Staffing Benchmarks 2026/2027, 64% of companies are increasing IT headcount and 11% are cutting it, the largest share adding staff since at least 2008.
Yorkshire Tech, an MSP in Harrogate, put numbers on that capacity. Its managing director, John Benson, billed a client £18,000 for an offboarding that turned into a Microsoft 365 security incident. "Most of that was done by AI, not by us," he said. A data centre move that used to mean two weeks of planning and rollback work took his team about an hour (Yorkshire Tech case study).
What to automate first
Password resets make a good first candidate. Ivanti's 2025 Digital Employee Experience Report found that 72% of companies had automated security patch management and 67% IT ticket routing, while nearly 40% still hadn't automated password resets. A reset runs often, it's safe once the user's identity is checked, and a wrong one is undone with another reset.
Score your own candidates against five questions. Fill in the last column for one task you have in mind.
| Question | Automate sooner | Automate later | Your task |
|---|---|---|---|
| How often does it run? | Weekly or more | A few times a year | |
| How long does one run take by hand? | Long enough that people put it off | A minute or two | |
| What does a mistake cost? | A re-run | Downtime, lost data or a breach | |
| How easy is it to undo? | One click or one command | A restore from backup, or never | |
| How much work to build and keep running? | A script you already have | A new integration with an API that changes often |
Four or five answers in the left column means automate it now. Two or more in the middle column means write a solid runbook first, or automate it behind an approval step. Work that needs a sign-off still automates well, since the approval becomes one step in the workflow: a software request can wait for the manager's yes and then install on its own.
Two kinds of candidate disappoint. A broken process automated as it is breaks faster, so fix the steps on paper (level 1) before you script them. A job that runs twice a year costs less as a clear runbook than as a script nobody remembers how to fix when the next run comes around.
How to measure IT automation
Take the baseline before anything goes live. For each task, write down how often it runs per month and how many minutes it takes by hand, from ticket timestamps or a week of timing it.
The formula, per automation and per month:
codehours back = (runs per month x minutes per run by hand / 60) - hours spent building, fixing and maintaining it
Track five numbers alongside it:
- Hours back, from the formula above.
- Failure rate: runs that errored or needed a person to finish them.
- Tickets closed with no technician touch, for help desk automation.
- Hours spent maintaining scripts and policies.
- Time to notice a failed run, since a job that has been failing quietly for a month makes every other number wrong.
When the maintenance hours start to eat the hours back, the automation needs rework or retirement. Our IT metrics guide covers the help desk and SLA numbers that sit next to these.
Approval gates for AI agents and automated fixes
Once automation can change things on its own, every action needs a rule for whether it waits for a person. Sort actions into three tiers by what they can break and how easily they can be undone.
| Tier | Example actions | Runs on its own? | Gate |
|---|---|---|---|
| Read-only | Inventory, log search, health checks, drafting a fix | Yes | Logged |
| Reversible | Restart a service, clear temp files, install a catalog app, reset MFA after an identity check | Yes, with a check afterwards | Logged with a rollback step; a person reviews the log |
| Destructive or wide | Wipe a device, delete an account or mailbox, change a firewall rule, push to every client at once | No | A named person approves each run |
Around the tiers sit five controls. Give each automation its own scoped credentials, so a help desk agent can reset MFA and can't touch firewall rules. Run anything new in dry-run mode first, where it reports what it would change. Keep an audit log of every action and every approval. Write the rollback step before the first live run. And keep a kill switch, one setting that stops every automation for a client during an incident.
Context moves an action between tiers. John Douglass, president of Pileus Technologies, told CRN that with his patching agents, "a domain controller doesn't get treated like a standard workstation." Before patching, his agent checks each device, and when it finds a problem it either fixes it or pauses that device and records why. Our guides to human-in-the-loop AI, automated remediation and AI agents for IT operations go deeper on approval design, and connecting an AI agent to your RMM and help desk covers the plumbing.
Disclosure: Flamingo builds OpenFrame, so read this paragraph as the vendor's view. OpenFrame is open infrastructure for IT and security with the agents built in, and our take on AI-native IT automation follows the tiers above. Mingo works for technicians across large areas of RMM, remote access, patching, the help desk and logs, and Fae handles support requests on each user's computer. You decide per client which actions run on their own and which wait for a technician's tap, and every action is logged. The self-hosted version is free and runs without the agents; the managed service with Mingo and Fae costs $1 per device per month with 10M AI tokens after a 14-day free trial (pricing).
Why IT automations break
A technician who isn't sure stops and asks. A script keeps going, on every device in scope, until something tells it to stop.
The world changes under it. An OS update renames a setting, a vendor retires an API, a field in the HR system gets a new name, and a script that worked for two years starts failing or, worse, half-working. Give every automation a named owner who gets its failure alerts, and re-run a test after major updates.
It fails quietly. One r/sysadmin admin found that a nightly backup job had been failing for a stretch while every uptime check stayed green; they only noticed when they needed a restore. The replies point to the fix: a dead man's switch, where the job checks in when it finishes and silence raises the alert.
Nobody owns it. The person who wrote the script left, the logic lives in their old notes, and nobody wants to touch it. Keep scripts in version control, document what each one does and who owns it (our MSP documentation tools roundup covers where), and review the list when someone leaves.
Two tools do the same job. An RMM patch policy and an MDM update ring both patch the same laptops and fight over reboot times. Pick one tool per job and switch the other off for that job; tool sprawl is where these overlaps come from.
It repeats a mistake at full scale. AWS traced its 19-20 October 2025 outage in us-east-1 to a race condition in DynamoDB's automated DNS management, which left an empty DNS record that, in AWS's words, "the automation failed to repair." At IT team scale the same pattern is a policy scoped to every client by mistake. Roll changes out in stages (test group, a slice of the fleet, then everyone) and keep the kill switch within reach.
IT automation tools by layer
IT automation lives in several layers of the stack:
- Scripting: PowerShell, Bash and Python for anything with a command line or an API. Start with our PowerShell commands guide.
- RMM: scheduled scripts, patch policies and alert-triggered actions across endpoints. See what RMM is.
- ITSM and help desk: ticket routing, approvals and request workflows. See what ITSM is.
- Identity: Microsoft Entra lifecycle workflows and Google Workspace admin rules for joiners, movers and leavers.
- Monitoring and AIOps: alert grouping and likely causes. See AIOps platforms and IT operations management tools.
- Configuration management and infrastructure as code: Ansible, Puppet and Terraform for servers and cloud.
To compare products, prices and who each one fits, read our roundup of IT automation software.

Content Marketing Lead
Ohayo! I run content, SEO, social, and community at Flamingo. Before IT, I worked as a correspondent for Ukraine's Public Broadcasting Company and have a Master's in journalism.
Related Content
Frequently Asked Questions
/blog/what-is-it-automation
Still deciding?
Ask Mingo answers from our docs and customer stories.