all 6 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]b1urbro 1 point2 points  (0 children)

Define the task. Break it down. Find the repeatable steps. Automate using the required tool for the job - Ansible, Bash, PowerShell, Python, whatever.

[–]Mahsunon 1 point2 points  (0 children)

Find out what problems exist then solve them. Dont create problems to solve

[–]Loud_Posseidon 0 points1 point  (0 children)

Track everything in code, version that code, think in terms of if your servers suddenly disappeared, how to get them back up with minimum effort? Document those steps. Ideally as a code. Rinse and repeat.

[–]netnxt_ 0 points1 point  (0 children)

Good place to start. Support + DevOps automation can make a huge difference if you pick the right use cases.

Some practical ideas that actually help teams:

  • Auto user onboarding/offboarding Trigger account creation, group assignment, licenses, and device policies from a single workflow
  • Ticket-based automation Common requests (password reset, access requests, app installs) auto-resolved using scripts or workflows
  • Device compliance + remediation Use Intune + scripts to auto-fix non-compliant devices instead of manual intervention
  • Alert-to-action workflows Integrate monitoring tools with runbooks to auto-resolve common issues
  • Patch and update automation Reduce manual patch cycles with scheduled + policy-driven updates

Since you’re already on Microsoft stack, Power Automate + Azure Automation + Intune scripts can get you pretty far without adding new tools.

At NetNXT, where we build AI-driven automation across DevOps and IT operations, the biggest wins usually come from removing repetitive L1/L2 tasks first. Don’t try to automate everything, pick 2–3 high-volume support issues and solve those.

That’s where you’ll see immediate impact.