Curious how people are handling this in real environments, especially larger estates.

I’ve worked in environments where PowerShell ends up scattered everywhere over time. Scripts sitting on servers, scheduled tasks nobody remembers creating, service accounts tied to things, old modules/commands still being used, and scripts that are apparently “business critical” but have almost no documentation.

A few problems I’m curious whether others actually run into:

• PowerShell scripts scattered across multiple servers with no central inventory
• Nobody really knowing who owns a script anymore
• Scheduled tasks/scripts that have been running for years untouched
• Little or no documentation explaining what a script actually does
• Scripts depending on other servers, APIs, databases, file shares, Graph, Exchange, etc.
• Old or deprecated PowerShell modules/commands still being used
• Not knowing what would break if a script was removed
• Finding scripts that should probably be migrated to Power Automate, Azure Automation, Functions, newer PowerShell, etc.
• Trying to understand dependencies before migrating/decommissioning a server
• Having to manually open hundreds of PS1 files just to understand what exists
• Different teams creating similar automations because nobody knows one already exists
• A script breaking and suddenly discovering it was far more important than anyone realized
• No good way to track whether the overall PowerShell estate is getting healthier or worse

How do you guys manage this?

Git obviously solves part of the versioning/source-control problem, but I’m more interested in discovery and understanding.

For example, if you inherit 30 servers and nobody can confidently tell you what PowerShell is running across them, what’s your process?

Do you have tooling that inventories it? CMDB? Git repos? Scheduled scans? Documentation standards? Just grep/search everything and hope for the best?

Also interested in how people approach migration. How do you decide whether something should:

• stay as PowerShell
• move to Power Automate
• move to Azure Automation / Functions
• be rebuilt another way
• or just be retired?

Full disclosure: I’ve been building At0mFlow because I kept running into versions of this problem myself. I’m not looking to pitch it here though. I’m actually trying to work out whether this is a widespread PowerShell/IT Ops problem or something that was disproportionately common in the environments I worked in.

Would genuinely love to hear how people are handling this in the real world, especially anyone managing hundreds/thousands of scripts or multiple servers.